SEC10-02 Developing an Incident Response Plan
The Incident Response Plan (IRP) is an important part of an organization's security policy. It aims to ensure that actions can be taken quickly and orderly when a security incident occurs, minimize losses, and restore normal operations as soon as possible.
- Risk level
High
- Key strategies
- Establish an incident response plan, including defining incident levels, response processes, and recovery strategies. Security incidents that affect service availability or can be perceived by tenants are classified into five levels: S1, S2, S3, S4, and S5.
- Implement continuous monitoring, including logs, network traffic, and abnormal behavior of the cloud environment. A preliminary analysis is performed when a potential incident is detected to determine the severity.
- Implement rapid security response actions to isolate affected systems or accounts, disconnect network connections, stop services, remove malicious files, fix vulnerabilities, replace abnormal systems, and harden systems. Ensure that all threats have been eliminated to avoid recurrence.
- Formulate recovery policies to gradually recover affected services, ensure data and system consistency, and perform tests to ensure that all systems are running properly.
- Conduct post-incident analysis to summarize the cause, response process, and lessons of the incident. Update the incident response plan and make improvements.
- Incident response plans are regularly reviewed and updated to accommodate new threats and business needs.
Event Severity
Incident Response Time
Average Risk Control Time
S1
5 minutes
1 hour
S2
5 minutes
2 hours
S3
5 minutes
4 hours
S4
10 minutes
24 hours
S5
10 minutes
48 hours
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot