ProcedureChecked
A ransomware incident response procedure lists the technical checks a responder runs, such as sessions, logs and persistence
01
What is a ransomware incident response procedure?
It is the step-level instruction that sits under the plan: what to open, what to look for and what to record. The plan assigns authority; the procedure tells a responder which logs to read. The guide's Containment and Eradication section is its core.
02
What techniques does incident response use against ransomware attacks?
Responders use triage, imaging, log review, threat hunting, session and file analysis, network capture and persistence analysis. The guide describes each in terms an administrator can run.
| Technique | What to do | Why |
|---|---|---|
| Triage | Rank affected systems against the critical asset list; note unaffected systems | Orders recovery |
| Imaging | Take a system image and memory capture from a sample of workstations, servers, virtual and cloud servers; collect logs and precursor malware samples | Preserves evidence; volatile data is lost on power-off |
| Threat hunting | Look for new or escalated AD accounts, odd VPN logins, tools that impair backups and shadow copies (bcdedit, fsutil, vssadmin, wbadmin, wmic), Cobalt Strike, unexpected remote management software, PowerShell and PsTools use, credential dumping, odd endpoint-to-endpoint traffic | Finds the route and the scope |
| Data theft checks | Look for abnormal outbound data on any port and for tunneling and sync tools such as Chisel, Cloudflared and Rclone | Tells you whether extortion is double |
| Server-side encryption identification | Review sessions and open files; file properties of encrypted files and ransom notes; the TerminalServices-RemoteConnectionManager log for RDP connections; Windows Security and SMB logs; packet capture filtered for files being written or renamed | Finds the infected workstation encrypting a server |
| Persistence analysis | Outside-in: rogue accounts, backdoors on perimeter systems, exploited external vulnerabilities. Inside-out: implants and living-off-the-land use of commercial tools, PsExec and PowerShell | Prevents a repeat the next week |
| Cloud checks | Snapshot volumes; alert on changes to IAM, network security and data protection resources; automate response to open firewall rules | Preserves evidence and blocks tampering |
03
What is a ransomware response procedure for the technical team, in order?
In order, the procedure for the technical team is seven steps, each drawn from the guide's checklist.
- Run the first three guide steps: isolate, triage, examine.
- Capture images and memory from a sample before any rebuild.
- Hunt using the list above, and record every finding in the decision log.
- Identify the accounts and systems involved in the initial breach, including email accounts.
- Cut access: disable VPN, remote access servers, single sign-on and public-facing assets where needed.
- Search for persistence, then rebuild in priority order from standard images.
- Reset passwords only after the environment is clean, then bring systems back in stages.
Related pages
Sources
Read 16 November 2026, the day this page was last reviewed, unless a line shows another date.
- CISA, MS-ISAC, FBI and NSA: #StopRansomware Guide (September 2023 edition, page read 16 November 2026)
- NIST IR 8374r1, full text (June 2026)
Last reviewed 16 November 2026.