IT Security for Finance

Penetration Testing ‘tools’ are used as part of engagements to help assess, identify and exploit commonly found vulnerabilities. There are numerous different kinds of tools used within every engagement, each with a different use and varying popularity – like most things, people have a preference!

Whilst these tools are effective at finding what they’re able to, it’s important to ensure your provider does not simply run automated tools and issue a report. Many vulnerabilities cannot be identified simply by running an automated tool without some form of manual verification and, in some cases, manual exploitation too. Our consultants at Fidus focus on manual testing where possible and whilst some of these tools are used to aid assessments, they will never be the focal point of the engagement.

Commonly seen tools include; NMap, Metapsloit, SQLMap, Nessus, Qualys, Nikto, SSLScan, Cobalt Strike and many, many more.

The end goal of a Pen Test varies from client to client and has many underlying factors, such as; complexity of application and/or network, whether there have been previous tests, what kind of data the application/network holds and the size of the organisation.

The most frequent goal we are given by clients is “Can you obtain our customer information?”. However, it is also important to not overlook other issues which could lead to things such as loss of business reputation if the customer facing website is compromised.

Penetration Testing should NOT become a Pass/Fail assessment for your organisation It should be seen as an exercise to evaluate your current security posture with the aim to make as many improvements as possible.

At Fidus, we ensure the client is able to extract as much value from the assessment as possible. As such, our reports contain sections for both the executive team which is aimed at the risks to the business and a technical section for the development and IT teams. We provide enough information for the C-Level staff members to fully understand the report and enough information for the technical team to be able to locate, reproduce and fix all issues discovered.

• Initiation / Scoping – Ensuring the delivery of work is exactly as you require and the correct amount of time is allocated to your engagement.
• Pre-Assessment – Confirmation that your environment is accessible and ready for testing and all requirements have been completed.
• Assessment – Conducting the engagement as per the Scope of Work.
• Post-Assessment – Collection of all results and ensuring the tested environment has been tidied up where possible.
• Reporting – Compilation of results for final deliverable.
• Remediation Discussion and Support – Discussion and explanation of all issues where required and further support for implementing changes as recommended within the deliverable.

The time it takes to conduct each assessment is dependent on the scope of the engagement. There are multiple factors which can impact the length of the engagement, such as; network size, complexity of applications, size of organisation and whether the assessment is internal or external.

The main benefit of is the proactive approach to finding serious vulnerabilities before attackers do. These vulnerabilities can lead to numerous scenarios such as; reputational damage, loss of user data and financial fines.

Compliance

Penetration Testing is also a key factor to becoming compliant in multiple standards, such as Cyber Essentials Plus, PCI DSS and ISO 27001.

Evaluate Current Security Controls

A pen test allows you to evaluate current security controls which are in place. These could be Intrusion Prevention Systems (IDS), Intrusion Protection Systems (IPS), Firewalls and Web Application Firewalls (WAF). We commonly see mis-configuration of these devices, sometimes rendering them ineffective at their main job, keeping your data safe.

Avoid The Cost of Network Downtime

Have you ever worked out how much it would cost your business if you had even a day downtime because of a cyber attack? This is not simply the loss of a day wages for all employees, it may also include; legal fees, incident response, customer protection and damage control activities.

A security assessment also allows you to establish the level of exposure if a specific area of your company gets breached, such as the main user web application, and ascertain how sensitive the data held within is. Currently, sensitive breaches must be reported to the Information Commissioner’s Office (ICO) with fines sometimes reaching 6 figures. However, with the upcoming General Data Protection Regulation (GDPR) law, these fines are set to multiply and only give organisations 72 hours to discover and report a breach. The easiest way to avoid a breach is to proactively defend against one.

Penetration Testing should be performed on a regular basis to ensure newly discovered threats and previously recommended implementations are evaluated. In addition to this, penetration testing should occur when there’s a big change to network infrastructure, a new web application is deployed, during/before mergers and Phishing assessments should take place upon expansion of your team.

The kind of assessment you require has many underlying factors. Some questions such as “We’re about to deploy a new web application, what kind of testing do you recommend?” are much easier to answer than “We’ve never had a Penetration Test before, what do you recommend?”.

For the latter question, there are a series of questions which need to be answered first. Such as; What are your key assets? What would cripple your business if stolen? (Signing keys, source code, customer data etc), How many employees do you have? What is your budget?

It is important to have all of the information to be able to evaluate what would have the best return on investment for your Penetration Test.

If you would like to talk through the different kind of paths you could take, please get in touch.