During and after
Cloud Response
Investigate, contain and regain control.
Specialist-led investigation when an incident is active or something feels wrong.
Three routes
Start from what you know.
You do not need to know whether a compromise occurred to start the right conversation.
Active or likely
Incident Response
Establish scope and coordinate investigation, containment and removal of attacker access.
Incident Response →One lead
Targeted Investigation
Examine an agreed hypothesis within a defined scope and report findings and limitations.
Targeted Investigation →A broad concern
Compromise Assessment
Examine the agreed environment and available evidence for signs of compromise.
Compromise Assessment →
Why cloud response is different
Containment is not eviction.
Revoking sessions and rotating keys stops the bleeding. In cloud the attacker often stays as configuration: an OAuth grant, a federated credential, a mailbox rule, a new MFA method. We stay until every persistence mechanism found in scoping is removed and verified, not until the alerts stop.
Containing activity is not the same as establishing that attacker access has been removed.
See an investigation, level by level. One compromised identity, three platforms, 159 resources, down to the log line that proves it. Explore an incident →
Not sure which route fits?
Tell us what is happening. We’ll point you to the right first step.