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.

Threat Intelligence

5/17/2017
04:30 PM
David Damato
David Damato
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Why We Need a Data-Driven Cybersecurity Market

NIST should bring together industry to create a standard set of metrics and develop better ways to share information.

Imagine you're the chief information security officer (CISO) of a big bank. You've just implemented a new cybersecurity program and you want to see how your metrics stack up against those of your peers. It should be easy, right? It's not.

Unfortunately, there is no standardized process for measuring and reporting on cybersecurity metrics that all organizations can access. I can give my firsthand experience, or they can hire one of the big consultancies. Even then, the available data sets are too small and in different formats.

The NIST Cybersecurity Famework — put forward by the US Department of Commerce and widely adopted by businesses and government agencies — is the ideal mechanism for setting these standards. That's why I was glad to see the Department's updated draft — which was released earlier this year, and for which comments were due in April — even added a section on metrics and measurement. But the National Institute of Standards and Technology doesn't go far enough. It should use its convening power to bring together stakeholders across industries and develop a set of common metrics, authorize and approve third parties to audit them, and develop ways to share this information.

This is not unprecedented.

Take the energy sector. Business owners are constantly looking for ways to make their buildings run more efficiently. But for a long time, they had no way of knowing how their energy use stacked up against building owners of a similar size and region. The Energy Department put forth a solution: a national database of anonymized real-life buildings and their energy data, to which any organization can submit their building portfolio's data, and which anyone can access to analyze and compare data from a similar subset of buildings (say, in their region). This allows users of the data to gain a better understanding of trends and market conditions. Equipped with this information, they can make more-informed investment decisions.

NIST can do the same for cybersecurity metrics. They should coordinate with the Homeland Security Department, which has done some preliminary work in this area.

Of course, this is no easy task. The sensitivity of cybersecurity data adds a number of complexities that must be addressed, but the immense value this would provide would be worth the effort. It would allow everyone from CISOs to policymakers to cyber insurance companies to inform their decisions with real-world data. There's a path forward, but it will require a concerted effort by government, cybersecurity vendors, and businesses.

First, NIST must put forth a core set of common metrics that all organizations should strive toward knowing about their IT and cybersecurity capabilities. These don't need to be exhaustive or mandatory. But they should cover the basic and most meaningful components of cyber hygiene, such as the ratio of managed to unmanaged assets, the mean time to remediate an incident, and the mean time to implement a patch across an organization's network. NIST should engage industry and government to develop and agree on these metrics.

Second, NIST should develop standardized criteria for third-party auditors to verify organizations' cybersecurity metrics. Rather than acting as an auditor itself, NIST could certify third-party auditors and give them the federal government's stamp of approval, creating a system that could work at a national scale.

Third, NIST, working with Congress and industry, should develop the necessary market and legal incentives and infrastructure – such as a publicly accessible database managed by NIST or a nonprofit organization and accessible to industry — for organizations to share these metrics. Any data that private organizations choose to submit to the database must be done so voluntarily, and must be cleansed and anonymized. Businesses should receive full certainty that they will never be legally punished for submitting data.

If implemented correctly, these efforts could spur an entirely new approach to cybersecurity — one that's market-driven and data-backed.

CISOs would have not only consistent metrics to measure performance but also an industry standard to strive toward. Just as some utilities now include on your energy bill data about your neighbors' energy usage, CISOs would know the average time to patch their systems, based on organizations of similar size and sector.

Policymakers would have hard data to shape cybersecurity policies. Currently, they're forced to rely on meetings with vendors, who might tell them a dozen different indicators they should focus on. This solution would fix that, helping create policy supported by real-world evidence of what constitutes best-in-class, and what's no longer acceptable in today's threat environment.

The fast-growing cyber-insurance market would also benefit. With a standardized framework and metrics for measuring cybersecurity, insurers could better assess organizations' risk and develop standard report procedures, like a 10-K report businesses submit to the Securities and Exchange Commission.

Of course, for this approach to work, organizations must first be able to access these key metrics about their networks and do so in a timely and accurate manner. Although many organizations are certainly making progress in this regard, many will have to adopt software solutions to enable them to collect this data.

As breaches abound, it's become all too clear our current approach to cybersecurity is failing. Instead of more regulations, what we need is more data, better access to that data, and a framework by which to collect it and compare it across companies and industries. If we do that, we will go a long way toward securing the devices and networks on which our economy relies.

Related Content:

David Damato is Chief Security Officer at Tanium, where he provides strategic product direction over module development for the Tanium Platform and manages the company's internal security program. David brings a wealth of security expertise, spanning incident response and ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-20327
PUBLISHED: 2021-02-25
A specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Node....
CVE-2021-20328
PUBLISHED: 2021-02-25
Specific versions of the Java driver that support client-side field level encryption (CSFLE) fail to perform correct host name verification on the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in inte...
CVE-2020-27543
PUBLISHED: 2021-02-25
The restify-paginate package 0.0.5 for Node.js allows remote attackers to cause a Denial-of-Service by omitting the HTTP Host header. A Restify-based web service would crash with an uncaught exception.
CVE-2020-23534
PUBLISHED: 2021-02-25
A server-side request forgery (SSRF) vulnerability in Upgrade.php of gopeak masterlab 2.1.5, via the 'source' parameter.
CVE-2021-27330
PUBLISHED: 2021-02-25
Triconsole Datepicker Calendar <3.77 is affected by cross-site scripting (XSS) in calendar_form.php. Attackers can read authentication cookies that are still active, which can be used to perform further attacks such as reading browser history, directory listings, and file contents.