Before an incident

Forensic Readiness Review

Could you reconstruct what happened?

Check whether the evidence your incident questions need is recorded, retained and reachable.

Incident questionWhich identity accessed these files? SourcePeriod needed Sign-in records File activity Sharing eventsNot recorded Unknown · file access before 1 Mar 2026
Illustrative · sources and periods are examples

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.

InvictusForensic Readiness Review
Sample organisation · Azure and Microsoft 365

Evidence coverage

Sample · fictional data
Forensic Readiness Review · Evidence coverage · p. 5Sample · fictional data
QuestionSourcePeriod assessedStill unknown
Which identity accessed these files?File activity records1 Mar to 31 May 2026Access before 1 Mar 2026
Was a mailbox forwarding rule created?Mailbox audit records1 Mar to 31 May 2026Nothing within the period assessed
Confidential · prepared for the sample organisationp. 5

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 →