You have an incident response plan, right? But how do you know it’s effective? Is there anything you’re overlooking? What will happen at your organization in the event of a data breach or security incident? While many organizations have a plan in place, far fewer test it and are confident in it if the need to execute should arise.
March 2018 research from the Ponemon Institute found that 77 percent of respondents said their organization does not have a formal cybersecurity incident response plan. Almost half of the respondents said their organization’s plan is either informal and ad hoc — or nonexistent.
“They’re not prepared,” said Sean Mason, director of threat management and incident response at Cisco Security Advisory Services. “It should be the starting block.”
Get Started on Incident Response Improvements
Many security analysts and consultant agree: It’s time to get serious about incident response. With data breaches and other cyberattacks increasing annually, organizations should be well-prepared and secure. To ensure your plan is effective, it should include the following four elements.
1. It’s Tested Consistently
While many organizations claim to have an incident response plan, few actually put them to the test. This is mistake number one, because unless it’s been tested, you really have no idea if it is effective.
“The best organizations that I see who are prepared are ones that are doing that proactive work,” said Mason. “They’re doing tabletop exercises — they’re doing red team versus blue team.”
Much like exercise, routinely testing an incident response plan gives an organization the practice it needs to identify weak spots and make improvements. “Go through and simulate incidents, committing it to muscle memory as it’s tested on a routine basis,” said Mason.
2. It’s Detailed but Flexible
An incident response plan should include detail but also be flexible so it can be applied to different kinds of attacks and incidents.
“A good incident response plan gives you enough lateral movement for a wide range of incidents,” said Steve Armstrong, a SANS Institute instructor and 20-year veteran of security and incident response. “I’ve articulated incident response plans in spreadsheets, and they have a table for each type of incident.”
Flexibility and variety in an IT plan also ensures it can be updated regularly — so it can evolve as cyberattacks change over time.
3. It’s Clear About Communication
Clear communication plans are also essential for incident response. Armstrong said many incident response plans are informal and don’t have a solid understanding of how the network comes into play in incident response communication.
“Plans need to make clear how post-incident communication will be secure,” Armstrong said. “It needs to be not on network, particularly if it has been compromised.”
4. It’s Inclusive When It Comes to Stakeholders
A concise list of stakeholders and how each should be involved in incident response is also crucial. “An organization should understand its environment and what it’s trying to protect, and who is on its team,” Armstrong said. “Who is up-front striking goals and who is the safety net in back?”
“If it’s an incident with multiple machines, you should have already gone through and thought about security, networking, business and finance,” said Mason. “And who are your external partners that are going to help in a time of crisis? It is easy to think through and say, ‘We got this.’ But then think, ‘If I have 10,000 machines impacted by ransomware, who is going to do all that work?'”
An incident response plan should also include the intention to get your legal department involved as early on in the process as possible. “You should have involved legal right out of the gate,” said Mason. Your legal department can often advise if it’s necessary to involve law enforcement or other external partners.
Incident response remains a significant challenge for most organizations globally and is hindering cyber resilience. Consider these four recommendations to improve your plan.