Study guide
Incident Classification and Categorization
CISM Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISM Orientation and 2026 Exam Facts
Current CISM Exam Facts The November 2026 Outline Change The Security Manager Mindset Scaled Score and Preliminary Status Registration Scheduling and Fees Certification After Passing
2 Chapter 2: Information Security Governance
Organizational Culture and Governance Signals Legal, Regulatory, and Contractual Requirements Structures, Roles, and Responsibilities Information Security Strategy Development Governance Frameworks and Standards Strategic Planning, Budgets, and Business Cases
3 Chapter 3: Information Security Risk Management
Emerging Risk and Threat Landscape Vulnerability and Control Deficiency Analysis Risk Assessment and Analysis Risk Treatment and Response Options Risk and Control Ownership Risk Monitoring and Reporting
4 Chapter 4: Information Security Program Development
Program Resources: People, Tools, and Technologies Information Asset Identification and Classification Industry Standards and Frameworks Policies, Procedures, and Guidelines Information Security Program Metrics Program Alignment with Strategy
5 Chapter 5: Program Management and Control Execution
Security Control Design and Selection Control Implementation and Integration Control Testing and Evaluation Security Awareness and Training External Services and Supplier Management Program Communications and Reporting
6 Chapter 6: Incident Management Readiness
Incident Response Plan Business Impact Analysis Business Continuity Plan Disaster Recovery Plan Incident Classification and Categorization Incident Training Testing and Evaluation
7 Chapter 7: Incident Management Operations
Incident Management Tools and Techniques Incident Investigation and Evaluation Incident Containment Methods Incident Response Communications Incident Eradication and Recovery Post-Incident Review Practices
8 Chapter 8: Supporting Governance Tasks
Internal and External Influences Maintaining Security Strategy Governance Framework Maintenance Corporate Governance Integration Policy Direction and Standards Business Cases for Security Investment
9 Chapter 9: Cross-Domain Risk and Program Decisions
Senior Leadership Commitment Responsibilities and Lines of Authority Program Effectiveness Reporting Risk Process Oversight Threat and Vulnerability Participation Risk Appetite and Treatment Decisions
10 Chapter 10: External Parties Data and Emerging Technology
Information Security Requirements in Contracts Monitoring External Parties Information Asset Lifecycle Thinking Cloud SaaS and Provider Risk AI, Blockchain, and Ransomware Context Compliance and Control Evidence
11 Chapter 11: CISM Practice Strategy
Domain-Weighted Study Allocation Management-Focused Answer Choices One-Best-Answer Elimination Timed Four-Hour Practice Using Domain Feedback Correctly Retake, Rescore, and Post-Exam Feedback
12 Chapter 12: Final Review and Exam Day Readiness
Two-Week Final Review Plan Exam Day Rules and Identification Remote Proctoring Readiness Preliminary Status Versus Official Score Application Window, Experience, and Ethics CPE Maintenance After Certification
Incident Classification and Categorization
Key Takeaways Explain This Topic AI
Classification assigns severity/priority (how bad, how fast to respond); categorization assigns type (what kind of incident).
Severity is set from business impact and urgency, driving escalation paths, notification timing, and resource allocation.
Consistent, pre-defined criteria prevent under- or over-reacting and make metrics comparable across incidents.
An event is not yet an incident; declaration follows triage against defined thresholds.
Last updated: June 2026
Classification Versus Categorization
These two terms are tested as a distinction, so keep them separate. Classification assigns a severity or priority , how damaging the incident is and how urgently it must be handled, while categorization assigns a type , what kind of incident it is (malware, phishing, unauthorized access, denial of service, data loss, insider misuse, physical). Classification governs how fast and how high you respond; categorization governs which playbook and skills you apply.
Before either step, recall that an event (any observable occurrence) becomes an incident only after triage confirms it adversely affects, or threatens, confidentiality, integrity, or availability. Declaration against defined thresholds is what activates the response. Treating every alert as a full incident exhausts the team; ignoring real ones is worse.
Severity Driven by Business Impact
CISM insists severity be set from business impact and urgency , not from how interesting the technology is. A defaced marketing page may be low severity; a 200-record exposure of regulated health data is high. A representative severity scale:
- Severity Business impact Typical response
- Critical (Sev 1) Major outage, regulated-data breach, safety risk Immediate, executive + legal notified
- High (Sev 2) Significant impact on key processes Rapid, management notified
- Medium (Sev 3) Limited impact, contained Standard handling within SLA
- Low (Sev 4) Minimal/no business impact Routine, logged and monitored
The practical formula many programs use: Priority = Impact × Urgency . High impact plus high urgency yields the highest priority and the fastest escalation.
Why Consistent Criteria Matter
Pre-defined, written classification and categorization criteria deliver four management benefits the exam rewards:
Proportionate response: The team neither over-reacts to noise nor under-reacts to a serious breach, because thresholds are decided in advance, not in the heat of the moment.
Correct escalation and notification: Severity tiers map to who is told and when, which is critical where breach-notification deadlines apply (for example, GDPR's 72-hour authority notification window). Misclassifying a reportable breach as low severity can cause a missed legal deadline.
Resource allocation: Limited responders are pointed at the highest-priority incidents first.
Comparable metrics: Consistent labels let management trend incident volume by type and severity, measure mean time to detect and respond, and report meaningful KPIs to the board.
Common Traps
Letting the responder's intuition set severity: ISACA prefers a documented matrix applied consistently over individual judgment that varies by person and mood.
Classifying by technology rather than impact: "It was on a server" is not severity; what the disruption does to the business is.
Static classification: Severity can change as scope is discovered, a "medium" containment may be re-classified "critical" once exfiltration of regulated data is confirmed. The plan should allow re-classification.
Confusing category with severity: A phishing email (category) can be low or critical severity depending on whether credentials were captured and used.
Worked scenario: A help-desk ticket reports a single workstation running slowly. Triage finds it is beaconing to a known command-and-control host on the finance network. Categorization: malware/compromise; classification escalates from low to critical because the business impact, potential access to financial systems, is now high, triggering executive and legal notification per the IRP.
Triage, Escalation, and the Notification Clock
Triage is the gate between an event and a declared incident. The team evaluates the alert against documented criteria: is it real (not a false positive), does it affect confidentiality, integrity, or availability, and what is its likely scope? Only confirmed incidents proceed into the lifecycle; this discipline conserves limited responders and prevents alert fatigue from burying the serious cases.
Mapping Severity to Escalation
Classification is only useful if each severity tier is wired to concrete actions. A mature program defines, in advance, who is notified and how fast for each level:
- Severity Notify Target acknowledgment
- Critical CISO, executives, legal, comms; possibly board Minutes
- High Security manager, affected business owner Within ~1 hour
- Medium On-call analyst, team lead Within shift / SLA
- Low Logged, monitored, routine queue Best effort
This mapping is what makes classification actionable. The exam rewards the manager who has these thresholds pre-agreed so that escalation is automatic rather than debated mid-crisis.
Legal and Regulatory Notification Drivers
Classification often determines whether external notification obligations are triggered. Many regimes impose hard deadlines: the EU GDPR requires notifying the supervisory authority within 72 hours of becoming aware of a qualifying personal-data breach; various U.S. state and sector laws (and HIPAA for health data) impose their own timelines. If an incident touching regulated data is misclassified as low severity, the organization can blow a statutory deadline and incur fines on top of the breach itself.
CISM expects the security manager to ensure classification criteria explicitly flag potentially reportable incidents to legal early.
Severity Can and Should Change
Classification is not a one-time stamp. As investigation reveals true scope, severity should be re-evaluated , upward when exfiltration or regulated data exposure is confirmed, sometimes downward when an alert proves limited. The IRP should permit and document re-classification, and metrics should record the final, validated severity so management trending stays accurate. Consistent categorization likewise lets the organization see, over time, whether phishing, misconfiguration, or insider activity is the dominant incident driver, pointing investment where it reduces the most risk.