International (SANS Institute)

SANS Incident Handler's Handbook and PICERL Methodology

70 controls. 175 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

70 controls 175 frameworks share controls with it International (SANS Institute) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
PICERL-C-01Containment: Short Term Containment Strategy0
PICERL-C-02Containment: System Backup Before Remediation0
PICERL-C-03Containment: Long Term Containment0
PICERL-C1Short-Term Containment0
PICERL-C2System Backup82
PICERL-C3Long-Term Containment68
PICERL-E-01Eradication: Root Cause Analysis0
PICERL-E-02Eradication: Removal of Threat Actor Artefacts0
PICERL-E-03Eradication: Credential Reset and Identity Hygiene0
PICERL-E1Threat Removal23
PICERL-E2Root Cause Analysis0
PICERL-E3Backdoor Elimination0
PICERL-I-01Identification: Detection Sources and Alert Triage0
PICERL-I-02Identification: Incident Declaration and Notification0
PICERL-I-03Identification: Evidence Collection and Chain of Custody0
PICERL-I-04Identification: Scope Determination1
PICERL-I1Monitoring and Detection0
PICERL-I2Evidence Collection2
PICERL-I3Incident Classification0
PICERL-L-01Lessons Learned: Post Incident Review0
PICERL-L-02Lessons Learned: Control Improvements and Detection Engineering0
PICERL-L-03Lessons Learned: Metrics and Reporting to Executives0
PICERL-L1Post-Incident Review0
PICERL-L2Documentation and Reporting0
PICERL-L3Plan Improvement68
PICERL-P-01Preparation: Incident Response Policy and Charter0
PICERL-P-02Preparation: Incident Response Team Roles and Skills0
PICERL-P-03Preparation: Jump Kit and Tooling Readiness0
PICERL-P-04Preparation: Logging, Detection, and Telemetry Baseline0
PICERL-P-05Preparation: Tabletop Exercises and Drills0
PICERL-P1Security Policy Review0
PICERL-P2Risk Assessment154
PICERL-P3CSIRT Formation106
PICERL-P4Tools and Documentation0
PICERL-R-01Recovery: Restoration Planning and Sequencing0
PICERL-R-02Recovery: Validation and Monitoring0
PICERL-R-03Recovery: Communications and Stakeholder Updates0
PICERL-R1System Restoration42
PICERL-R2Security Verification42
PICERL-R3Enhanced Monitoring0
CPhase 3: Containment0
C-1C-1 Short-term containment: limit the damage fast, from isolating a segment to failing over to other servers0
C-2C-2 Take a forensic image of affected systems with recognised tools before wiping or reimaging, and store it securely0
C-3C-3 Long-term containment: temporary fixes to keep production running while clean systems are rebuilt0
CHECKLISTThe incident handler's checklist (section 8)0
EPhase 4: Eradication0
E-1E-1 Remove malicious content and restore clean systems, usually by full reimaging from known-good images, documenting effort and cost0
E-2E-2 Improve defences so the same cause cannot recur: patch exploited weaknesses, disable unused services, harden0
HANDBOOKThe handbook: what it is and where PICERL comes from0
IPhase 2: Identification0
I-1I-1 Detect and decide whether an event is an incident using logs, error messages, IDS and firewall data, and report it promptly0
I-2I-2 Notify the team, coordinate with a command centre, assign a primary handler plus a second handler, and document0
I-3I-3 Check Windows hosts for unusual processes, files, registry run keys, network use, scheduled tasks, accounts and event logs0
I-4I-4 Check Unix hosts for root processes, unlinked files, SUID and large files, promiscuous interfaces, cron jobs, UID 0 accounts and logs0
LPhase 6: Lessons Learned0
L-1L-1 Complete the documentation and write an incident report giving a play-by-play account0
L-2L-2 Hold a short lessons learned meeting within about two weeks, finalize an executive summary and agree improvements0
PPhase 1: Preparation0
P-aP-a Written security policy that tells staff what is expected and lets the team judge whether an incident occurred0
P-bP-b Incident response plan that ranks incidents by organizational impact0
P-cP-c Communication plan: who the team contacts, when and why, including when to involve law enforcement0
P-dP-d Document every action taken so records answer who, what, when, where, why and how0
P-eP-e Multidisciplinary response team including legal, HR, public relations and IT specialists0
P-fP-f Response team can be granted the permissions it needs during an incident and have them removed afterwards0
P-gP-g Ready tools in a jump bag: journal, contact list, bootable media, forensic laptop, tool kits, write-blocking duplicators0
P-hP-h Regular drills so every team member knows and can perform their duties0
RPhase 5: Recovery0
R-1R-1 System owners decide the date and time to restore operations, on the response team's advice0
R-2R-2 Test and verify restored systems, monitor them for a set period with chosen tools, and compare against baselines0
STATUSStatus and relationship to other incident response guidance0

Tell me when SANS Incident Handler's Handbook and PICERL Methodology files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for SANS Incident Handler's Handbook and PICERL Methodology, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition