The news is crowded with reports from noteworthy companies of cyber-attacks. Last year was the year of the data breach and this year is the year of ransomware. Companies large and small, even those with large security budgets and mature security practices, still proved vulnerable to attack. Every company will suffer a security incident someday, but not all companies are prepared for it, and preparation will determine what impact a security incident will have on your company.
Will your company weather the attack and come out stronger for it or will you lose customers, brand image, or your company?
“We’re not in Kansas anymore”
This is where your incident response plan comes in. The incident response plan outlines the activities that will take place in an incident. Decisions made before an incident are far superior to those made in the heat of the moment when the stress is on. Plans can be thought through and properly vetted, and this leads to more robust decision-making, more effective incident response, less company and customer loss due to the incident, and less stress overall.
“Houston, we have a problem”
The first step in an incident response plan is to define the team of individuals who will conduct and coordinate the incident response. This is more than just a group of technical wizards or high-level executives. It also includes PR, legal, security, and third parties.
“To the Batcave”
Once the team is assembled, the next step is to create an incident response plan. This is not a step that is given to one or two team members. Rather, those involved on the team should also be involved in the incident response planning effort.
Scenarios or table top exercises can be used to develop plans for specific incidents or to enhance existing plans. Scenarios such as malware infection, ransomware infection, a lost or stolen device, Distributed Denial of Service (DDoS) attacks, cyber breaches, and social engineering should be specifically addressed in meetings where each team member walks through the actions they would take in that incident. A facilitator guides the discussion and aids in making sure critical steps are not skipped. The output from scenario planning is a detailed step by step process for handling specific incidents.
“Who’s on First?”
It is not enough to know what to do. You also have to know who is going to do it. Many plans have failed because no one knew who was supposed to carry out the expertly-written instructions. Each task in the incident response plan should have a designated person or role assigned to it. Role-specific tasks provide accountability and ensure that there will be someone to conduct those activities during an incident. None of the tasks identified in the procedures should be overlooked. It is important to also assign alternates in case the primary person is unavailable when the actual incident occurs. Once the incident procedures have been properly vetted and approved and the roles outlined, response activities should be practiced regularly so that the incident response team is familiar with their responsibilities.
There is a lot more information available on incident response, but an effective incident response plan requires the right team, well-thought-out instructions, and tasks that are clearly assigned to individuals. Plans lacking these elements will not provide your company, customers, and employees with the guidance they need when an incident occurs, and it will happen. Be prepared.
This post is sponsored by AT&T Security.