SANS Incident Handler's Handbook and PICERL Methodology
The SANS six-phase incident handling process (Preparation, Identification, Containment, Eradication, Recovery, Lessons Learned: PICERL) as set out in the SANS Reading Room Incident Handler's Handbook: what to have in place before an incident, how to decide and scope it, the three containment steps including a forensic image before rebuilding, clean rebuilds and hardening, recovery decided by system owners and monitored against baselines, and a report and review within two weeks. Built from the paper, read in full.
SANS Incident Handler's Handbook and PICERL Methodology is a compliance framework from International (SANS Institute) with 6 domains and 21 controls that map to 161 other frameworks. The largest domains are Phase 1: Preparation – SANS Incident Handler's Handbook and PICERL Methodology (8 controls), Phase 2: Identification – SANS Incident Handler's Handbook and PICERL Methodology (4 controls), Phase 3: Containment – SANS Incident Handler's Handbook and PICERL Methodology (3 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (6)
Phase 1: Preparation – SANS Incident Handler's Handbook and PICERL Methodology
| Code | Title |
|---|---|
| sans-incident-handlers-handbook-and-picerl-methodology::P-a | P-a Written security policy that tells staff what is expected and lets the team judge whether an incident occurred |
| sans-incident-handlers-handbook-and-picerl-methodology::P-b | P-b Incident response plan that ranks incidents by organizational impact |
| sans-incident-handlers-handbook-and-picerl-methodology::P-c | P-c Communication plan: who the team contacts, when and why, including when to involve law enforcement |
| sans-incident-handlers-handbook-and-picerl-methodology::P-d | P-d Document every action taken so records answer who, what, when, where, why and how |
| sans-incident-handlers-handbook-and-picerl-methodology::P-e | P-e Multidisciplinary response team including legal, HR, public relations and IT specialists |
| sans-incident-handlers-handbook-and-picerl-methodology::P-f | P-f Response team can be granted the permissions it needs during an incident and have them removed afterwards |
| sans-incident-handlers-handbook-and-picerl-methodology::P-g | P-g Ready tools in a jump bag: journal, contact list, bootable media, forensic laptop, tool kits, write-blocking duplicators |
| sans-incident-handlers-handbook-and-picerl-methodology::P-h | P-h Regular drills so every team member knows and can perform their duties |
Phase 2: Identification – SANS Incident Handler's Handbook and PICERL Methodology
| Code | Title |
|---|---|
| sans-incident-handlers-handbook-and-picerl-methodology::I-1 | I-1 Detect and decide whether an event is an incident using logs, error messages, IDS and firewall data, and report it promptly |
| sans-incident-handlers-handbook-and-picerl-methodology::I-2 | I-2 Notify the team, coordinate with a command centre, assign a primary handler plus a second handler, and document |
| sans-incident-handlers-handbook-and-picerl-methodology::I-3 | I-3 Check Windows hosts for unusual processes, files, registry run keys, network use, scheduled tasks, accounts and event logs |
| sans-incident-handlers-handbook-and-picerl-methodology::I-4 | I-4 Check Unix hosts for root processes, unlinked files, SUID and large files, promiscuous interfaces, cron jobs, UID 0 accounts and logs |
Phase 3: Containment – SANS Incident Handler's Handbook and PICERL Methodology
| Code | Title |
|---|---|
| sans-incident-handlers-handbook-and-picerl-methodology::C-1 | C-1 Short-term containment: limit the damage fast, from isolating a segment to failing over to other servers |
| sans-incident-handlers-handbook-and-picerl-methodology::C-2 | C-2 Take a forensic image of affected systems with recognised tools before wiping or reimaging, and store it securely |
| sans-incident-handlers-handbook-and-picerl-methodology::C-3 | C-3 Long-term containment: temporary fixes to keep production running while clean systems are rebuilt |
Phase 4: Eradication – SANS Incident Handler's Handbook and PICERL Methodology
| Code | Title |
|---|---|
| sans-incident-handlers-handbook-and-picerl-methodology::E-1 | E-1 Remove malicious content and restore clean systems, usually by full reimaging from known-good images, documenting effort and cost |
| sans-incident-handlers-handbook-and-picerl-methodology::E-2 | E-2 Improve defences so the same cause cannot recur: patch exploited weaknesses, disable unused services, harden |
Phase 5: Recovery – SANS Incident Handler's Handbook and PICERL Methodology
| Code | Title |
|---|---|
| sans-incident-handlers-handbook-and-picerl-methodology::R-1 | R-1 System owners decide the date and time to restore operations, on the response team's advice |
| sans-incident-handlers-handbook-and-picerl-methodology::R-2 | R-2 Test and verify restored systems, monitor them for a set period with chosen tools, and compare against baselines |
Phase 6: Lessons Learned – SANS Incident Handler's Handbook and PICERL Methodology
| Code | Title |
|---|---|
| sans-incident-handlers-handbook-and-picerl-methodology::L-1 | L-1 Complete the documentation and write an incident report giving a play-by-play account |
| sans-incident-handlers-handbook-and-picerl-methodology::L-2 | L-2 Hold a short lessons learned meeting within about two weeks, finalize an executive summary and agree improvements |
Your Compliance Coverage
If you comply with SANS Incident Handler's Handbook and PICERL Methodology, you already cover:
South Korea ISMS-P
13%
8 controls mapped
Compare →PSD2 SCA
11%
7 controls mapped
Compare →PCI PIN Security
11%
7 controls mapped
Compare →+ 158 more: FFIEC IT Examination Handbook (11%), PCI P2PE (11%)
See all 161 mapped frameworks ↓Maps to 161 other frameworks
Coverage is not the same as your position
This page shows what SANS Incident Handler's Handbook and PICERL Methodology overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is SANS Incident Handler's Handbook and PICERL Methodology and who does it apply to?
SANS Incident Handler's Handbook and PICERL Methodology is a compliance framework from International (SANS Institute) with 6 domains and 21 controls. The SANS six-phase incident handling process (Preparation, Identification, Containment, Eradication, Recovery, Lessons Learned: PICERL) as set out in the SANS Reading Room Incident Handler's Handbook: what to have in place before an incident, how to decide and scope it, the three containment steps including a forensic image before rebuilding, clean rebuilds and hardening, recovery decided by system owners and monitored against baselines, and a report and review within two weeks. Built from the paper, read in full. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does SANS Incident Handler's Handbook and PICERL Methodology actually require?
SANS Incident Handler's Handbook and PICERL Methodology has 21 controls organised across 6 domains. The largest domains are Phase 1: Preparation – SANS Incident Handler's Handbook and PICERL Methodology (8 controls), Phase 2: Identification – SANS Incident Handler's Handbook and PICERL Methodology (4 controls), Phase 3: Containment – SANS Incident Handler's Handbook and PICERL Methodology (3 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of SANS Incident Handler's Handbook and PICERL Methodology do I already cover?
SANS Incident Handler's Handbook and PICERL Methodology maps to 161 other compliance frameworks. The top mapping partners are South Korea ISMS-P (13% coverage), PSD2 SCA (11% coverage), PCI PIN Security (11% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement SANS Incident Handler's Handbook and PICERL Methodology?
Start your SANS Incident Handler's Handbook and PICERL Methodology compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about SANS Incident Handler's Handbook and PICERL Methodology requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 21 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,121 frameworks.
Get Started Free →Free forever, no credit card required