CPSO Reporting Structure Part 2
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
8 hours 10 minutes
Hi, this is Matthew Clark. This is Lesson 2.5 sips. So reporting structures part two.
In this video, we will continue our discussion about possible places for the sip. So to report into including this large alphabet soup of positions
reporting to the CIS O or C so
So let's start with this is so the chief security officer and I pronounced this sis Oh, but and everyone pronounces both these words completely differently.
But the Cisco roll looks at the entire organizations risk, including physical security, compliance, fraud prevention, business continuity, financial risk, safety, ethics, privacy, reputation and brand protection.
It all changes in different on every organization.
But having the sips a report into the CIS so might not be a bad thing. This is a C suite roll. It handles all types of risk and generally doesn't have a P and l. It doesn't have a profit or loss.
And and this helps the sip. So not to be buried in a position way down in the weeds. In the organization,
this position can be very effective and reporting to the sea so as appear to the sea. So
let's talk about the sea so the chief information security officer.
The sips opposition could be effective reporting into the sea. So
because the ceases responsible for enterprise cybersecurity
in either position, the key to success is when the sys Oh, and the sea so understand that product security is different than enterprise information security. It's just not another flavor of cybersecurity.
If the company's main source of income is from connected products and services or their significant reputational or regulatory risk associated with connected products and services,
then it certainly makes sense for the soup, so to be positioned in a way that they can inform the business about products. Cybersecurity risk.
Just it's a cyst. So informs the business of information security risk.
Maybe that route is in person. Or maybe it's through the CSO or the sea. So or the CTO
Personally, I tend to believe that the closer and individual is to the top, the clear their messages and the less filters that they have.
So let's talk about the chief risk officer, the chief privacy officer and the chief legal officer.
Some organizations may wish tohave the chief product security officer reporting into an organization that doesn't have a P and L because they don't want this this kind of conflict to happen. And maybe the CSO role doesn't exist in those in that type of organization.
So these types of organizations both risk and privacy and legal could be good alternate solutions, depending on the organization.
So what? The one of the downfalls of this, though, is that the chief product security officer
We'll need to make sure that they communicate well what risk it are because these organizations arm or compliance, focused.
Then they are type, typically cybersecurity focused.
And so that means that there's gonna be distance between them and the final product. And that distance may impact their comprehension of the urgency. Are need a certain risk that are out there.
So CEO reporting into the chief information officer up with this in here because you know why not? The CEO is generally, um, in almost every single organization, and it may seem like a good fit for some people.
In many ways, this might be the opposite of placing the role within engineering. It may not feel like a natural fit because the focus of the CEO is generally on enterprise technology. They're more focused on the operational aspect of information technology.
And while I T might certainly know about production floor issues as an organization, there's gonna have layers of separation between them and the product development process.
And one of the risk is that the sip so becomes an observer to real action. They would end up
scheduling a meeting to be caught up on the latest engineering decision. Instead of being embedded in those groups, making those decisions
like engineering. This might be also be a source of natural conflict, which, granted might not be a bad thing.
But the see it I always is affected by P and l decisions.
So unless the organization is very immature, in the process is the CIA. You probably isn't a good fit.
And by that I mean that I've worked with some I t organizations that air so embedded in the business, um, that they are actually the keepers of the business process, information and investigation That might not be a bad fit, especially if the Sips organization is very immature and needs to Bill learned how to build business process
It could be the sip so is buried so far down in organizational layers that she feels like she's reporting to the abyss and never sees the light of day
to be effective. The Simpson needs to be able to communicate with C Suite,
And how is she going to be able to do that or get a time on the calendar when she's buried so far down and organizations address book?
Or worse yet, the sip, so is, has a title and name on Lee because she changed it on her email signature.
I spoke to a company a few years ago. It was a medium sized manufacturing company looking to hire, see So and that position reported to the CEO who reported the CTO who reported to the CEO. And it was a mess. Everyone in the organizational chain above the sea so said that they were personally responsible for security,
and they said it like they meant they actually were the ones who are accountable
for the program, the one who are making the decisions
and that doesn't work in the race. It
and it certainly doesn't work in the real world, and you can't do that or well, you shouldn't do that. I think many organizations try to do that. Bearing security isn't good for anyone.
Well, that's it for this lesson. In summary, we covered the advantages and disadvantages of different reporting structures for the sip. So
and that includes all this alphabet soup of positions as well as Theodorus.
I'll see you next time.