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

2/6/2019
09:00 AM
Jai Vijayan
Jai Vijayan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail

7 Tips for Communicating with the Board

The key? Rather than getting bogged down in the technical details, focus on how a security program is addressing business risk.
2 of 8

1. Use Metrics That Relate to Business Objectives
Board members and other business leaders are not security experts. Metrics on vulnerability reduction, threats blocked, and attacks mitigated are more meaningful when presented in the overall context of business risk reduction.
'Metrics should be related directly to business objectives,' says Chris Morales, head of security analytics at Vectra. 'How does operational process impact the company's ability to respond, and how does that relate to selling product in the market?' 
Numbers also should reflect simple trends based on objectives. 'No one at the board level cares about how much malware you blocked every month,' he notes.
Image Source: Shutterstock

1. Use Metrics That Relate to Business Objectives

Board members and other business leaders are not security experts. Metrics on vulnerability reduction, threats blocked, and attacks mitigated are more meaningful when presented in the overall context of business risk reduction.

"Metrics should be related directly to business objectives," says Chris Morales, head of security analytics at Vectra. "How does operational process impact the company's ability to respond, and how does that relate to selling product in the market?"

Numbers also should reflect simple trends based on objectives. "No one at the board level cares about how much malware you blocked every month," he notes.

Image Source: Shutterstock

2 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
csoandy
50%
50%
csoandy,
User Rank: Author
2/13/2019 | 10:25:19 AM
Too tactical
"Don't use FUD" might be the best advice here, even if "highlight legal consequences" doesn't follow it. The goal is to meet the Directors where they are. Understand their goals & beliefs, and work to meet them there. Explain the implications of recent news. Discuss the long term implications of risk — and highlight the benefits of wise risk choices being made. Don't be seen as the person who only criticized the business.
97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
TeamViewer Admits Breach from 2016
Dark Reading Staff 5/20/2019
How a Manufacturing Firm Recovered from a Devastating Ransomware Attack
Kelly Jackson Higgins, Executive Editor at Dark Reading,  5/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5798
PUBLISHED: 2019-05-23
Lack of correct bounds checking in Skia in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.
CVE-2019-5799
PUBLISHED: 2019-05-23
Incorrect inheritance of a new document's policy in Content Security Policy in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security policy via a crafted HTML page.
CVE-2019-5800
PUBLISHED: 2019-05-23
Insufficient policy enforcement in Blink in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security policy via a crafted HTML page.
CVE-2019-5801
PUBLISHED: 2019-05-23
Incorrect eliding of URLs in Omnibox in Google Chrome on iOS prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing via a crafted HTML page.
CVE-2019-5802
PUBLISHED: 2019-05-23
Incorrect handling of download origins in Navigation in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to perform domain spoofing via a crafted HTML page.