Don’t Just Make an Incident Response Plan
One of the first things Borkar asks organizations is whether they have their IR plan printed out. Just asking that question makes people realize they should probably go back and take another look at their plan, she said.
There are two broad areas for organizations to focus on when it comes to reinforcing incident response:
Roles and Responsibilities
IT teams and other stakeholders need to understand what they’re going to do in various incident scenarios. Team members should know their roles, and they should know who to call in the event of an incident.
Practice
Rehearsing the plan is also key, Borkar emphasized. “Irrespective of how much they practice, the incident is never perfect or exactly what they practiced, but then you’re only worried about the 20% to 30% that deviates from your plan,” she said.
When this is all in place, recovery may take days. Without it, recovery can take months. “That’s months of business continuity issues, months of the company not innovating,” Borkar said.
WATCH NOW: Build your cyber resilience playbook.
Despite this, statistics paint a picture of organizations’ preparedness that shocked Thursday’s panelists. “There was a recent customer survey, and a jarring statistic came out of that: 26% of organizations have an incident response plan and have rehearsed it,” Rapp shared. “Not rehearsing it is like having a gym membership and never going to the gym.”
Giving the All Clear After a Cyber Incident
A common mistake that companies make when responding to a threat is assuming they’re safe once they have stopped the incident that’s underway.
“It’s very important to assume, once you’re in the heat of battle and trying to mitigate it, that the threat actor might have left some persistence mechanism behind,” Simeon said. “Don’t assume that, just because you’ve locked a couple of accounts or mitigated the accounts they got into initially, it means you’ve completely kicked them out of the environment entirely.” He explained that threat intelligence teams get to see the bigger picture and can warn organizations about techniques they’ve seen threat actors use in the past.
“How do you know the threat actor is gone? Just assume they’re there,” Borkar said.
IT teams should approach every incident like they’re playing the long game, presenters said. This is where working with experts can prove especially valuable. “Our approach to containment and recovery is all around business continuity,” Rapp said. “We’re able to keep the business online while then trying to evict the threat actor.”
The Cyberthreat Landscape Today
While attackers may be lingering on the tail end of an attack, dwell time, conversely, is getting shorter. Dwell time is the amount of time between a cybercriminal accessing your network and doing the encryption for the ransom, when they’re in your network making choices and looking around, said DeGrippo.