Operations

10/9/2014
12:35 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
100%
0%

MBIA Breach Highlights Need For Tightened Security Ops

Configuration change management and better monitoring could have prevented search engine indexing of sensitive financial information.

A newly disclosed breach at the largest bond insurer in the US has highlighted the consequences of operational laxity within the enterprise. The insurer, MBIA Inc., publicly exposed sensitive financial information through a web application that allowed back-end data to be indexed by search engines, along with administrative credentials that would allow an attacker access to any other database information not already easily accessible by search. Unlike many of today's high-profile breaches, this data exposure wasn't caused through active attacks like phishing or brute forcing of passwords.

"This breach occurred through lack of awareness," says Richard Westmoreland, lead security analyst for SilverSky. "A simple mistake can create a large exposure that goes unnoticed for a long period of time."

Discovered by independent researcher Brian Seely and disclosed by Brian Krebs of KrebsOnSecurity, the data exposure was caused by a misconfigured Oracle Reports server. According to security pundits, it serves as a black eye for MBIA, which put bank account numbers, routing numbers and other sensitive customer data at risk of being used for fraud and also as a reminder to other organization why security operations checks and balances are necessary.

According to Andrew Jaquith, CTO and senior vice president of cloud strategy for SilverSky, if the story holds true then the CIO or CISO at MBI probably deserves to be fired.

"This was not a security breach. This was gross negligence, " Jaquith says.

While MBIA's incident was particularly egregious, Seely discovered that it wasn't alone.

"Recently, while researching the scope of a vulnerability, we found that numerous companies and organizations had misconfigured their Oracle reporting services," he wrote.

Configuration management stands as one of the SANS Critical 10 controls. As SANS evangelizes, solid processes that establish standardized configurations, take advantage of configuration management tools, institute file integrity checking and automatically monitor for insecure configurations can go a long way toward hardening systems.

"Even if a strong initial configuration is developed and installed, it must be continually managed to avoid security 'decay' as software is updated or patched, new security vulnerabilities are reported, and configurations are 'tweaked' to allow the installation of new software or support new operational requirements," SANS explains. "If not, attackers will find opportunities to exploit both network-accessible services and client software."

In the case of Oracle Reports, organizations are encouraged to follow Oracle best-practices for enabling security on Reports servers and defining security policies on these machines.

At the same time, organizations shouldn't depend on configuration management practices for peace of mind. Too often these practices can break down.

"We have seen numerous cases like this -- to varying degrees of severity. The issue is that somewhere down the line a database server is poorly configured, or a web application is written with slight flaws in the business logic," says Amy Blackshaw, manager for RSA Fraud and Risk Intelligence. "If we only rely on having 100 percent correct configuration and business logic, we will continue to see this type of 'attack' occur."

Both Blackshaw and Westmoreland agree that monitoring and analysis of logs could have also gone a long way toward reducing the risk posed by such a breach. As Westmoreland explains, the goal would be to limit the length of time such exposures exist, thereby reducing their risk. In the case of MBIA, the fact that much of the information found by search engines was already indexed indicates that the data was sitting out open on the web for a long time.

"With appropriate logging enabled and daily log review, the window of compromise could have been shortened. With file integrity checking and 24/7 real-time monitoring, the misconfiguration may had been identified before any data had been crawled and indexed," Westmoreland says, "Mistakes do happen -- and just as with exploitation, it is not a matter of if or when -- it is happening now, so how fast can you catch it?"

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Ulf Mattsson
50%
50%
Ulf Mattsson,
User Rank: Moderator
10/10/2014 | 1:02:00 PM
Different ways to attack our systems across the entire data flow
I agree that "This breach occurred through lack of awareness" and I think that the general shortage of security skills is a growing concern.

I agree that "A simple mistake can create a large exposure that goes unnoticed for a long period of time" and unfortunately less than 14% of breaches are detected by internal security tools according to the annual international breach investigations report by Verizon. Current reactive security approaches can't tell you what normal looks like in your own systems.

I'm also concerned that this incident "exposed sensitive financial information ... that allowed back-end data to be indexed" and I think that recent data breaches are illustrating that there are so many different ways to attack our systems across the entire data flow. So I think that we urgently should lock down our sensitive data with modern data security technologies. 

I think it is time to secure the sensitive data in the entire data flow with modern approaches. Recent studies reported that modern data tokenization can cut security incidents by 50 %.

Ulf Mattsson, CTO Protegrity
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
New Mirai Version Targets Business IoT Devices
Dark Reading Staff 3/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Reading Schneier's Friday Squid Blog again?
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-6149
PUBLISHED: 2019-03-18
An unquoted search path vulnerability was identified in Lenovo Dynamic Power Reduction Utility prior to version 2.2.2.0 that could allow a malicious user with local access to execute code with administrative privileges.
CVE-2018-15509
PUBLISHED: 2019-03-18
Five9 Agent Desktop Plus 10.0.70 has Incorrect Access Control (issue 2 of 2).
CVE-2018-20806
PUBLISHED: 2019-03-17
Phamm (aka PHP LDAP Virtual Hosting Manager) 0.6.8 allows XSS via the login page (the /public/main.php action parameter).
CVE-2019-5616
PUBLISHED: 2019-03-15
CircuitWerkes Sicon-8, a hardware device used for managing electrical devices, ships with a web-based front-end controller and implements an authentication mechanism in JavaScript that is run in the context of a user's web browser.
CVE-2018-17882
PUBLISHED: 2019-03-15
An Integer overflow vulnerability exists in the batchTransfer function of a smart contract implementation for CryptoBotsBattle (CBTB), an Ethereum token. This vulnerability could be used by an attacker to create an arbitrary amount of tokens for any user.