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
50%
50%

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.
Previous
1 of 8
Next

CISOs and other security leaders are under growing pressure to improve how they communicate with boards of directors.

Cybersecurity has become a board-level issue in many organizations amid growing concerns over the regulatory, financial, and reputational implications of data breaches and security failures. In fact, Gartner expects that by 2020, 100% of large organizations will be asked to report to their boards at least once annually on cybersecurity risk — up from the 40% that are required to do so currently.

That means security leaders will need to overcome their traditional communication challenges and find new and better ways to convey technology risk.

Ensuring board awareness about key metrics of cybersecurity programs has become critically important, says Greg Reber, partner at Moss Adams, a Seattle-based accounting, consulting, and wealth management firm. Board members need to be able to track not just cybersecurity events and actions, but also new and emerging threats. They also require a continuous assessment of how a program is doing, along with a road map of cybersecurity-related projects and their goals, Reber says.

"Cybersecurity is a relatively new risk but aligns very directly within traditional BoD oversight duties," he notes.

Here are the key steps for effectively communicating with the board.

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
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.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.
CVE-2020-13404
PUBLISHED: 2020-08-05
The ATOS/Sips (aka Atos-Magento) community module 3.0.0 to 3.0.5 for Magento allows command injection.
CVE-2020-15112
PUBLISHED: 2020-08-05
In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime pa...