Ransomware Response
Coordinate rapid containment, evidence preservation, business continuity, and clean recovery during ransomware events.
On this page · 4 sections
Operating context
Ransomware response balances stopping spread with maintaining safety-critical services and forensic visibility. Decisions require executive, legal, technical, and continuity coordination.
- Define the security decision that ransomware response must support.
- Assign accountable owners, escalation paths, service levels, and privacy boundaries.
- Measure signal quality, response consistency, operational cost, and improvement over time.
Operational workflow
- 01
Establish scope, dependencies, normal behavior, and a documented baseline.
- 02
Collect the minimum telemetry and context needed for ransomware response.
- 03
Correlate independent signals and state confidence before taking disruptive action.
- 04
Document the decision, evidence, containment or control action, and responsible owner.
- 05
Review the outcome, tune the process, and validate the improvement with a safe test.
Signals, evidence & decisions
| Signal or artifact | Decision it supports |
|---|---|
| affected-host and identity timeline | Establish event sequence and affected scope. |
| encryption, exfiltration, and lateral-movement signals | Confirm identity, asset, or control context. |
| backup integrity and recovery validation | Support containment, recovery, or tuning. |
Record source, timestamp, collection method, confidence, owner, and disposition. Preserve the smallest useful evidence set and document any uncertainty.
Implementation & improvement
- Predefine isolation authority and critical-system exceptions.
- Protect backup control planes and credentials.
- Rebuild from trusted sources and rotate exposed secrets.