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.

Operations

3/19/2015
05:00 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
JMacLeod
100%
0%
JMacLeod,
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!!!!

 

Paladium
100%
0%
Paladium,
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.

 
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-24028
PUBLISHED: 2021-04-14
An invalid free in Thrift's table-based serialization can cause the application to crash or potentially result in code execution or other undesirable effects. This issue affects Facebook Thrift prior to v2021.02.22.00.
CVE-2021-29370
PUBLISHED: 2021-04-13
A UXSS was discovered in the Thanos-Soft Cheetah Browser in Android 1.2.0 due to the inadequate filter of the intent scheme. This resulted in Cross-site scripting on the cheetah browser in any website.
CVE-2021-3460
PUBLISHED: 2021-04-13
The Motorola MH702x devices, prior to version 2.0.0.301, do not properly verify the server certificate during communication with the support server which could lead to the communication channel being accessible by an attacker.
CVE-2021-3462
PUBLISHED: 2021-04-13
A privilege escalation vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could allow unauthorized access to the driver's device object.
CVE-2021-3463
PUBLISHED: 2021-04-13
A null pointer dereference vulnerability in Lenovo Power Management Driver for Windows 10, prior to version 1.67.17.54, that could cause systems to experience a blue screen error.