In a previous article we wrote about the activities and information required to create an effective incident response plan. In this article we will talk about the phases of an incident response plan in order to create a well-structured program.
As a review, the incident response plan should define the goals, the various individuals involved, the roles and responsibilities, the communications methods, and the escalation processes throughout the phases of the plan.
As we mentioned in the previous article, an incident can be anything from a breach to a systems failure, but our focus for this blog will be cyber incidents. To that end, we will first define the types of cyber incidents that an organization can experience before we discuss the phases of an incident response plan.
Types of Cyber Incidents
- Exploitation – this type of incident takes advantage of unpatched hardware and software or vulnerabilities in systems to take control of the IT environment.
- Ransomware – most of us have heard of ransomware attacks. This type of attack uses malware that locks systems and files until a ransom is paid. However, paying the ransom does not guarantee that the data will be unlocked and accessible.
- Data Theft – this type of incident involves cybercriminals stealing information that is stored on an organization’s systems. The cybercriminals usually gain access to the systems and the information within them through stolen user credentials. Often, the cybercriminals quietly watch the traffic on the systems for periods of time to identify the most valuable information that they can steal to inflict the most damage.
Phases of an Incident Response Plan
- Outline the goals of the incident response strategy including the policies and procedures. The improvement of the organization’s security, visibility of an incident and the recovery from an incident need to be clearly defined.
- Implement a reliable backup plan to help restore your data.
- Have a comprehensive strategy for patching and updating your hardware, operating systems, and applications.
- Test the plan to ensure it meets expectations and make improvements based on the results as required.
- Monitor networks, systems, and devices for potential threats.
- Document events and potential incidents.
- Analyze the occurrences to determine whether the incident response plan needs to be activated.
- Understand intrusions to contain and apply the appropriate measures for effective mitigation. This may involve isolating systems or suspending access to systems and other measures.
- Eliminate the intrusion by restoring from reliable backups.
- Ensure devices and systems are clean by running anti-malware and antivirus software
- Preserve evidence and documentation to assist with the analysis of the incident.
- Identify the root cause and determine what can be improved to avoid the incident in the future.
- Evaluate the incident response procedures and processes to highlight what went well and what needs to be improved.
- Document the lessons learned and what needs to be adjusted for future incidents.
- Meticulously document the steps that were taken to uncover and resolve the incident that can be reused to resolve future incidents quickly and effectively.
One last piece of advice that we can offer when it comes to an incident response plan is having a printed copy on hand. When an incident occurs and the systems are unavailable, having an electronic copy will not be very helpful if the team cannot access it.
These topics are an overview of the phases of an incident response plan. In creating your plan an organization needs to determine which of the areas where they will require external expertise. It may be none, all, or some of the areas. However, in our experience, getting assistance from experts, whether legal, insurance, communications, incident response specialists or IT service providers is useful as you create your incident response plan.
Call MicroAge today to see how we can help you.