Attacks/Breaches

11/7/2017
10:30 AM
Joshua Bevitz
Joshua Bevitz
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
0%
100%

4 Proactive Steps to Avoid Being the Next Data Breach Victim

Despite highly publicized data breaches, most companies are not taking the necessary actions to prevent them.

Over the last few years, companies around the world have experienced cyberattacks in which personally identifiable information (PII) of consumers was stolen. Even though the Yahoo data breach took place in 2013, it was only recently reported that 3 billion accounts were affected, which is more than three times as many accounts as initially reported.

This year, Equifax experienced a significant breach as well. What isn't well known is that the breach could have been avoided by a patch in the software program Apache Struts, which is used by consumers to dispute information in Equifax's credit reports. Even before the breach, the US Department of Homeland Security advised Equifax that a patch was recommended. Unfortunately for more than 140 million consumers, the patch was never implemented and their PII was stolen, which included names, addresses, birth dates, Social Security numbers, and driver's license numbers.

The Equifax data breach exposed the fact that, despite highly publicized data breaches, most companies still are not taking the necessary actions to prevent them. Most companies are not adequately protected against data breaches or prepared to respond to a breach and mitigate the adverse effects, including the purchase of applicable insurance. Here is what you need to do. 

Step 1. Adequately protect databases containing PII. Equifax made a series of mistakes that businesses should avoid. For example, it had large unsecured databases containing PII, and those databases were not segmented to reduce the size of potential breaches. In addition, the databases were not subject to rigorous access controls. Given the widespread coverage of data breaches, there is no excuse for failing to take simple steps that can significantly increase the security of the PII in your computer systems and reduce the chance of a data breach or the scope of one should it happen.  

Step 2. Put policies in place to reduce risk. Although Equifax was in the business of selling consumer data, its data retention policies were weak or nonexistent. In addition, while the company instructed the responsible personnel to install the Apache Struts patch, it appears that it had no management policy that would have exposed the failure to install the patch. Moreover, it does not appear that the scans that were conducted were tailored to look for the vulnerability that was supposed to be addressed by the patch. It is also unclear whether the monitoring was continuous. Establishing policies and protocol to ensure routine updates, patches, and testing are easy. They are some of the most effective measures a company can take to prevent data breaches.

Step 3. Quickly take action to protect consumers and shareholders. Equifax's CEO waited over a month to advise the board of directors. Although there are valid reasons to delay revealing a data breach, some shareholders will argue that this delay was a breach of fiduciary duty. Equifax waited even longer to advise the public, resulting in consumers losing valuable time in which they could have protected themselves. All of those mistakes not only resulted in the massive data breach but also damaged the reputation of the company, creating the potential liability for Equifax's officers and likely further damaging consumers.

After a data breach occurs, companies should notify their attorneys, law enforcement, and their insurance company. The Department of Homeland Security also recommends reporting the data breach to www.us-cert.gov. In California, companies should also comply with the notification requirements in Civil Code section 1798.82. Even if there is no state or federal rule mandating notification, companies should still notify who was affected so that they can mitigate potential harm (and liability to themselves). Finally, companies should assess and preserve the evidence of the breach and the damage.

Step 4. Buy insurance to cover data breaches. Most courts have held that standard commercial general liability policies provide insurance coverage only for losses to tangible property, and that the loss of electronic data isn't covered. To make sure that you are protected, purchase insurance policies that cover data breach losses and resulting damage to companies, such as business interruption. If there is insurance coverage for the loss, companies should document the time spent to deal with the breach as well as the costs to do so.

Unfortunately, cyberattacks involving data breaches are likely to become more frequent and more damaging when they take place. However, if you protect your databases, put policies in place to reduce risk, quickly take action to protect consumers and shareholders, and buy insurance to cover data breaches, you can try to avoid being next, and mitigate a breach if one occurs.

Related Content:

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry's most knowledgeable IT security experts. Check out the INsecurity agenda here.

 

A partner in Newmeyer & Dillion's Walnut Creek office, Joshua Bevitz has experience practicing in a wide range of legal specialties, including cybersecurity, civil litigation, real estate litigation, construction litigation, insurance litigation, professional liability ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Well, at least it isn't Mobby Dick!
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-9923
PUBLISHED: 2019-03-22
pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.
CVE-2019-9924
PUBLISHED: 2019-03-22
rbash in Bash before 4.4-beta2 did not prevent the shell user from modifying BASH_CMDS, thus allowing the user to execute any command with the permissions of the shell.
CVE-2019-9925
PUBLISHED: 2019-03-22
S-CMS PHP v1.0 has XSS in 4.edu.php via the S_id parameter.
CVE-2019-9927
PUBLISHED: 2019-03-22
Caret before 2019-02-22 allows Remote Code Execution.
CVE-2019-9936
PUBLISHED: 2019-03-22
In SQLite 3.27.2, running fts5 prefix queries inside a transaction could trigger a heap-based buffer over-read in fts5HashEntrySort in sqlite3.c, which may lead to an information leak. This is related to ext/fts5/fts5_hash.c.