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

9/21/2017
04:45 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

SEC Says Intruders May Have Accessed Insider Data for Illegal Trading

2016 breach of the Securities and Exchange Commission's EDGAR database dents its reputation as a federal cybersecurity enforcer.

The Securities and Exchange Commission's (SEC) credibility as an enforcer of cybersecurity requirements took a bit of beating this week after it disclosed a 2016 data breach that might have given intruders access to nonpublic information for illegal trading.

In brief comments buried in the middle of a long public statement on the agency's cybersecurity posture, SEC Chairman Jay Clayton tied the breach to a software vulnerability in the test filing component of the SEC's EDGAR system.

The breach was discovered and addressed at some unspecified time in 2016. But it wasn't until August 2017 that the SEC learned that the incident might have allowed the intruders to profit illegally through trading, Clayton said, without providing any additional details on how that might have happened. The vulnerability provided access to certain nonpublic information in EDGAR and was patched promptly after discovery, he noted.

EDGAR is an automated system for electronically collecting, validating, accepting, and forwarding disclosure documents from public companies that are required by US law to file with the SEC. On average, the EDGAR system receives and processes some 1.7 million electronic filings annually, a lot of which is publicly available data. Some of the typical data in EDGAR includes statements for IPOs and quarterly and annual reports. But some documents that companies might file voluntarily — such as the proposed sale of securities — may remain nonpublic.

"The EDGAR database contains or has the potential to contain the filings companies make that are labeled as private," says Chris Pierson, chief security officer and general counsel at Viewpost.

For instance, companies can make filings for mergers and acquisitions that they might want to keep private for a period of time. "These are the filings that a hacker would want to find and see as it indicates the intentions of a public company and can be translated into monetary reward," Pierson says.

The incident is the second one that the SEC has disclosed this year involving unauthorized access or misuse of its systems. In May, the SEC announced that it had filed fraud charges against a mechanical engineer who managed to make a fake regulatory filing on the agency's systems in an attempt to manipulate the prices of Fitbit's stock.

The almost complete lack of details surrounding the 2016 breach incident has resulted in some speculation over what might have happened and the true extent of the compromise.

The SEC's language surrounding the breach discovery and vulnerabilities sound intentionally vague, says Atiq Raza, CEO of Virsec Systems. "They are implying that as soon as the vulnerability was discovered, they patched it promptly using all due diligence," he says.

"But this begs more questions: discovered by whom and when?" he says. "It may well be that the SEC discovered an unpatched server that was being exploited, for an unknown, probably long period, and only then took steps to apply critical patches."

Ilia Kolochenko, CEO of Web security firm High-Tech Bridge, says the vagueness of the SEC's disclosure is sure to provoke speculation about nation-state involvement or actions by known cybercrime groups.

"In the financial world, even a press release can make you millions if you get it before everybody else does," Kolochenko says. "In the Equifax situation, victims may be attacked to steal a couple of hundreds of dollars on average, while in this breach smart attackers could potentially make huge amounts of money at the expense of unaware honest investors."

Clayton's disclosure pertaining to an incident that happened back in 2016 has also raised some questions about the SEC's own breach notification obligations.

But some executives such as Jeremiah Grossman, head of security strategy at cybersecurity firm SentinelOne, says the apparent lag is not all that surprising.

"There's no legal obligation I'm aware of for the SEC to ever disclose this kind of breach, or to notify the parties whose data was compromised," Grossman notes. "We're talking EDGAR data, not PII. That might be one possible explanation."

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.

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
I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-2079
PUBLISHED: 2019-11-22
A cross-site request forgery (CSRF) vulnerability in the Activity module 6.x-1.x for Drupal.
CVE-2019-11325
PUBLISHED: 2019-11-21
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
CVE-2019-18887
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. The UriSigner was subject to timing attacks. This is related to symfony/http-kernel.
CVE-2019-18888
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. T...
CVE-2019-18889
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. Serializing certain cache adapter interfaces could result in remote code injection. This is related to symfony/cache.