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.

Prior to becoming an independent analyst, Paul Shomo was one of the engineering and product leaders behind the forensics software EnCase. In addition to his work in the digital forensics and incident response (DFIR) space, he developed code for OSes that power many of today's ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
CVE-2020-5990
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
CVE-2020-25483
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
CVE-2020-5977
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.