Before an incident
Forensic Readiness Review
Could you reconstruct what happened?
Check whether the evidence your incident questions need is recorded, retained and reachable.
Three checks
Recorded. Retained. Reachable.
Recorded
Does the activity produce usable evidence?
Retained
Does it cover the period you need?
Reachable
Can authorized responders retrieve it in time?
Settings show what should be recorded. A retrieval sample shows what is. We sample where the scope includes it.
Sample coverage
A log exists. Does it answer the question?
For an agreed scenario, we map the question to the source, the scope assessed, the period covered and what stays unknown.
Sample organisation · Azure and Microsoft 365
Evidence coverage
Sample · fictional data| Question | Source | Period assessed | Still unknown |
|---|---|---|---|
| Which identity accessed these files? | File activity records | 1 Mar to 31 May 2026 | Access before 1 Mar 2026 |
| Was a mailbox forwarding rule created? | Mailbox audit records | 1 Mar to 31 May 2026 | Nothing within the period assessed |
Specialist noteAccess before 1 March can’t be reconstructed. Retention is the first fix.
What changes
Make the gaps explicit.
- ChooseAgree the incident scenarios that matter for your environment.
- ExamineCheck the sources each scenario depends on.
- VerifyTest agreed samples to confirm the evidence is usable.
- PrioritizeRank the gaps and the changes that close them, with a specialist.
It doesn’t establish whether a compromise occurred. That is a Compromise Assessment →
Prepare the record before you need it.
Can the team act on it? Explore the Response Readiness Review →
