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.

IdentityReachesEvidence Compromisedidentity Mailbox Files App consent Mailbox access recorded File access not keptfor the period needed Consent grant recorded Act first · remove the app consent Identity Compromised identity ReachesEvidence Mailbox Files App consent Mailbox access recorded File access not keptfor the period needed Consent grant recorded Act first · remove the app consent
Illustrative scenario · not a customer result

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.

InvictusResponse Readiness
Sample organisation · readiness review

Prioritized plan

Sample · fictional data
Response Readiness · Prioritized plan · p. 4Sample · fictional data
FindingConsequence in an incidentPriorityNext step
Users can consent to third-party appsAn attacker-controlled app could keep mailbox access after a password resetFirstRequire admin approval for app consent
Mailbox activity is not kept for the period you would needLimits what you could establish about mail accessFirstExtend retention for the agreed sources
Admin roles are assigned permanentlyA stolen session for a permanent Global Administrator can change tenant-wide settingsNextMove 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.

  1. ScopeAgree the environment and the questions.
  2. ReviewExamine the controls and the evidence.

What would your next incident test?

Academy →Cloud Response →