How to Customize the Incident Management Policy
Last updated: May 13, 2025
Our team provides two default incident management policies that you can customize to match your organization's needs:
Incident Management Procedure (general incidents)
Security Incident Management Policy (security-specific incidents)
Merging or Maintaining Separate Policies
You can choose to either maintain these as separate policies or merge them into a single comprehensive incident management policy, depending on your organization's needs. Having a single policy may be preferable if your security and general incident handling procedures are similar.
Customizable Elements
The following elements can be customized in the policy templates:
Severity Categories - Modify the incident severity definitions to align with your internal classification system
Escalation Procedures - Update the escalation paths and internal reporting structures
Response Team Roles - Adjust role assignments and responsibilities (e.g., assigning final breach determinations to CTO vs CEO)
Incident Report Templates - Replace the provided templates with your own internal documentation formats
Response Meeting Agenda - Modify the suggested meeting structure while maintaining key elements like:
Initial investigation and troubleshooting
Documenting Indicators of Compromise (IOCs)
Action planning and mitigation steps
Root Cause Analysis (RCA)
Best Practices
While customizing your incident management policy:
Maintain a clear process flow from incident detection through resolution
Ensure alignment with any existing ITSM or ITIL frameworks your organization uses
Keep documentation of IOCs and investigation findings throughout the incident lifecycle
Include problem management follow-up to track implementation of long-term solutions