About Us | Contact Us
View Cart

When Ransomware Hits, Concerns Go Beyond Payment

By Jolley | Hadaway | Friday, August 26, 2016 - Leave a Comment

Without further investigation, there’s no guarantee that data was merely encrypted…


100920700When ransomware strikes it’s likely many organizations will focus on whether the encryption used can be broken, and whether it makes more sense to simply pay to unlock the affected machines. While concerns about payment are likely the most pressing concern that you will face should the worst happen, there could also be a obligation to notify both federal investigators and customers about the incident and its severity.

If you haven’t thought about it yet, now is the time to add it to your next incident response team meeting agenda: incidents involving ransomware have risen steadily since the late 00’s and are expected to reach record numbers in 2016 according to a report from the Institute for Critical Infrastructure Technology. Once ransomware strikes, you may only have as little as 24 hours to decide on a strategy–during which time your organization may not have a working network–so it is important to think about this issue now.

What should be addressed?  Not just, “are we going to pay a ransom” but also “will we notify our customers.”

Not that you have to make that decision now, but your team should understand the nuances of ramsomware’s impact on the disclosure process.

While every case will be different, generally if non-public customer data was among the assets frozen by the ransomware Federal examiners will need to be notified about the availability issue the incident presented. Because a ransomware event may only be an availability issue, customer notification may not be not required–but this is by no means universally true!  Your incident response team will want to follow the five step process to determine if there is a potential for misuse.

Which is why you need to address this scenario, as a team, now!

There can never be a blanket guarantee about ransomware and data security because the vectors used to install them can often be used to install other malicious software which can transmit data! That means in each case you should perform a full scan of the compromised machines, review the logs from your incident detection/protection systems and also review what non-public information, if any, were on the machines.

If there’s still any doubts about the situation it may be time to call in the data forensics team to be certain, or depending on the severity of the breach, to simply notify the customers that may be impacted. The one thing you can’t do is assume that encryption was the only thing that happened to your data.

Article by Matthew Jolley and Dan Hadaway.


same_strip_012513


 

Posted in Articles, Compliance

Latest News
    The Four Basic Truths of System Security Webinar-Video The last thirty years have seen an evolution of frameworks, laws, and assessment approaches to information security which can intimidate the management team with their complexity. This webinar will discuss the four basic truths of system security regardless of frameworks or approach, and eight control systems to […]
    Community Banking and their layers of security. . . Michael Hartke’s first post as Executive Vice President! Thinking back to my first talk to security professionals in community banking almost 10 years ago, the question continues to this day. First some background… infotex was moderating the Indiana Bankers Association Security Conference when one of the […]
    Reasons why we should be considered! infotex provides a number of services that can be checked out if you click over to offerings.infotex.com! We even made a movie with all the reasons why infotex should be your next MSOC!  
    infotex and GoTo To all infotex managed security service Clients: As recently reported by major news outlets there was a data breach affecting GoTo (formerly LogMeIn) wherein attackers stole encrypted backups containing customer information in November 2022.  Based on the advisory from GoTo the products they offer that are affected include LogMeIn Pro, LogMeIn Central, […]
    An option for increasing security for ALL organizations. . . The threat landscape is evolving daily, and it is becoming increasingly difficult for even large organizations providing cyber defense services to keep up. As Brandao (2021) notes, it is important for organizations to adapt holistic technologies that can correlate all attack events. Therefore, developing XDR […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Check out posters.infotex.com for the whole collection! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape) You are welcome to print out and distribute this around your […]
    A relic of the internet’s less secure past, many small firms struggle to secure their email systems… An article review. With a great deal of cybersecurity related news focused on new threats and similarly new techniques aimed at combating them, it can be easy to forget some of the older threats that have never gone […]
    Seven Trends . . . …that small bank Information Security Officers face in 2023 Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . Welcome to the Magnificent Seven, my annual predictive article about the seven trends in technology that will impact the Information Security Officers of […]
    System Security and Cybersecurity are not the same thing. . . Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . Regarding “information security,” the last thirty years have seen an evolution of frameworks, laws, and assessment approaches which intimidate the management team with their complexity.  […]
    The cryptographic algorithm is vulnerable to attack and is no longer considered secure… An article review. NIST has announced that it plans to retire the SHA-1 cryptographic algorithm by the end of 2030, citing multiple vulnerabilities in the standard, effectively ending its use after nearly 30 years.  Introduced in 1995, SHA-1 used a 160-bit hash […]