Remote Compromise

What? A scenario-driven testing approach to simulate remote attackers aiming to breach perimeter defenses via remote infrastructure weaknesses or via targeted attacks against user end-point systems.

How? We learn the current threat model, agree on scenarios to simulate with time-limits and terms, then play each out, documenting observations, findings, and countermeasures. Scenarios can include:

• Network Perimeter Attacks: Perform OSINT and map internet attack surface then attempt to gain access to sensitive system data or establish a network foothold.
• Phishing Simulations: Measure specific security controls and awareness training for users and high-value targets (spear-phishing campaigns) that could result in compromised credentials and malware.

When? Periodically (e.g. quarterly, bi-annually) to incrementally measure and improve defences; Ad-hoc to verify major infrastructure changes; Annually to get the most out of penetration testing obligations.

Assumed Breach

What? A scenario-driven testing approach that assumes breach of specific network assets aiming to identify weaknesses and gaps in security controls in place to protect business critical assets.

How? We understand the high-level threat model, agree on scenarios, time limits, and terms; then play out each scenario, documenting the approaches, techniques, findings, and countermeasures. Scenarios can include:

• Internal Endpoint Pivoting: Understand lateral movement, information disclosure and elevation of privilege attacks for cloud and enterprise networks.
• Malicious Insider Attacks: Simulate a malicious insider with privileged access (e.g. developer or network engineer), to identify weaknesses that enable a breach of important assets.

When? Periodically (e.g. quarterly or bi-annually) to incrementally measure and improve defences; Ad-hoc testing to verify recent changes or new controls; As an add-on to specific security auditing services.

1. Initial Chat

An informal chat to learn about the project requirements, goals, and timing.

We like to ensure we're the right fit for a project before going further.

2. Scoping

We hold a meeting to understand project specifics in more detail to create a draft proposal.

Each proposal is tailored to the unique requirements of every project we do.

3. Preparation

We ensure all materials and communications channels are setup in advance so we can hit the ground running.

We loop in all key stakeholders and host a kick-off call to ensure everyone is across project specifics.

4. Delivery

We follow our internal methodologies for each activity of the project with regular updates throughout.

Project activities are prioritised to meet objectives allowing us to focus on what's important.

5. Handover

We hold a close-down meeting to present draft deliverables for initial review.

We step through detailed findings, discuss the root-cause of issues, and summarise recommendations.

6. Closedown

We ensure final deliverables meet all requirements and expectations.

As part of our project data safeguarding processes, we securely archive the project on completion.