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
Talking Cyber-Risk with Executives
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
dunsany
50%
50%
dunsany,
User Rank: Apprentice
7/11/2017 | 11:30:22 AM
Who should the CSO report to
As promised, here's my blog on CISO reporting structures at F5 Labs

F5 Labs - Who Should the CISO Report To

 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
7/2/2017 | 12:11:44 AM
Re: Reporting/communicating to whom?
@Christian: Moreover, what often fails to be recognized here is that sometimes the ROI is the avoidance of even greater negative ROI.

Which, technically, is a positive.

Really, more executives need to know more about risk assessment. That's what it comes down to.
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
6/30/2017 | 11:43:59 AM
Re: Reporting/communicating to whom?
While I understand Dr. T's comment about security and money, and to some extent agree, I also know from experience that I can never - repeat, never - walk into any manager's office without a cost/savings breakdown of some sort to get a decision, buy-in, support. 

Having done it for so long, I guess I no longer see it as pointless if it means I get the resources I need to make something happen that I know isn't about the money, but all about the security.  The bosses know you have to spend money to make money, but ultimately that ROI has got to be laid out, even if the monetary return is minimal.  Selling a secure environment is all the easier when there is at least some savings and commercial gain attached.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/29/2017 | 9:24:19 AM
Re: Reporting/communicating to whom?
@Dr.T: I'm not sure that's possible, first of all (for reasons not least of which including the inherent conflict of interest that the CIO's job has with the CISO's job), but why do you think that it should not matter?
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/28/2017 | 9:13:13 PM
Re: Reporting/communicating to whom?
@Raymond: Extending these questions even further, then, what about the Chief Privacy Officer or similarly situated role/office? Also to the COO? To the CISO? to...?
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/28/2017 | 9:12:06 PM
Re: Reporting/communicating to whom?
@Dr. T: Security is about money, though -- or, at least, about economic value. Ditto for security's exact opposite -- accessibility.

It's all about risk management at the end of the day. Seems like something right up the CFO's alley. Of course, for the same reasons, also sounds like something right up the CLO or General Counsel's alley.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/28/2017 | 9:10:41 PM
Re: Reporting/communicating to whom?
@Raymond: Sounds about right to me. I've seen a variety of solutions to keep the CISO from reporting to the CIO. Where do you see the trends happening in terms of who this person to whom the CISO is? Is there one office that seems to be "winning" in this regard?
dunsany
50%
50%
dunsany,
User Rank: Apprentice
6/27/2017 | 5:23:36 PM
Re: Reporting/communicating to whom?
For most organizations, risk translates into monetary loss in one form or another.  It's not ideal in the human-world but in the corporate-world of lost revenues and liability lawsuits, money is a powerful measure for security loss avoidance.  The big problem is justifying potential dollar loss vs spending on controls to a CFO-type who sees only the sure loss of budget drain for new controls.  In my experience, I've had the most sucesses as head of security reporting to COO, who cares about operational effectiveness as well maintaining customer satisfication.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/27/2017 | 4:26:35 PM
customers
"Current and future customer perception and loss"

I think this is where everything starts being problematic, no business without customers. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/27/2017 | 4:24:44 PM
Re: Reporting/communicating to whom?
"the CISO should report outside of IT"

This sounds like a good idea to avoid conflict of interest.
Page 1 / 2   >   >>


COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/14/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Hacking It as a CISO: Advice for Security Leadership
Kelly Sheridan, Staff Editor, Dark Reading,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 New Cybersecurity Vulnerabilities That Could Put Your Enterprise at Risk
In this Dark Reading Tech Digest, we look at the ways security researchers and ethical hackers find critical vulnerabilities and offer insights into how you can fix them before attackers can exploit them.
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-7700
PUBLISHED: 2020-08-14
All versions of phpjs are vulnerable to Prototype Pollution via parse_str.
CVE-2020-7701
PUBLISHED: 2020-08-14
madlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue.
CVE-2020-9228
PUBLISHED: 2020-08-14
FusionCompute 8.0.0 has an information disclosure vulnerability. Due to the properly protection of certain information, attackers may exploit this vulnerability to obtain certain information.
CVE-2020-9229
PUBLISHED: 2020-08-14
FusionCompute 8.0.0 has an information disclosure vulnerability. Due to the properly protection of certain information, attackers may exploit this vulnerability to obtain certain information.
CVE-2019-19643
PUBLISHED: 2020-08-14
ise smart connect KNX Vaillant 1.2.839 contain a Denial of Service.