Adversary Emulation and Response
Breach Assessment
Investigate suspected unauthorised activity and establish the supported scope of system or data exposure. Findings distinguish accessible information from evidence of actual access, transfer or misuse.
01 / Overview
Assessment objectives and control obligations
Breach assessment defines the investigative period, relevant systems and evidential questions before preserving available records. Correlation reconstructs affected identities, access events and potential disclosure across endpoint, cloud and repository sources. Log expiration, incomplete collection and historical configuration uncertainty remain explicit analytical constraints.
Findings distinguish accessible data from substantiated access, transfer or misuse. Supported record estimates and confidence statements inform containment and notification deliberations with the organisation’s legal advisers. Additional collection is recommended where it could materially alter impact characterisation; missing evidence may prevent either confirmation or exclusion of specific activity.
02 / Technical analysis
Failure mechanisms and security implications
No alert does not prove no breach. A secure current configuration does not establish the historical state. We correlate independent sources and distinguish confirmed activity from possible exposure.
03 / Scope
Technical coverage and authorisation boundaries
Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.
- Access reconstruction
- Account, endpoint, cloud and repository activity.
- Data impact
- Data categories, supported record estimates and transfer evidence.
- Decision support
- Containment facts, root cause and unresolved questions.
- Supporting tools
- Environment-appropriate instrumentation may include Forensic acquisition, Log analysis, Data classification, Timeline analysis. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.
04 / Methodology
Investigation and validation methodology
Investigation separates confirmed facts from working hypotheses and prioritises decisions that protect the business while preserving useful evidence. Activity is coordinated with the incident owner.
01
Authority and triage
Initial coordination
We confirm the incident owner, access permissions, known facts and immediate risks, prioritising time sensitive evidence.
02
Preserve relevant records
Confirm authority, time coverage and sources at risk of loss.
03
Test investigative explanations
Reconstruct activity and state confidence, alternatives and gaps.
04
Recovery and closure
Agreed exit criteria
We support eradication and staged recovery, monitoring requirements and open questions, with closure based on agreed evidence and business decisions.
05 / Assessment options
Access models and evidential confidence
Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.
- Black box
- Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
- Grey box
- Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
- White box
- Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.
06 / Deliverables
Decision-support and verification deliverables
Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.
Executive summary
The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.
Technical findings
Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.
Coverage and limitations
The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.
Treatment and retest status
Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.
Service specific evidence
A supported chronology and data impact assessment inform authorised decision makers.
07 / References
Applicable technical references
References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.
- NIST incident response recommendations
- Revision 3 integrates preparation, detection, response, recovery and improvement with CSF 2.0 risk management. The reference does not prescribe identical actions for every incident.
- NIST forensic techniques guidance
- The forensic guide supports collection, examination, analysis and reporting. Current platform methods, evidence volatility and jurisdictional requirements supplement this foundation.
- Hong Kong privacy framework
- The Privacy Commissioner explains the PDPO and data protection principles. Technical findings support the organisation and its legal advisers; they do not replace a legal compliance determination.
08 / Safeguards
Operational safeguards and evidence governance
Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.
Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.
Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.
Missing records may prevent confirmation or exclusion of activity. Technical findings do not determine every legal notification duty.
09 / Suitability
Commissioning criteria
Use for suspected compromise or unexplained exposure where historical evidence must be assessed.
Next step
Define the assessment you need
Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.
- Confidentiality first
A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.
- Scope and cost in writing
Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.
- Answered by the delivery team
The consultants who scope an engagement are the consultants who perform it and explain the result to your team.
