Attacks/Breaches

10/4/2017
05:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Yahoo, Equifax Serve as Cautionary Tales in Discerning Data Breach Scope

Both companies this week revealed that their previously disclosed breaches impacted a lot more people than previously thought.

Yahoo and Equifax's separate disclosures this week that previously reported data breaches at their organizations were even bigger than first thought illuminated the massive challenge enterprises face in gauging the true scope of malicious intrusions these days.

Yahoo's parent company Verizon on Tuesday said an August 2013 breach that Yahoo disclosed in Dec. 2016 impacted a mind-boggling three billion email accounts rather than the one billion figure originally reported. 

Following Verizon's acquisition of Yahoo and during the integration of the two companies, Yahoo obtained new information showing that every single one of its user accounts in August 2013 was compromised, Verizon subsidiary Oath said in a statement. The investigation showed that the data that was stolen did not include, however, clear text passwords, payment card data, or bank account information, the company said.

In a similar update the day before, Equifax said that the actual number of people impacted by the breach it disclosed on Sept. 7 was 145.5 million, or 2.5 million more than the number it had first reported. The company said a forensic analysis conducted by cybersecurity firm Mandiant unearthed the additional victims. The investigation showed that no databases outside the US were impacted, Equifax said, while also revising downward the number of Canadian victims impacted from 100,000 to 8,000.

Nathan Wenzler, chief security strategist at security consulting firm AsTech, says multiple factors can make it hard for organizations to get a true handle on the scope of intrusions such as the ones at Yahoo and Equifax. "Most of it centers on the lack of sound asset management and inventory processes," he says.

Many organizations don't actually know what they have to begin with, and therefore struggle to figure out what was breached when an incident occurs. "And, to be fair, a lot of hackers don't make it easy to figure out either," Wenzler says. "Systems can be compromised quietly, with no trace of anything serious being done, which can make it difficult for a researcher to know for certain that a system was compromised."

Companies with a less than perfect understanding of their assets are likely to keep discovering more datasets that have been compromised than they originally assumed when investigating a breach incident, he says.

CEO in the Hotseat

Equifax's update this week added to broad concerns over its response to the breach overall, including its 45-day delay in breach notification and its inavertently pointing those wanting to sign up for free credit monitoring to a phishing website.

Former Equifax CEO Richard Smith, who retired from the company after the breach, this week acknowledged mistakes with the rollout of the signup website and call centers. In many cases, such issues added to the frustration of American consumers, he said in prepared testimony for a US House Committee on Energy and Commerce subcommittee, which held a hearing on the breach this week.

The testimony delved into some details of the incident. Smith noted that when Equifax's security organization first heard from US-CERT about an Apache Struts vulnerability that needed to be patched, the information was promptly relayed to all applicable personnel. However, the vulnerability remained unpatched and was not caught in subsequent scans, giving the intruders a way into Equifax's network.

In some cases, organizations that suffer large, sophisticated breaches will never know the full scope of its impact, says Michael Sutton, CISO at Zscaler. With Yahoo, there's no information on what new evidence led it to the two billion additional breached accounts one year after the original discovery. That the initial investigation failed to catch such a huge number of compromised accounts is significant, he says.

"While it’s possible that new evidence, such as logs were uncovered that hadn’t previously been reviewed, more likely a new connection was made," he says. "Breach investigations are all about connecting the dots — identifying an entry point and figuring out where the attacker went from there," he says. "Without transparency from Yahoo, we can only speculate as to what new dots were connected."

Generally, determining the full scope of an incident can be hard when multiple entry points are involved and when multiple devices or accounts are compromised, Sutton notes.

Investigators had a hard time figuring out what was stolen from Equifax because the records were stored in various data tables across multiple systems, according to the CEO's testimony. So tracing the records back to specific individuals, given the massive scope of the compromise, was very time consuming and difficult, he said.

The telltale signs of such attacks can be scattered and hard to find even if they exist. "Following the trail of breadcrumbs to trace the attacker's path requires that the bread crumbs exist in the first place," Sutton says. "It’s possible that logs have blind spots or have been overwritten, especially when a breach investigation takes places months or years after the incident."

Backup logs are one place where a breached entity might discover more records than were originally presumed compromised in an incident, says Alex Held, chief research officer at SecurityScorecard.

Attackers can put in a lot of effort to erase evidence of unauthorized access following a successful attack. Log removal is often the final step in this effort because it can blur the true scope of the incident and make attribution difficult. In such situations, a backup logs that may not have been available during the initial investigation can shed fresh light on the true scope of the incident, he says.

Related Content:

 

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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
gif-washco
50%
50%
gif-washco,
User Rank: Apprentice
10/5/2017 | 2:22:06 PM
Failure of Leadership
On both Yahoo and Equifax megabreaches, the failure of leadership is the key to a long stream of events leading to the revelation. And yet both CEOs (Marissa Mayer and Richard Smith respectively) got their golden parachutes and basically got paid for leadership negligence. Blaming other people in the company for the breach, even with an apology, makes their statements insincere. Very disappointing since these leaders should instead be role models of postivie leaderships and own up to their failures.

 
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
Don't Roll the Dice When Prioritizing Vulnerability Fixes
Ericka Chickowski, Contributing Writer, Dark Reading,  5/15/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11321
PUBLISHED: 2018-05-22
An issue was discovered in com_fields in Joomla! Core before 3.8.8. Inadequate filtering allows users authorised to create custom fields to manipulate the filtering options and inject an unvalidated option.
CVE-2018-11322
PUBLISHED: 2018-05-22
An issue was discovered in Joomla! Core before 3.8.8. Depending on the server configuration, PHAR files might be handled as executable PHP scripts by the webserver.
CVE-2018-11323
PUBLISHED: 2018-05-22
An issue was discovered in Joomla! Core before 3.8.8. Inadequate checks allowed users to modify the access levels of user groups with higher permissions.
CVE-2018-11324
PUBLISHED: 2018-05-22
An issue was discovered in Joomla! Core before 3.8.8. A long running background process, such as remote checks for core or extension updates, could create a race condition where a session that was expected to be destroyed would be recreated.
CVE-2018-11325
PUBLISHED: 2018-05-22
An issue was discovered in Joomla! Core before 3.8.8. The web install application would autofill password fields after either a form validation error or navigating to a previous install step, and display the plaintext password for the administrator account at the confirmation screen.