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

Image Source: Shutterstock

Image Source: Shutterstock

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.
New Free Tool Scans for Chrome Extension Safety
Dark Reading Staff 2/21/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6485
PUBLISHED: 2019-02-22
Citrix NetScaler Gateway 12.1 before build 50.31, 12.0 before build 60.9, 11.1 before build 60.14, 11.0 before build 72.17, and 10.5 before build 69.5 and Application Delivery Controller (ADC) 12.1 before build 50.31, 12.0 before build 60.9, 11.1 before build 60.14, 11.0 before build 72.17, and 10.5...
CVE-2019-9020
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. Invalid input to the function xmlrpc_decode() can lead to an invalid memory access (heap out of bounds read or read after free). This is related to xml_elem_parse_buf in ext/xmlrpc/libxmlrpc...
CVE-2019-9021
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. A heap-based buffer over-read in PHAR reading functions in the PHAR extension may allow an attacker to read allocated or unallocated memory past the actual data when trying to parse the file...
CVE-2019-9022
PUBLISHED: 2019-02-22
An issue was discovered in PHP 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.2. dns_get_record misparses a DNS response, which can allow a hostile DNS server to cause PHP to misuse memcpy, leading to read operations going past the buffer allocated for DNS data. This affects php_parser...
CVE-2019-9023
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. A number of heap-based buffer over-read instances are present in mbstring regular expression functions when supplied with invalid multibyte data. These occur in ext/mbstring/oniguruma/regcom...