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.


05:00 PM
Connect Directly

Frenemies Of The C-Suite: CSO, CIO, CRO, CPO

Sometimes the security, IT, risk, and privacy offices just can't get along.

Fifteen-year-old girls are the go-to experts on the phenomenon of a "frenemy" -- a person who is both your friend and your enemy. Yet, even 15-year-old girls would agree that leaders of security, privacy, risk, and IT departments know just as much about those kinds of complex, melodramatic relationships. 

Part of the problem: "There are too many chiefs, and none of them are really chiefs," says Jason Straight, senior vice president and chief privacy officer at UnitedLex. 

In very general and traditional terms, chief privacy officers come from legal backgrounds, chief risk officers mostly business/finance, and chief information officers and security officers from technology.

Some conflicts are avoidable. Others are necessary, but can be less painful if you approach them from the right mindset. And there are actually great opportunities for friendship, if you know where to look. 

Conflict and opportunity: What does 'risk' mean?

CPOs focus on data and compliance. That's pretty standard. CIOs focus on how IT can support and drive the business. Again: that's pretty clear. CROs and CISO/CSOs however, have rather confusing directives.

Unlike risk officers, security professionals are averse to risk and want more authority to make decisions instead of just give advice. Yet they've been encouraged to loosen up, stop unplugging and locking up everything, and told "why can't you be more like the CRO?" 

That can cause some friction. However, risk officers have their own troubles, and they need security experts help to solve it.

Market risk, operational risk, credit risk and enterprise risk have been in the school books for ages, but information and technology risk are new realms for risk officers. 

"Lots of risk officers are saying 'I don't feel comfortable with the information side, but I've gotta be that guy now, too,'" says John Pironti, president of IP Architects. Big data collection, he says, is just too fundamental a part of any business to ignore. This is a place where security officers and risk officers can begin to understand each other.

Conflict: The CISO reports to the CIO

"The biggest place I see conflict is when the CSO reports to the CIO," says Pironti. "It's a problem of what merits they're judged by. Security guys are not going to tell you to do things in the most efficient way. That's not a criticism. It's just not their job."

The trouble of course, is that when a major security incident happens and someone's looking for a scapegoat, the CISO may be penalized for failures that only happened because the CISO's decisions were overruled by the CIO.

The only solution here, is to move the CISO elsewhere: under the CEO, the CFO, or the CRO, but definitely not the CIO.

Conflict: "Where's the data?"

It's often the CPO who comes with the question. Personally identifiable information is collected from hither and thither. A job application here, a web form there. 

"You get this tension," says Straight. "Nobody really knows where this stuff is." And if the CPO, for example, says that a privacy law will grant them Safe Harbor if they can encrypt that data, everyone' may be, Straight says, "'Well good for you, but I don't have the budget to go find it.'"

The CSO, CRO and CPO may all agree that it's in the best interest of the company, its security and its compliance to discover and lock down that data, but it's rare that anyone really has clear ownership of it.  

[Everything you need to know about today’s IT security challenges – but were afraid to ask. Register with Discount Code DRBLOG to save $100 for this special one-day event, Dark Reading's Cyber Security Crash Course at Interop on Wednesday, April 29.]

Conflict: CPO and the CSO have an unequal relationship

"You can't have privacy without security," says Straight, "but you can have a perfect security program without privacy. And both [the CPO and CSO] know that."

Sure, the security department is going to plan on nailing on databases, but there could be those occasions that they meet a CPO with a roll of the eyes and a dismissive wave of the hand. 

On the other hand, the two could bond over the fact that they are both unappreciated by the CIO and application developers. 

"Security is usually an afterthought," says Straight, "and privacy is usually not a thought at all."

Friendship opportunity: Cyberinsurance

When there's a data breach -- and don't worry, there will be -- someone has got to pay. The field of cyber liability insurance is so new and so confusing that everyone is looking to each other for answers.

"The CPO, CRO and CSO all have interst in cyberinsurance and privacy liability," says Straight, "and it's had a positive effect" on those relationships.

If all else fails, you can always bond over shared disdain for the chief marketing officer.

Check out John Pironti's and Jason Straight's sessions at Interop Las Vegas, April 27 to May 1.  

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Strategist
3/23/2015 | 3:04:17 PM
I think I see why we're failing now.

The trouble of course, is that when a major security incident happens and someone's looking for a scapegoat, the CISO may be penalized for failures that only happened because the CISO's decisions were overruled by the CIO.

The only solution here, is to move the CISO elsewhere: under the CEO, the CFO, or the CRO, but definitely not the CIO.

NO! No, it isn't‼! The solution is to make CIOs responsible for the security of their IT services and to hold them to account for poor outcomes!!!!


User Rank: Moderator
3/20/2015 | 6:39:25 AM
Re: Cybeinsurance
Cyberinsurance will not protect you if you are negligent, where you have failed to follow typical, industry recommended approaches.  If you fail to staff security with enough people to be minimally effective, fail to monitor, fail to respond, or simply fail to have reasonable security controls in place, cyberinsurance will not cover you.  Equally important, cyberinsurance will not prevent media attention, or damaged brand, or lost customers.  Does it have a place in the portfolio?  Yes, certainly.  Just as long as its an additive solution and not a replacement for real security staff.

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
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
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could b...
PUBLISHED: 2020-01-23
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3...
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.
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.