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

11/12/2016
09:00 AM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Security Metrics Checklist

Which metrics are the best indicators of a strong cybersecurity team? Experts say security pros should be recording and reporting these data points to demonstrate their success.
Previous
1 of 9
Next

It's easy to assume the best sign of security success is an absence of malicious activity. However, it's unrealistic for security pros to adopt the "no news is good news" approach to defense, security experts say.

Pete Lindstrom, vice president of security research with IDC's executive program, says the argument of "when we're successful, nothing happens," is the wrong approach. He says security departments tend to focus more on incidents and less on the "bits and bytes" of their programs.

CISOs, IT managers, and other security leaders need to record and report metrics to their CIOs and business executives to demonstrate the performance of their teams. But right now, most security teams lack definitive guidelines for gauging their success.

"The challenge with measuring security metrics is you never know what your security operations are not seeing," explains Jeff Schilling, chief of customer operations and security at Armor. This causes some metrics, like the number of hosts, to be false because teams have a tough time parsing false positives and don't know if they're finding all their infected hosts.

With so many unknowns, he continues, it's difficult to paint a full picture of performance. 

There are a few metrics today's security leaders are studying to gauge the success of their employees, explains Joseph Carson, CISSP, who handles EMEA product marketing and global strategic alliances for Thycotic. 

Some businesses measure their success by the number of security incidents they are experiencing and handling at any point in time, for instance. Others evaluate their system vulnerabilities by recording where their systems are patched, where they have been exposed, and the number of identified viruses trying to compromise systems within the organization, he says.

Security pros also evaluate the behavior of the perimeter, and record instances like firewall incidents and potentially dangerous websites. The number of solutions implemented is another common metric considered when evaluating security posture.

"Most of these things relate to different types of security measurements," Carson says. "But it also comes down to how well organizations can collect inventory from Web system applications and users in the environment." 

The problem with many of these metrics is they don't bridge the gap between business and security. Security pros should be focusing on metrics like the location and accuracy of information, and efficiency of alerts, to paint a better picture of their security strategies. 

"Many of the metrics we measure today don't translate into the business," Carson explains. "If an incident occurs, what is the business impact?" 

Here are eight key metrics for measuring the success (or failure) of a security program:

 

 

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Previous
1 of 9
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
More SolarWinds Attack Details Emerge
Kelly Jackson Higgins, Executive Editor at Dark Reading,  1/12/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-36192
PUBLISHED: 2021-01-18
An issue was discovered in the Source Integration plugin before 2.4.1 for MantisBT. An attacker can gain access to the Summary field of private Issues (either marked as Private, or part of a private Project), if they are attached to an existing Changeset. The information is visible on the view.php p...
CVE-2020-36193
PUBLISHED: 2021-01-18
Tar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.
CVE-2020-7343
PUBLISHED: 2021-01-18
Missing Authorization vulnerability in McAfee Agent (MA) for Windows prior to 5.7.1 allows local users to block McAfee product updates by manipulating a directory used by MA for temporary files. The product would continue to function with out-of-date detection files.
CVE-2020-28476
PUBLISHED: 2021-01-18
All versions of package tornado are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configura...
CVE-2020-28473
PUBLISHED: 2021-01-18
The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with defa...