What’s in an Incident Response Plan?
While many districts proactively deploy cybersecurity measures and technology to detect threats and prevent breaches, no IT infrastructure is completely impenetrable. Schools must plan for the inevitable and develop incident response plans to execute when successful cyberattacks take place, district IT leaders say.
A plan includes having an incident command structure: identifying who leads the response, who handles communications, who has authority to turn off IT systems and establishing the criteria for when to escalate issues to district leadership, says Amy McLaughlin, project director for CoSN’s cybersecurity and network and systems design initiatives.
McLaughlin recommends that districts develop high-level plans. “You don’t know what the incidents are going to be. Sometimes, people try to plan for every possible scenario, and then it becomes overwhelming,” she says.
Other important elements include updated contact information, including after-hours emergency numbers, for IT staff, key district leaders, vendors and ISPs, she says. Districts should also maintain readily accessible technical documentation, such as network architecture maps and a detailed inventory of servers and applications.
“You want to have it all in one place, so it’s at your fingertips,” McLaughlin says.
After recovering from an incident, districts should also perform after-action reports to identify lessons learned and make improvements, she says.
READ MORE: Inventory is a key element of incident response planning.
Arizona School District Activates Response Plan After Attack
When Gabel was promoted to network operations manager, the Agua Fria lacked an incident response plan, so he drew one up: a one-page flowchart that outlines staff roles and responsibilities and the process for identifying, containing and eradicating threats to restore operations.
In September 2023, he presented the strategy to the superintendent and the executive cabinet, got their buy-in and then explained the plan to his IT staff.
“It’s imperative that you have a blueprint for what’s going to happen, if not for yourself, then for your team and stakeholders, so that everyone knows what part they will play,” he says.
There is no one-size-fits-all plan. It can be as detailed as a district needs it to be, says Gabel, now IT director. In Agua Fria’s case, Gabel created a simple chart that matched his team’s technical knowledge.
“We are a cohesive team,” he says. “We’ve built trust with each other, where we know our capabilities and we know who’s going to do what, so when an event happens, our team is ready.”
Agua Fria’s plan was put to the test when ransomware infected the district’s virtualized environment. Gabel served as incident commander, managing the process.
At 6 a.m., the IT team didn’t know ransomware was the cause. The server cluster, which runs about 40 virtual machines, was nonresponsive, so the team rebooted it, but it was still not working. Meanwhile, the district’s CrowdStrike security software sent alerts that it repeatedly blocked a service account from accessing other servers over VPN. That’s when the staff and the consulting firm realized the district was hacked.
They immediately shut down the network and VPN and alerted the Department of Homeland Security, the FBI and the district’s insurance provider. Then the IT staff and consulting team collaborated on two tasks: investigating how the hackers got in and determining the scope of impact. Meanwhile, a recovery team sanitized affected servers, verified the integrity of data backups and restored services.