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


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-42258
PUBLISHED: 2021-10-22
BQE BillQuick Web Suite 2018 through 2021 before 22.0.9.1 allows SQL injection for unauthenticated remote code execution, as exploited in the wild in October 2021 for ransomware installation. SQL injection can, for example, use the txtID (aka username) parameter. Successful exploitation can include ...
CVE-2020-28968
PUBLISHED: 2021-10-22
Draytek VigorAP 1000C contains a stored cross-site scripting (XSS) vulnerability in the RADIUS Setting - RADIUS Server Configuration module. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the username input field.
CVE-2020-28969
PUBLISHED: 2021-10-22
Aplioxio PDF ShapingUp 5.0.0.139 contains a buffer overflow which allows attackers to cause a denial of service (DoS) via a crafted PDF file.
CVE-2020-36485
PUBLISHED: 2021-10-22
Portable Ltd Playable v9.18 was discovered to contain an arbitrary file upload vulnerability in the filename parameter of the upload module. This vulnerability allows attackers to execute arbitrary code via a crafted JPEG file.
CVE-2020-36486
PUBLISHED: 2021-10-22
Swift File Transfer Mobile v1.1.2 and below was discovered to contain a cross-site scripting (XSS) vulnerability via the 'path' parameter of the 'list' and 'download' exception-handling.