I scoped offensive work around the ways an attacker could reach a client’s important systems and what the organisation could detect once access was gained. Healthcare, cargo, hospitality, MSP, trading and private-equity environments shared common intrusion techniques but had different assets and operational constraints.
I began with blind external attack-surface mapping and perimeter probing to establish the outside view. That discovery informed priorities for layered email protection, common Active Directory attack paths, critical-component updates and endpoint and network visibility.
I also performed internal and assumed-breach assessments to examine weaknesses from inside the environment. My SOC and incident-response experience helped connect offensive findings with the evidence a responder would need and the actions the relevant teams would have to take.
Depending on the environment, the scope extended into continuing web-application testing, software-development processes and repeated attack-surface mapping. A private-healthcare scope included AI chatbot testing requirements. I carried that environment-specific context into the assessment, reporting and control recommendations.
Methods, evidence & technical decisions
Starting with the business and its systems
I discussed the environment and threats with client managers and executives before defining testing priorities. Settings included healthcare, cargo, hospitality, MSPs, trading, private equity and a humanitarian organisation. A healthcare assessment included an AI chatbot application in its testing requirements.
Open this detail ↗Establishing the external attack surface
I used blind external mapping and perimeter probing to understand what an outside party could discover and approach. Those observations informed subsequent testing priorities and the comparison between the exposed surface and intended scope.
Open this detail ↗Prioritising email, identity and critical systems
I considered layered email protection, common Active Directory attacks and the update state of critical components. These priorities shaped the assessment and control recommendations.
Open this detail ↗Connecting findings to detection and response
I considered EDR coverage and network visibility alongside the intrusion techniques under assessment. SOC and incident-response experience helped me ask what the organisation could observe, investigate and act on, and turn those questions into assessment priorities and control recommendations.
Open this detail ↗Assessing from an internal foothold
I performed internal and assumed-breach assessments to examine weaknesses from within the environment. The findings informed response planning and a threat model grounded in that client’s systems and likely intrusion paths.
Open this detail ↗Revisiting exposure as systems changed
Where required, scope included continuing web-application testing, examination of software-development processes and repeated attack-surface mapping. These activities kept assessment planning connected to changes in systems and exposure.
Open this detail ↗Skills used in this work