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.

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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/2/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9498
PUBLISHED: 2020-07-02
Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed...
CVE-2020-3282
PUBLISHED: 2020-07-02
A vulnerability in the web-based management interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an unauthenticated, remote attack...
CVE-2020-5909
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, when users run the command displayed in NGINX Controller user interface (UI) to fetch the agent installer, the server TLS certificate is not verified.
CVE-2020-5910
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection would be authorized.
CVE-2020-5911
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.