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 Associate Editor at Dark Reading. She started her career in business tech journalism at Insurance & Technology and most recently reported for InformationWeek, where she covered Microsoft and business IT. Sheridan earned her BA at Villanova University. View Full Bio

Previous
1 of 9
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
Dark Reading Live EVENTS
INsecurity - For the Defenders of Enterprise Security
A Dark Reading Conference
While red team conferences focus primarily on new vulnerabilities and security researchers, INsecurity puts security execution, protection, and operations center stage. The primary speakers will be CISOs and leaders in security defense; the blue team will be the focus.
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: No, no, no! Have a Unix CRON do the pop-up reminders!
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
The Impact of a Security Breach 2017
The Impact of a Security Breach 2017
Despite the escalation of cybersecurity staffing and technology, enterprises continue to suffer data breaches and compromises at an alarming rate. How do these breaches occur? How are enterprises responding, and what is the impact of these compromises on the business? This report offers new data on the frequency of data breaches, the losses they cause, and the steps that organizations are taking to prevent them in the future.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.