Risk

3/16/2018
01:00 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Who Does What in Cybersecurity at the C-Level

As security evolve as a corporate priority, so do the roles and responsibilities of the executive team. These seven titles are already feeling the impact.
Previous
1 of 8
Next


Image Source: Shutterstock via Cartoon Resource

Image Source: Shutterstock via Cartoon Resource

What’s in a title? As the threat landscape grows more severe, job titles and lines of reporting will continue to change for security professionals. For example, last year’s CIO 100 found that 70% of CISOs report directly to the CIO, while IDC predicted that during 2018, 75% of CSOs and CISOs will report directly to the CEO.

Rob Clyde, a vice chair on the board of directors at ISACA, says just about all C-Suite players will have a seat on the board of directors in the future – and they’d better be ready.

"However technical these people are, they still have to understand the business and explain the technology to the board in plain English," Clyde says.

John McCumber, director of cybersecurity advocacy at ISC2, says the Chief Data Officer will continue to play a more important security role at many companies – and should have a seat at the table. "Organizations live and die by data," McCumber says. "We are coming to the end of the 'era of threat' and now have to accept that the threats will exist and that we have to deal with them."

Here's a look at seven important C-Suite job titles in security: CISO, CRO, CTO, CIO, CPO/CDO, CFO, and CAE, and their key security roles as defined by ISACA's Clyde and ISC2's McCumber. 

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/24/2018 | 6:58:08 AM
Re: CISOs and C levels
@szurier: Alas, one of many reasons why it has become so difficult to attract people to the role. That, and, of course, low salaries.

We don't have a cybersecurity talent shortage. We have a cybersecurity compensation shortage!
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/24/2018 | 6:56:41 AM
Re: C-level roles
@Brian: Not even at the federal level, either. I have a colleague who likes to say that "AG" doesn't stand for "Attorney General"; it really stands for "Aspiring Governor"!

It's a lot easier to keep the state AG's office (among other regulatory bodies) from hitting you with all kinds of fines and added oversight if you can demonstrate you're doing everything you can to rectify the situation -- and a sacrificial C-suite lamb goes a long way.
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
3/23/2018 | 1:43:18 PM
Re: C-level roles
Fine article, nicely outlines enterprise IT responsibilities. 

@Joe S.: Yes, calling C-levels on the carpet, so that congressional committee members can harang the "witnesses" and demonstrate their outrage to their constituents, is a lot easier than understanding the problem or providing solutions (or explaining why they, the legislators, failed to enact reasoned and pragmatic regulation, which would have prevented the incident, or limited the damage). 
szurier210
50%
50%
szurier210,
User Rank: Apprentice
3/23/2018 | 10:05:32 AM
Re: CISOs and C levels
Remember that CISO really means: Career Is Surely Over!!!
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/23/2018 | 10:02:28 AM
Re: CISOs and C levels
@gxmundy: Alas, your cynicism is on the mark. CISOs, CIOs, CTOs, and even CEOs are often the first to go -- sacrificed so as to appease politicians -- when a major breach splashes across the headlines.

Perhaps, however, if there was more uniformity as to how the CISO position worked and where it was placed in the org chart, there would be a better understanding of it to legitimize it further.

Whether an organization wants that or not, however, is a different story.
gxmundy@gmail.com
50%
50%
[email protected],
User Rank: Apprentice
3/22/2018 | 11:15:35 AM
CISOs and C levels
Who CISOs report to is a matter of deniability. That position is seen by C levels as the scapegoat for the eventual security breach. I agree that its a conflict in security terms to roll it under the CIO but its a business decision to not roll it under any other Executive.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/22/2018 | 10:40:48 AM
CISOs
It's eye-opening that so many CISOs continue to report to CIOs despite the clear conflict of interest between those two offices that has been discussed for a few years now ( and which I wrote about for Dark Reading's sister site, InformationWeek, here: informationweek.com/strategic-cio/cyber-security-and-the-cio-changing-the-conversation/a/d-id/1320660? ).

Still, I don't buy IDC's prediction (IDC tends to have pretty wild predictions and forecasts for the future, anyway) -- especially considering that there are so many other (probably better) alternatives for the CISO to report to. The CFO looks like it's the best choice, particularly as the CFO's role comes to encompass more types of risk assessment and risk management. The General Counsel is another viable alternative. (Some even go so far as to propose that the CISO report directly to the board, but that's really pushing things IMHO.)
antivirussupport12
50%
50%
antivirussupport12,
User Rank: Guru
3/17/2018 | 3:07:57 PM
Re: Who Does What in Cybersecurity at the C-Level
This post is good.
REISEN1955
100%
0%
REISEN1955,
User Rank: Ninja
3/16/2018 | 2:31:07 PM
For what it is worth - at Equivax
Simple: ignore the problem when it surfaces, sell stock before the problem is announced, blame the entire catastrophe on one (1) Information Tech hire,  Latter means a horrible implementation of protocols across the board.  
toprasage
50%
50%
toprasage,
User Rank: Apprentice
3/16/2018 | 1:26:29 PM
Who Does What in Cybersecurity at the C-Level
 "Organizations live and die by data,"

Totally agree !
Higher Education: 15 Books to Help Cybersecurity Pros Be Better
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
Worst Password Blunders of 2018 Hit Organizations East and West
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-20168
PUBLISHED: 2018-12-17
Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which allows attackers to cause a denial of service ("physical address not valid" panic) via a crafted application.
CVE-2018-20167
PUBLISHED: 2018-12-17
Terminology before 1.3.1 allows Remote Code Execution because popmedia is mishandled, as demonstrated by an unsafe "cat README.md" command when \e}pn is used. A popmedia control sequence can allow the malicious execution of executable file formats registered in the X desktop share MIME typ...
CVE-2018-20161
PUBLISHED: 2018-12-15
A design flaw in the BlinkForHome (aka Blink For Home) Sync Module 2.10.4 and earlier allows attackers to disable cameras via Wi-Fi, because incident clips (triggered by the motion sensor) are not saved if the attacker's traffic (such as Dot11Deauth) successfully disconnects the Sync Module from the...
CVE-2018-20159
PUBLISHED: 2018-12-15
i-doit open 1.11.2 allows Remote Code Execution because ZIP archives are mishandled. It has an upload feature that allows an authenticated user with the administrator role to upload arbitrary files to the main website directory. Exploitation involves uploading a ".php" file within a "...
CVE-2018-20157
PUBLISHED: 2018-12-15
The data import functionality in OpenRefine through 3.1 allows an XML External Entity (XXE) attack through a crafted (zip) file, allowing attackers to read arbitrary files.