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
Oldest First  |  Newest First  |  Threaded View
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 !
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.  
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.
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.)
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/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.
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!!!
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). 
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.
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!


Commentary
Cyberattacks Are Tailored to Employees ... Why Isn't Security Training?
Tim Sadler, CEO and co-founder of Tessian,  6/17/2021
Edge-DRsplash-10-edge-articles
7 Powerful Cybersecurity Skills the Energy Sector Needs Most
Pam Baker, Contributing Writer,  6/22/2021
News
Microsoft Disrupts Large-Scale BEC Campaign Across Web Services
Kelly Sheridan, Staff Editor, Dark Reading,  6/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-34390
PUBLISHED: 2021-06-22
Trusty TLK contains a vulnerability in the NVIDIA TLK kernel function where a lack of checks allows the exploitation of an integer overflow on the size parameter of the tz_map_shared_mem function.
CVE-2021-34391
PUBLISHED: 2021-06-22
Trusty TLK contains a vulnerability in the NVIDIA TLK kernel�s tz_handle_trusted_app_smc function where a lack of integer overflow checks on the req_off and param_ofs variables leads to memory corruption of critical kernel structures.
CVE-2021-34392
PUBLISHED: 2021-06-22
Trusty TLK contains a vulnerability in the NVIDIA TLK kernel where an integer overflow in the tz_map_shared_mem function can bypass boundary checks, which might lead to denial of service.
CVE-2021-34393
PUBLISHED: 2021-06-22
Trusty contains a vulnerability in TSEC TA which deserializes the incoming messages even though the TSEC TA does not expose any command. This vulnerability might allow an attacker to exploit the deserializer to impact code execution, causing information disclosure.
CVE-2021-34394
PUBLISHED: 2021-06-22
Trusty contains a vulnerability in all TAs whose deserializer does not reject messages with multiple occurrences of the same parameter. The deserialization of untrusted data might allow an attacker to exploit the deserializer to impact code execution.