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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
KPMG Study: Breaches Up, Security Spending Down
Newest First  |  Oldest First  |  Threaded View
Page 1 / 3   >   >>
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
8/1/2016 | 7:30:37 AM
Re: Proactivity vs Reactivity
@Ryan: For that matter, how do you feel about the relationship between the CISO, the CCO, and the CPO?  In many organizations, one of these does the job of another -- if not all three.
RyanSepe
RyanSepe,
 User Rank: Ninja
7/31/2016 | 10:15:55 PM
Re: Proactivity vs Reactivity
Also a divorce of the roles is probably for the best.
RyanSepe
RyanSepe,
 User Rank: Ninja
7/31/2016 | 10:08:15 PM
Re: Proactivity vs Reactivity
I've put a lot of thought into this conflict of interest in the past between the CIO's goals and the CISO's. As you stated in your article, the success metrics for each is different. Cyber Security is more of a cost saving mechanism than a revenue earning mechanism, and unfortunately for InfoSec professionals the latter is held in higher regard.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
7/30/2016 | 7:26:56 AM
Re: Proactivity vs Reactivity
Indeed, even the federal government has taken note of the CIO-CISO conflict of interest.  Capitol Hill Republicans have proposed having the CISO of the Department of Health and Human Services answer to the General Counsel, as can be seen in this report from last year: energycommerce.house.gov/sites/republicans.energycommerce.house.gov/files/114/Analysis/20150806HHSinformationsecurityreport.pdf

Now, a bipartisan bill before Congress proposes separating the office of the DHHS CISO entirely -- completely divorcing the role of the CIO.  See, e.g., fcw.com/articles/2016/05/27/hhs-ciso-hearing.aspx
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
7/30/2016 | 7:23:30 AM
Re: Proactivity vs Reactivity
@RyanSepe: The notion isn't novel -- and one of the primary justifications for it is that the CISO and the CIO have an inherent conflict of interest.

I wrote about it for InformationWeek last year, in fact: informationweek.com/strategic-cio/cyber-security-and-the-cio-changing-the-conversation/a/d-id/1320660
GonzSTL
GonzSTL,
 User Rank: Ninja
7/29/2016 | 3:47:59 PM
Re: Proactivity vs Reactivity
Personally, I think that cybersecurity has come to the point where it really is its own discipline. When it comes to protecting an organization, cybersecurity has to have an equal voice at the table, and any tiebreaker should come from the one who is responsible for the organization as a whole. That usually falls on the shoulders of the CEO. Anytime you place security under another line, it takes a back seat and no longer has a fair voice at the table. For instance, if the CISO falls under the CIO, there is an inherent conflict of interest. IT is tasked with delivering technology to enable the business, whereas security needs to ensure that the technology is safely delivered (an oversimplification, I know, but it illustrates the point). If a situation arises where those come into conflict, IT generally overrules security. I have seen this happen. I have seen a CIO reclassify a security position because IT needed another FTE and did not have an open req. How does that help security? In that particular case, the security position that was reclassified was never reinstated or replaced. It was a permanent loss for security.
RyanSepe
RyanSepe,
 User Rank: Ninja
7/29/2016 | 1:54:47 PM
Re: Proactivity vs Reactivity
That's an interesting point of view that I have yet to hear having the CISO under the CFO. Definitely seems plausible. Typically what I have seen is the CISO under the CIO. Do you think it would be more beneficial to have the CISO under the CFO, like you stated, or on the same level as the CFO all under the CEO?
RyanSepe
RyanSepe,
 User Rank: Ninja
7/29/2016 | 1:52:20 PM
Re: 20% ?
Yes, I have heard variations of this same premise elsewhere. I do agree with this to a certain extent. I think what it comes down to was how severe was the hack.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
7/29/2016 | 1:29:13 PM
Re: Proactivity vs Reactivity
@Dr.T: Yet another (of many) reasons the CISO should report directly to the CFO.  If security comes more directly under the CFO's purview, the fallout of a breach or data loss/compromise will hit the CFO more directly.  Then they'll start budgeting better.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
7/29/2016 | 1:27:23 PM
Re: 20% ?
An MIT Professor and cybersecurity expert I know, Stuart Madnick, always has this quip to share at every presentation he gives: "There are two types of organizations: Those that know they've been hacked, and those that don't know they've been hacked."
Page 1 / 3   >   >>


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
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file