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.

Operations

3/4/2016
12:30 PM
Paul Shomo
Paul Shomo
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Why Marrying Infosec & Info Governance Boosts Security Capabilities

In today's data centric world, security pros need to know where sensitive data is supposed to be, not just where it actually is now.

Cybersecurity is an industry of espionage, crime markets, and cyber mercenaries reverse engineering the weapons of warring states. Perhaps these stories are so sensational that we’re focusing a too much on the bad guys. That’s a bold assertion in an industry driven by threat intelligence, yet our perimeters have already been invaded, and we’re occupied. Shouldn’t we focus on circling the wagons around our sensitive data?

It used to be that a perimeter breach caused a stir. Today, hacker ownage of endpoints could be another day at the office -- unless our beloved customer data has been accessed. Unfortunately, the Identity Theft Resource Center reports the number breaches stayed the same in 2015, yet hackers have been twice as successful getting to our data. Confidential data only exists on a minority of endpoints, yet cyber criminals are better at getting to these select machines than we are at defending them. We had better prioritize our defense with data-centric thinking, fast.

When I say data-centric security, I’m not really talking about the traditional role of Data Loss Prevention (DLP), which in the past has attempted to block commandeering of sensitive data. History teaches us that the perimeter is no match for today’s cybercriminals. Hackers shouldn’t be holding our crown jewels with only perimeter technologies standing between them and victory. Data-centric security begins far earlier and involves knowing where our sensitive data is supposed to be, versus where it is now.

If we know that only 10 percent of our endpoints hold sensitive data, our vital attack surface is significantly reduced. We certainly wouldn’t surrender the 90 percent, but for this vital network segment we’d have the ability to tighten policies, increase budget, and prioritize response. Our security team’s efficiency would skyrocket by focusing on 1/10th of our attack surface.

Selectively spotting data during transfer is one thing, but digging through all the sensitive data “at rest” is not that easy. Anyone who has keyword searched their hard drive knows how time and I/O intensive it is. Searching every endpoint is one thing, but proprietary document stores, intranets and cloud repositories, are difficult to access. Yet, software exists to do this, and is probably already utilized by your compliance departments for data audits and to respond to court subpoenas in the eDiscovery process.

The second problem is that knowledge of what sensitive data looks like is segregated within companies. Finding customer contact info, credit card, and social security numbers is fairly straightforward. Using jargon to locate health records and financials is a little tougher. But do you think infosec at Coca Cola knows the secret ingredients needed to spot its intellectual property? Hardly! This type of knowledge is siloed in compliance, legal, and other departments accustomed to hierarchies of privilege where certain employees know secret IP keywords, conduct searches, view intimate user data, and provide sterilized reports to the uninitiated. Herein lies the integration point between infosec and compliance: communicating this map of endpoints storing privileged data.

Recently the FCC entered a $25 million settlement with AT&T Services, related to unauthorized disclosure of 280k customer records. The uncertainty over U.S. legal penalties and new EU privacy regulations are driving a new Information Governance (IG) market. These IG folks will soon appear in new positions, such as chief information governance officer (CIGO), or other titles with the acronym IG. Their mission will be tracking, regulating, and enforcing sensitive data policies.

The growth of the IG market is sure to funnel some resources from infosec, but making data-centric security possible is a net gain. The Ponemon Institute counts the average cost of a single stolen customer record at $154, and goes as high as $363 for healthcare organizations. This means theft of only a few thousand records incurs costs in the millions.

As I’ve already mentioned, infosec efficiency could be increased with a map of endpoints housing these confidential records. Today we receive alerts as these records exit our perimeter. Why not receive a “Data Displacement Event” earlier, as data appears where it’s not supposed to be? Detecting data gathered by hackers before exfiltration could save millions.

Infosec should respond to a data displacement event with the same vigor as locating malware. Quick, put the forensic security expertise on answering the priority questions of the day! How did these records get here? Which users or programs accessed them? Have they already been transferred externally?

In the post perimeter world, it’s time for a new way of thinking. If there isn’t a boat or a shoreline nearby, nobody cares if a Tsunami hits the middle of the ocean. Similarly, the location of sensitive data means everything in judging the importance of a security incident or endpoint pwnage. It’s time we allow the people who defend an organization’s private data to benefit from those who can recognize what these records look like, and where they are.

Related Content:


Interop 2016 Las VegasFind out more about security threats at Interop 2016, May 2-6, at the Mandalay Bay Convention Center, Las Vegas. Register today and receive an early bird discount of $200.

Paul Shomo is a senior technical manager for third party technologies at OpenText. A veteran of cybersecurity, Paul Shomo has spent more than 15 years as a software engineer with experience working in security and forensics, networking, and storage. Paul has spent several ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Virginia a Hot Spot For Cybersecurity Jobs
Jai Vijayan, Contributing Writer,  10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-17612
PUBLISHED: 2019-10-15
An issue was discovered in 74CMS v5.2.8. There is a SQL Injection generated by the _list method in the Common/Controller/BackendController.class.php file via the index.php?m=Admin&c=Ad&a=category sort parameter.
CVE-2019-17613
PUBLISHED: 2019-10-15
qibosoft 7 allows remote code execution because do/jf.php makes eval calls. The attacker can use the Point Introduction Management feature to supply PHP code to be evaluated. Alternatively, the attacker can access admin/index.php?lfj=jfadmin&action=addjf via CSRF, as demonstrated by a payload in...
CVE-2019-17395
PUBLISHED: 2019-10-15
In the Rapid Gator application 0.7.1 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.
CVE-2019-17602
PUBLISHED: 2019-10-15
An issue was discovered in Zoho ManageEngine OpManager before 12.4 build 124089. The OPMDeviceDetailsServlet servlet is prone to SQL injection. Depending on the configuration, this vulnerability could be exploited unauthenticated or authenticated.
CVE-2019-17394
PUBLISHED: 2019-10-15
In the Seesaw Parent and Family application 6.2.5 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.