PICERL-C-01 | Containment: Short Term Containment Strategy | 0 |
PICERL-C-02 | Containment: System Backup Before Remediation | 0 |
PICERL-C-03 | Containment: Long Term Containment | 0 |
PICERL-C1 | Short-Term Containment | 0 |
PICERL-C2 | System Backup | 82 |
PICERL-C3 | Long-Term Containment | 68 |
PICERL-E-01 | Eradication: Root Cause Analysis | 0 |
PICERL-E-02 | Eradication: Removal of Threat Actor Artefacts | 0 |
PICERL-E-03 | Eradication: Credential Reset and Identity Hygiene | 0 |
PICERL-E1 | Threat Removal | 23 |
PICERL-E2 | Root Cause Analysis | 0 |
PICERL-E3 | Backdoor Elimination | 0 |
PICERL-I-01 | Identification: Detection Sources and Alert Triage | 0 |
PICERL-I-02 | Identification: Incident Declaration and Notification | 0 |
PICERL-I-03 | Identification: Evidence Collection and Chain of Custody | 0 |
PICERL-I-04 | Identification: Scope Determination | 1 |
PICERL-I1 | Monitoring and Detection | 0 |
PICERL-I2 | Evidence Collection | 2 |
PICERL-I3 | Incident Classification | 0 |
PICERL-L-01 | Lessons Learned: Post Incident Review | 0 |
PICERL-L-02 | Lessons Learned: Control Improvements and Detection Engineering | 0 |
PICERL-L-03 | Lessons Learned: Metrics and Reporting to Executives | 0 |
PICERL-L1 | Post-Incident Review | 0 |
PICERL-L2 | Documentation and Reporting | 0 |
PICERL-L3 | Plan Improvement | 68 |
PICERL-P-01 | Preparation: Incident Response Policy and Charter | 0 |
PICERL-P-02 | Preparation: Incident Response Team Roles and Skills | 0 |
PICERL-P-03 | Preparation: Jump Kit and Tooling Readiness | 0 |
PICERL-P-04 | Preparation: Logging, Detection, and Telemetry Baseline | 0 |
PICERL-P-05 | Preparation: Tabletop Exercises and Drills | 0 |
PICERL-P1 | Security Policy Review | 0 |
PICERL-P2 | Risk Assessment | 154 |
PICERL-P3 | CSIRT Formation | 106 |
PICERL-P4 | Tools and Documentation | 0 |
PICERL-R-01 | Recovery: Restoration Planning and Sequencing | 0 |
PICERL-R-02 | Recovery: Validation and Monitoring | 0 |
PICERL-R-03 | Recovery: Communications and Stakeholder Updates | 0 |
PICERL-R1 | System Restoration | 42 |
PICERL-R2 | Security Verification | 42 |
PICERL-R3 | Enhanced Monitoring | 0 |
C | Phase 3: Containment | 0 |
C-1 | C-1 Short-term containment: limit the damage fast, from isolating a segment to failing over to other servers | 0 |
C-2 | C-2 Take a forensic image of affected systems with recognised tools before wiping or reimaging, and store it securely | 0 |
C-3 | C-3 Long-term containment: temporary fixes to keep production running while clean systems are rebuilt | 0 |
CHECKLIST | The incident handler's checklist (section 8) | 0 |
E | Phase 4: Eradication | 0 |
E-1 | E-1 Remove malicious content and restore clean systems, usually by full reimaging from known-good images, documenting effort and cost | 0 |
E-2 | E-2 Improve defences so the same cause cannot recur: patch exploited weaknesses, disable unused services, harden | 0 |
HANDBOOK | The handbook: what it is and where PICERL comes from | 0 |
I | Phase 2: Identification | 0 |
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 | 0 |
I-2 | I-2 Notify the team, coordinate with a command centre, assign a primary handler plus a second handler, and document | 0 |
I-3 | I-3 Check Windows hosts for unusual processes, files, registry run keys, network use, scheduled tasks, accounts and event logs | 0 |
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 | 0 |
L | Phase 6: Lessons Learned | 0 |
L-1 | L-1 Complete the documentation and write an incident report giving a play-by-play account | 0 |
L-2 | L-2 Hold a short lessons learned meeting within about two weeks, finalize an executive summary and agree improvements | 0 |
P | Phase 1: Preparation | 0 |
P-a | P-a Written security policy that tells staff what is expected and lets the team judge whether an incident occurred | 0 |
P-b | P-b Incident response plan that ranks incidents by organizational impact | 0 |
P-c | P-c Communication plan: who the team contacts, when and why, including when to involve law enforcement | 0 |
P-d | P-d Document every action taken so records answer who, what, when, where, why and how | 0 |
P-e | P-e Multidisciplinary response team including legal, HR, public relations and IT specialists | 0 |
P-f | P-f Response team can be granted the permissions it needs during an incident and have them removed afterwards | 0 |
P-g | P-g Ready tools in a jump bag: journal, contact list, bootable media, forensic laptop, tool kits, write-blocking duplicators | 0 |
P-h | P-h Regular drills so every team member knows and can perform their duties | 0 |
R | Phase 5: Recovery | 0 |
R-1 | R-1 System owners decide the date and time to restore operations, on the response team's advice | 0 |
R-2 | R-2 Test and verify restored systems, monitor them for a set period with chosen tools, and compare against baselines | 0 |
STATUS | Status and relationship to other incident response guidance | 0 |