Are Security Leaders Really That Incompetent?

Tuesday, April 24, 2012

Andrew Weidenhamer

Ad5130e786d13531cc0f2cde32dacd0f

Are Security Leaders that Incompetent or is Security Simply Still not a Priority within Organizations?

I’ve recently heard/read commentary on the panel discussion presented by Chris Nickerson, Marcus Ranum, and Alex Hutton at INFOSEC World 2012.

First, let me start off by saying I respect each of individual as being a thought leader in the industry and the contributions in which each have made to the Information Security field.

Let me also say, that I did not have a chance to actually attend INFOSEC World or have been able to actually watch the presentation. This is important as my comments are based off second and third hand explanation of the talk and I apologize if I have taken anything out of original context.

From my understanding, the main point of the discussion was that security leaders aren’t prioritizing security initiatives appropriately and, in many cases, simply aren’t intelligent enough to protect their organizations. In my experience, I actually agree with both these points assuming that these points were actually made in the discussion.

However, I think what may have been missed or at least not emphasized, is that in many cases CSO’s/CISO’s aren’t the ones that are actually prioritizing security initiatives within the organizations but are simply executing or taking marching orders from those who are.

Let me use the movie Moneyball as an example. Brad Pitt, the GM of the Oakland Athletics, is tasked with putting a team together that is competitive on the field. As such, he approaches the owner to ask for money to be able to sign big name All Stars. The owner denies this request as the A's are a small market team and don’t have the same size wallet as a team such as the NY Yankees.

The obvious problem with this is that it is hard to compete against a big market team such as NY without allocating budget and spending money in order to be able to do so. As can be seen, the owner of the team was perfectly content in not improving his team significantly enough to actually be able to compete with the big boys.

Let me use another example. Let’s say my personal mission is to date the best looking girl in the world. I hire my best friend as my dating consultant and say “here is 200,000 dollars and the first thing I need is an Audi R8”.

My buddy understands what my mission is. Does the fact that he knows what my mission is help him better make decisions and prioritize objectives when I already told him what my first priority was? No. He is taking marching orders from me without having any real say as to what he actually believes is the best thing to do with that $200,000 which I allocated to him.

He could of course come back to me and say “Andrew, I think we should take the money and use it for plastic surgery as, being the expert in the field, I truly believe this better aligns with your mission.” That’s the only real option he has because at the end of the day, he is at the mercy of what I tell him to do assuming he wants to stay employed as my dating consultant.

How is this any different than what happens in the Information Security field? Typically when it comes to Information Security objectives are already determined by upper management.

Many times security leaders know what the right things to do are and what priorities the company SHOULD be focusing on, but because of the lack of budget, resources, other business objectives, politics, etc. have their hands tied to what their bosses tell them is important.

Many times, and as I believe discussed in the talk, these priorities are determined by regulatory mandates the organization is subject to. Obviously, most security professionals know that prioritizing security initiatives off regulatory mandates does very little at actually protecting your company.

However, if you are a CISO and the CEO (you would be lucky if you directly reported to the CEO as this typically is not the case) approaches you and says "we need to be PCI compliant or we are going to lose our ability to accept credit cards" that becomes your main objective and thus, is what you will be focusing on.

Nothing else matters at this point as you were directly told what your main priority is by your superior and, oh by the way, you have a family at home that relies on you having a good job.

Look, all I am trying to say, is that the individuals in which gave this presentation aren’t your average run-of-the mill security professionals. They are highly regarded within the industry and I doubt have many problems with getting budget and making decisions within their respective organizations. One of them is founder of his own company. Obviously he has no problem getting budget or prioritizing security initiatives as he reports to no one. It’s like the GM of the NY Yankees telling the GM of the Cleveland Indians that he has no idea how to run a baseball team. They aren’t operating on the same playing field.

With that said, I do believe there is a fundamental problem with those that are tasked with running a security organization. Many of them think because they have the CISSP certification, that somehow gives them the "know how" to be able to truly protect an organization and prioritize security initiatives off business objectives and company mission statements.

Again, I didn’t get the privilege of watching the presentation and apologize if I took something out of context. However, I have seen a lot of good security professionals fail not because they didn’t know how to protect the company, but because security wasn’t important to the company in which they were tasked to protect. These same security professionals thrived in other organizations that made security a top priority. 

- Andrew - @AWeidenhamer

3504
Enterprise Security
Post Rating I Like this!
1de705dde1cf97450678321cd77853d9
Ian Tibble You've pointed out valid observations on our beloved field of security, notably points about CISSP, directions coming from above, and compliance being the main driver. Forgive me but I would like to take it a step back in time, to discuss where this all came from. Let me re-iterate i completely agree with your comments and it's good to see someone on the same page.

I think we have to look at ourselves in the security field as to why CEOs have given us this direction - its primarily because we have not permitted ourselves to be trusted by C-levels. My book, especially chapter 1 deals with this in more detail, but there is some history here.

CEOs read about security in the FT and there are stories about incidents going back years, this isn't just a 2010-on story. Going back to the 90s, execs were asking CIOs about "what's all this hacking jazz, and what shall we do about it, if anything?" ...the main players at the time were hackers with no management layer in between. They were rude, abrasive, didn't fit in, casual Fridays, even on Mondays etc etc.

Early 2000s: The badly managed hackers were replaced with guys in suits and a full line of reporting from CISSP/MBA analyst up to the CISO. This latter version lacked confidence. They lacked confidence in their tools and their own knowledge of the firm's information assets, applications, and how well they were protected.

"Many of them think because they have the CISSP certification, that somehow gives them the "know how" to be able to truly protect an organization". What you say is right but this is an illusion of confidence, it's not real confidence. Nobody with purely CISSP as a source of knowledge really has any confidence in their professional capacity, even though they try to act confident. And guess what...who's the best person in the organization at sniffing out lack of confidence and lies? It's the C-levels. That's how they got to be C-levels. They don't know how to configure a firewall, fuzz, or reverse-engineer, but they sure do know a bullsh**er when they see one.

So...first there was people who couldn't speak business language who were badly managed. The industry did away with them and replaced with them folk who lacked confidence when reporting on the status of the business's information risk management program. We only have CISSP as a measure of professional qualification to do the job...does this work? Not really...at least not in the eyes of the C-levels.

At the end of this we have a situation where C-levels have never been well advised, and they know they have never been well advised. This is where security strategies based purely around low quality base compliance originates from. The C-levels set our agenda because they don't trust us to do it, and they won't trust us until we have a more suitable framework of professional accreditation (chapter 11 of my book) - ie. one that links security more closely with IT, and better tools (accurate automation).

1335356492
The views expressed in this post are the opinions of the Infosec Island member that posted this content. Infosec Island is not responsible for the content or messaging of this post.

Unauthorized reproduction of this article (in part or in whole) is prohibited without the express written permission of Infosec Island and the Infosec Island member that posted this content--this includes using our RSS feed for any purpose other than personal use.