Operations

11/12/2016
09:00 AM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
Google+
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

Image Source: Shutterstock

Image Source: Shutterstock

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

Previous
1 of 9
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The State of IT and Cybersecurity
The State of IT and Cybersecurity
IT and security are often viewed as different disciplines - and different departments. Find out what our survey data revealed, read the report today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-13435
PUBLISHED: 2018-08-16
** DISPUTED ** An issue was discovered in the LINE jp.naver.line application 8.8.0 for iOS. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method to disable passcode authentication. NOTE: the vendor indicates that this is not an attack of interest w...
CVE-2018-13446
PUBLISHED: 2018-08-16
** DISPUTED ** An issue was discovered in the LINE jp.naver.line application 8.8.1 for Android. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method's return value to true. In other words, an attacker could authenticate with an arbitrary passcode. ...
CVE-2018-14567
PUBLISHED: 2018-08-16
libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035 and CVE-2018-9251.
CVE-2018-15122
PUBLISHED: 2018-08-16
An issue found in Progress Telerik JustAssembly through 2018.1.323.2 and JustDecompile through 2018.2.605.0 makes it possible to execute code by decompiling a compiled .NET object (such as DLL or EXE) with an embedded resource file by clicking on the resource.
CVE-2018-11509
PUBLISHED: 2018-08-16
ASUSTOR ADM 3.1.0.RFQ3 uses the same default root:admin username and password as it does for the NAS itself for applications that are installed from the online repository. This may allow an attacker to login and upload a webshell.