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.

Comments
Who Does What in Cybersecurity at the C-Level
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: Moderator
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: Strategist
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 !


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.