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   >   >>


Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.
CVE-2019-20391
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20392
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20393
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.