Before an incident
Response Readiness
See the gaps before the incident.
We investigate cloud incidents. Readiness examines what an attacker could reach, what your evidence would show and whether your team could act.
Three questions
One incident, three questions
Start with one question, or combine them.
Sample output
A prioritized plan. Not another score.
Each finding says what it means in an incident and what to change first. The limits are stated.
Sample organisation · readiness review
Prioritized plan
Sample · fictional dataResponse Readiness · Prioritized plan · p. 4Sample · fictional data
| Finding | Consequence in an incident | Priority | Next step |
|---|---|---|---|
| Users can consent to third-party apps | An attacker-controlled app could keep mailbox access after a password reset | First | Require admin approval for app consent |
| Mailbox activity is not kept for the period you would need | Limits what you could establish about mail access | First | Extend retention for the agreed sources |
| Admin roles are assigned permanently | A stolen session for a permanent Global Administrator can change tenant-wide settings | Next | Move admin roles to just-in-time activation |
Scope: one Microsoft 365 tenant, agreed scenarios. Not assessed: on-premises Active Directory.
Confidential · prepared for the sample organisationp. 4
Specialist noteStart here. Everything below depends on it.
How it runs
From agreed scope to a dated plan.
- ScopeAgree the environment and the questions.
- ReviewExamine the controls and the evidence.
