News

9/11/2017
12:30 PM
Jai Vijayan
Jai Vijayan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

7 Takeaways From The Equifax Data Breach

The exposure of PII belonging to 143 million US consumers raises questions about the continued use of SSNs as identifiers, breach liability and app sec spending.
Previous
1 of 8
Next

(Image Source: Ivelin Radkov via Shutterstock)

(Image Source: Ivelin Radkov via Shutterstock)

Credit bureau Equifax's disclosure last week that unknown intruders had broken into its systems and accessed sensitive data on 143 million US residents has evoked a mixture of resignation, concern, and outrage.

The resignation stemmed from the fact that the breach is identical to countless ones before it. Once again a security hole in a Web application gave intruders a way to break into a major company's systems and siphon out a massive amount of data over more than two months without apparently triggering any alarms. The pattern has become so familiar in recent years that there really are no new lessons to be learned from these breaches anymore, at least from a security preparedness standpoint.

The sheer scope of the Equifax compromise has caused a lot of concern. The breach could well be the largest ever involving the exposure of Social Security Numbers, driver's license numbers, and other personally identifiable information. Victims could be at risk of identity theft and impersonation fraud for the conceivable future.

What has caused the outrage is Equifax's apparent security lapses in allowing a breach of this magnitude to happen. Many feel that Equifax, as a company handling vital PII belonging to a very large swath of the American population should have been especially careful about protecting the data. Instead, it appears to have allowed the breach to happen because of its failure to address an Apache Struts vulnerability that it should have known about and addressed.

A lot has been made about the growing sophistication of threat actors and the arsenal of increasingly deadly cyber tools at their command. The depressing reality, however, is that the bad guys rarely need to deploy anything more than rudimentary tools and techniques. As SentinelOne's chief of security strategy Jeremiah Grossman points out, many breaches can be prevented. "If we review the history of breaches, very few, if any, were the result of an exploit or attack technique that couldn't be seen coming," he says. "With respect to the vulnerabilities exploited, we know everything about them—how to prevent them, detect them and fix them." But people in the best position to make an impact are not incentivized to do so.

Here in no particular order are seven takeaways from the Equifax breach:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
9/20/2017 | 1:11:19 PM
New Discoveries
Perhaps I am a broken record, but I am amazed at the NEW IT SECURITY PROTOCOL discoveries that are made after every epic event - Delta, Merck, Equifax.  Such concepts are stunning - wow, like nobody thought of education for your user base (email basics) ----- power backup batteries in the bottom of a 42U server rack and a generator farm outside if needed ..... having on and offsite backups that are tested ---  patching applications and patching operating systems.  And always the management view that IT is just JUST an expense line item, so fire all the techs who know something and farm it all out to outsourcing firms that ONLY care about THEIR INVOICING.  Incredible how we shoot ourselves in the feet every single time. 
lunny
50%
50%
lunny,
User Rank: Strategist
9/20/2017 | 11:55:04 AM
Simplify the Mess
The app vulnerability was just the ingress point.  There are many open windows and unlocked doors that allowed the intruders to move about laterally and vertically throughout the environment.  We'll know more details eventually, as the litigation is sure to push much of the story into the public record.  The intruders got in, hid, obtained privileged credentials, and subsequently enjoyed free reign.  It wasn't hard.

We've got to stop treating servers like pets.  They are cattle.  They should all be standardized and we should build them all at the touch of a button from a single image that is fully patched.  You should be able to do this at any time and in just a few minutes.  It's called orchestration.  We're using orchestration to push out new code, but we are too timid to use it to bake security into the mix.  Despite all of the virtualization and cloud implementatinos, we're still patching servers as if they were all special and physical.  This is insane!  This is why companies cannot realistically patch all of their servers.  They are afraid it will be hard, complex, and things will break.  They're right.  Because every systems administrator, application owner, IT executive, business executive thinks their systems are special.  Well-designed network segmentation and a strong privileged access management regime is critical.

Equifax was simply whistling past the graveyard.  What will be written on their tombstone now?
mrgorle@yahoo.com
50%
50%
[email protected],
User Rank: Apprentice
9/13/2017 | 9:34:21 AM
Excellent and well written article
Excellent Article Jay.  content and quality of the material is worth spending time eventhough 8 times clicking the clicking the arrow....
WSJ Report: Facebook Breach the Work of Spammers, Not Nation-State Actors
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/19/2018
Good Times in Security Come When You Least Expect Them
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  10/23/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.