Incident Severity Classification
| Severity | Definition | Response Time | Escalation |
|---|---|---|---|
| P1 - Critical | Data breach, ransomware, full outage | Immediate (< 15 min) | CEO + Legal |
| P2 - High | Partial outage, suspected breach, malware detected | < 1 hour | IT Manager + HR |
| P3 - Medium | Single user compromise, phishing attempt | < 4 hours | IT Manager |
| P4 - Low | Suspicious email, policy violation | < 24 hours | IT Staff |
Phase 1: Detection & Identification
Detection Sources
- Antivirus / EDR alert
- User report ("I clicked a suspicious link")
- Monitoring alert (unusual login, data transfer spike)
- External notification (vendor, CERT-In advisory)
Identification Checklist
- Confirm the incident is real (not a false positive)
- Classify severity using the matrix above
- Identify affected systems, users, and data
- Document: time of detection, reporter, initial symptoms
- Open incident ticket in ITSM with severity tag
- Notify incident response team per severity level
Phase 2: Containment
Immediate Containment (< 30 minutes for P1/P2)
- Isolate affected systems from network (disable NIC or quarantine in MDM)
- Disable compromised user accounts in AD/Google Workspace
- Block malicious IPs/domains at firewall
- Preserve evidence: take memory dump and disk image before any changes
- Do NOT power off affected systems (destroys volatile evidence)
Short-Term Containment
- Deploy clean backup systems if available
- Implement temporary access controls
- Notify affected users with instructions (do not use affected device)
- Engage cyber insurance provider if applicable
Phase 3: Eradication
- Identify root cause (phishing, unpatched vulnerability, insider threat, etc.)
- Remove malware using EDR tools - verify with second scan
- Patch exploited vulnerability or misconfiguration
- Reset all passwords for affected accounts (and any shared credentials)
- Revoke and reissue API keys, certificates, and tokens
- Scan all systems in the same network segment
- Verify no persistence mechanisms remain (scheduled tasks, startup entries, backdoors)
Phase 4: Recovery
- Restore systems from clean backup (verify backup integrity before restore)
- Re-enable user accounts with new credentials
- Monitor restored systems intensively for 72 hours
- Gradually restore network access (do not reconnect all at once)
- Confirm business operations are fully restored
- Notify affected customers/partners if data was exposed (PDPB compliance)
Phase 5: Post-Incident Review
Conduct within 5 business days of incident closure.
Review Questions
- 1What was the root cause?
- 2How was it detected - and could it have been detected earlier?
- 3What was the total business impact (downtime, data loss, cost)?
- 4Were the response procedures followed? What gaps were found?
- 5What controls would have prevented this incident?
Output
- Incident report (timeline, impact, root cause, actions taken)
- Updated runbook with lessons learned
- Security control improvements with owner and deadline
- Training requirement identified (if human error was a factor)
Communication Templates
Internal Alert (P1/P2)
SECURITY INCIDENT ALERT - [Severity]
We have detected a security incident affecting [systems/users]. IT is actively responding. Please do not use [affected systems] until further notice. Do not discuss this externally. Updates every 30 minutes.
Customer Notification (if data exposed)
Dear [Customer], we are writing to inform you that we detected a security incident on [date] that may have affected [data type]. We have contained the incident and taken the following steps: [actions]. We recommend you [customer actions]. Contact: [[email protected]]
Key Contacts
| Role | Name | Phone | |
|---|---|---|---|
| IT Manager | |||
| CEO / MD | |||
| Legal Counsel | |||
| Cyber Insurance | |||
| CERT-In (national) | [email protected] |