Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

4/16/2020
10:00 AM
Shawn Taylor
Shawn Taylor
Commentary
Connect Directly
LinkedIn
Twitter
RSS
E-Mail vvv
50%
50%

5 Things Ransomware Taught Me About Responding in a Crisis

What happened in Atlanta is worth studying because it was one of the earliest cases of a major city ransomware attacks and because it came out the other side stronger and more resilient.

When I first flew to Atlanta in March 2018, the city was in crisis. It had been hit by a massive ransomware attack, one that took down multiple critical departments and systems and made headlines around the country. 

It's a story that's unfortunately repeated itself around the country since, with ransomware attacks hitting Albany, N.Y.; Baltimore, Md.; Lakeland, Fla., and many more. In total, ransomware hit more than 70 state and local governments in 2019. 

The recovery from this large of an attack isn't easy by any means, but the city rallied behind its new CIO Gary Brantley to make it happen. He was brought in after the city's digital infrastructure had been stabilized and had been charged with ensuring such an event would not happen again. 

I got to see what this process looks like first-hand when I was brought in to help with Atlanta's recovery and subsequent efforts to revitalize the city's security approach. It's a process I've repeated around the country, consulting to state and local agencies around the US, some of which had suffered their own ransomware attacks in the past year. 

Every case is a learning experience, both for the city/county/agency and for the security professionals brought in to help. But Atlanta has proven to be a particularly good case study to follow, not only because it was one of the earlier cases of a major city ransomware attack, but also because it has come out on the other side of the event much stronger and resilient. 

Many of these principles will also apply in the coming months as organizations respond to the latest crisis of the COVID-19 pandemic. While this is a crisis in a different form, many of the same principles of cybersecurity resilience and response still apply.  

Here are some of the takeaways from the city's cybersecurity turnaround:

1. To Pay, or Not to Pay? 
It's become one of the central questions in the midst of a ransomware attack: to pay or not to pay? On one hand, paying the hackers only reinforces their desire to attack future organizations. It's also not guaranteed hackers will follow through with promises to decrypt data after payment, not to mention the fact that there's no guarantee they aren't still in the environment and can execute another attack. But, not paying can also mean a slower and much more costly recovery. 

Atlanta chose to not pay the ransom, which amounted to roughly $50,000 in bitcoin, and recovery efforts ended up costing the city an estimated $7 million and took more than a year to complete. Brantley maintained that not paying is still one of the best decisions the city ever made. Ultimately, the recovery also gave the city an opportunity to establish a robust foundation upon which to rebuild their enterprise and teams to be stronger than ever before. 

2. Incident Response is Key 
It may seem obvious, but having a prepared incident response team in place before an attack occurs is key. Atlanta had a team already in place before the attack that included software and services vendors along with Homeland Security. All of these teams were aligned and working together before, during, and after the attack. This unified response management helped ensure that when the attack occurred, the teams were more quickly able to curb the attack and restore services. Companies, cities, or agencies who don't have this in place should consider implementing a strategy for incident response before it is needed.  

3. Getting Back to Basics 
One of the first things Brantley focused on as CIO was to get back to the basics. "One of the main learnings was to go back to operational basics, do the core things right and consistently," he recently said in a presentation at the RSA Conference in San Francisco. To do that, his team embraced and began to follow the NIST Cybersecurity Framework (CSF). On top of that, because the city had to rebuild many systems from scratch, it was able to replace legacy systems with newer, faster, and more secure technology.

This is especially important for a city like Atlanta, which is a hub for technology innovation. The City of Atlanta hosts one of the world's busiest passenger airports, has a world-renowned public transportation system, and is a leader on smart city initiatives. All of those functions rely on solid infrastructure, which is reinforced by these strong cybersecurity basics that Brantley has been working to put into place. 

4. It's Not Just About Technology
While technology is obviously an important component of ransomware recovery, Brantley focused just as much on his teams, culture and people. "From Day 1, I took a lot of time to understand the organization, to listen, and to learn," he said at RSA. One of his first steps was to ensure the right people were in the right roles, then augment those employees with new hires that brought different skillsets. 

Brantley knew that the execution of the city's technical transformation would only be possible with the right team in place. It's a lesson any business can learn from: The power of teamwork is always one of the strongest pieces of a recovery. 

5. Look Forward, Not Back 
It's tempting following this type of attack to want to limit future innovative technology initiatives. But Atlanta used this event to spur technology innovation across the city, tackling initiatives around facial recognition, drones, and even exploring technologies that can leverage 5G. It is incorporating security with each of these innovations.

"This fight is tough," Brantley added. "We are in a war where we get attacked, but you can't attack back. Make progress. Move forward. The transformation never stops."

Related Content:

Check out this listing of free products and services compiled for Dark Reading by Omdia analysts to help meet the challenges of COVID-19. 

Spanning a 20-year career as an accomplished and well-respected Systems Engineer, Shawn Taylor's strong mix of technical acumen, architectural expertise, and passion for operational efficiencies has established him as a trusted adviser to ForeScout's customers since joining ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
jking@midflorida.com
50%
50%
[email protected],
User Rank: Apprentice
4/17/2020 | 9:58:56 AM
Lakeland, FL
This article mentions Lakeland, FL as having had a newsworthy ransomware attack.  I'm curious if you can share the details on that one?  Thank you.
22334455h
50%
50%
22334455h,
User Rank: Apprentice
4/24/2020 | 11:03:42 PM
Re: Lakeland, FL
yes thats right
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...