Step 1: Understand the organisation’s vulnerability to the threat
Identify the types of attacks the threat actors are likely to carry out, and map out the attack paths, highlighting the offensive techniques likely to be used. This analysis should exploit the significant amount of open source threat intelligence reporting available on techniques used by specific state-sponsored threat actors (including those threat actors referenced by US-CERT). The MITRE ATT&CK framework should be used to structure this analysis and provide a common language to discuss the attack techniques.
The organisation's ability to defend and detect against these specific techniques should then be evaluated. We have found this is best conducted using a combination of:
- Technical knowledge about the environment and the security controls applied; and,
- Purple teaming to simulate attacker techniques, determine the effectiveness of security controls and capabilities, and test assumptions held about the environment.
Step 2: Identify pragmatic and threat-focused actions to remediate vulnerabilities
The success of security improvement programmes often depends on whether pragmatic fixes and improvements have been identified to remediate vulnerabilities, and directly improve protection, detection and response capabilities to make it more difficult for an attacker to successfully compromise the organisation.
We have seen organisations have the most success identifying these when they:
- Gather expertise from across the organisation including IT and security teams (covering both red and blue teams) into a single location to workshop the problem with a whiteboard;
- Bring in independent security expertise to understand previous attacks in-depth, challenge stakeholders on analysis and decision making, and drive discussions towards actionable outcomes with assigned owners;
- Use a red team to help prioritise improvement activities by providing an attacker-centric view of the environment and its vulnerabilities; and, most importantly,
- Unswayingly focus on identifying achievable quick-win improvements.
We have found using a purple team approach to simulate attack techniques to be a highly effective way of identifying both vulnerabilities and improvements to resolve these. At a large financial services organisation, we were recently able to help them identify over 400 pragmatic fixes and improvements, by simulating the activity of several cyber crime threat actors they were concerned about.
Step 3: Develop and deliver a programme focused on rapid risk reduction
These identified actions should then be used to form a plan of what can be achieved over the next 30, 60, or 90 days; dedicated resource should then deliver this at pace using focused governance to drive accountability.
We have seen organisations (including those who have struggled for years to implement meaningful cyber security improvements) to be most successful at this when they have:
- Used Agile project management techniques and tools (for example, Atlassian’s Jira) to allow them to be reactive to new risks identified and flexible to changing requirements;
- Brought together teams from across the organisation to surge efforts to overcome complex challenges; and,
- Created a sense of pace and urgency by educating employees on the cyber threat and resulting risk to the business.
Step 4: Validate and measure progress at reducing risk
All completed improvement activities should be validated, for example, by using a red team. We have found this is crucial to ensuring that IT changes implemented have effectively remediated the vulnerabilities identified and that there are no adjacent vulnerabilities present that an attacker could exploit.
Progress should also be tracked and reported. This can be done using a broad range of metrics, however, we have found that “cost to the attacker” is highly effective at clearly articulating and demonstrating the risk reduction benefits of security improvement programmes. Typically generated by the red team as a measure of how difficult it is to execute (without detection) techniques likely used by attackers, this provides a higher cadence view of risk exposure, and a pragmatic means to set risk appetite.
Step 5: Address root-causes of vulnerabilities with strategic transformation programmes
Strategic projects should be mobilised to build sustainable security capabilities that address the root-causes of the vulnerabilities identified. We have seen this as key to ensuring vulnerabilities are not re-introduced as a result of IT business-as-usual activities, or by the deployment of new applications and infrastructure. Immediate risk reduction provided by rapid security uplift programmes also provides cover for strategic transformation programmes to design and develop these capabilities, by ensuring that the immediate threat is addressed and that there is an acceptable level of cyber risk exposure in the short-term.
It is also key to ensure that all teams involved are discussing and tracking the same issues when addressing the root-causes of the vulnerabilities identified. Root-cause issues should also be mapped to a common control framework, to allow teams to communicate in a consistent and clear manner.