Given my situation, I am thinking a lot about what makes a good ciso. I don’t think I was particularly good, but that’s another story.

I am curious what the community thinks makes a good CISO, at least from one narrow perspective. Do you think CISOs should be:

Deeply technical
35.8%
Marginally technical, mainly business
60.6%
All business, technical stuff if what employees are for
3.7%
Poll ended at .
@jerry large insurance policy
@jerry compared to cto they may just be semi deeply technical but still... good communication and be able to delegate is probably ciso strong suit , optimally, - my 2 cents #c-suite
@jerry 50/50 split? You need both to get the tech and the business, otherwise you're creating tech debt/ shadow it, or alienating the part that makes money to be able to invest/pay ppl

@jerry

[ ] Both technical and business

I know it's a unicorn -- but it seems very difficult for a CISO to not have a healthy helping of both.

@jerry A CISO has to be able to convince the CEO and the Board to fund security initiatives. A CISO will have to make the business case to them that it is worth the investment. That is the most important thing a CISO can do.
@jerry Depends on the size of the company / team?
@jerry it's not simple. A CISO must have good technical skills to understand and defend their organisation's threat model. But they also need good business skills to explain things to their colleagues.

@jerry NB: this definitely struck a nerve of mine regarding C suite tech roles & their titles.

I'm willing to bet I skewed your data based on that. 🤷

@jerry

Probably a pair of people, one business, one technical.

But overall I'm frustrated with business, law, and finance. They have this nasty habit of folding in on themselves and becoming an arms race that sucks all the air out of the room.

@jerry Be technical enough to understand the threat landscape and effectiveness of measures, instead of just following compliance requirements
@jerry That really depends on the size of your organisation doesn't it ?
I don't expect the CISO of a large organisation to be a technical person, but a smaller org may need a person like that.
@jerry
You need to be able to convince the business to do things and you need to have staff you trust. To be deeply technical you probably have to be doing the work, and you don't have time to do both.

@jerry it needs to be someone who has cred with both the tech/security part of the org, and the board. So they need one foot in both worlds.

The entire problem is that tech and biz speak different languages; the CISO needs to be a translation layer that can balance their different priorities.

@jerry when i was in the lower rungs of the corporate world, I use to feel top bosses should be highly technical in nature then only they can understand us. the more i rise up the more i feel being a techy puts a lot of limitation on the way i approach a topic. a non technical person, management focused approaches things differently and at top level frankly you have enough people below you to help with tech you do need to be able to navigate the company politics, realtionships and being able to present points forward (almost like an anti geek list of things to be able to do)
@jerry the best CISOs I've seen or worked with are technical enough to sniff out ~~bullsh~~ fertilizer, and to listen when the more deeply technical resources were trying to explain something that they didn't know how to articulate at a higher level. They are also in tune with the organization's business priorities, and recognized that the best way to support their team was to educate their peers, prioritize limited resources, and successfully advocate for necessary funds and solutions while somehow knowing which hills to avoid dying on.
@jerry I think they should be technical enough to call BS on their team and business savvy enough to call BS on other execs.

@jerry I was the marginally technical, mostly business CISO. I knew the things that needed to be done but probably not all the fine details of how to do the work. I’m always happy to learn and get my hands dirty, but sometimes that derails me making progress in other areas.

Prime example, I know what’s required to check the various boxes for CMMC and can ask the questions to determine if we have the process in place, but I may not know exactly what the steps are to make that process work.

@jerry « was deeply technical, then become business aware » is different from marginally technical…

@jerry
Above all CISOs need:
An unbelievably robust tolerance for inadequacy which makes any security achieved a delightful surprise. A capacity for accepting the limits of influence & control; that any marginal security gain may be “good enough for who it’s for”.

As a bonus: talent for having criticism delivered, received as praise.

@jerry

They just need to be able to take the blame when the time comes and get replaced by the new guy.

@jerry d) very capable in risk management & policy / process development, with enough technical knowledge to understand where risks arise in technical systems and to be able to liaise with both the tech people & the business system owners (a.k.a. risk owners) 🙃
@jerry I have difficulties with the option. My choice would be „good communicator“ which is neither„business“ nor „technical“. You must be able to speak with both sides.
@jerry In Sales, I learned that what drives people is what is important to their boss/what they get MBO-ed on. CISOs typically work for CXOs who are MBO-ed on business results. My guess is that CISOs need to be mostly business.
(Just in case, MBO=Management by Objective pay bonus)
@dennisfaucher @jerry Mostly business but technical enough to understand the outlines of what their tech folks are saying and translate between tech speak and business speak.
@dennisfaucher as a CISO, that was how my compensation worked too. So I deeply understand

@jerry

I think they should be technical enough to call BS on their team and business savvy enough to call BS on other execs.


This.

@jerry I'd say technical enough that your technical folks underneath you couldn't blind you with details, yet business-savvy enough to participate in CxO meetings and to both explain your division in human terms yet still fight for and get your needed budget.

This is my view from the sidelines, never been a CISO, never want to be one.

@jerry In my opinion, this was missing a level in between. I think you can see, by the weights of answers, that people agree that business and its processes are important but so is technical.

I’d say “deep technical roots/background” is important. It doesn’t need to be current or hands on anymore. But having the skill and ability to truly follow along a highly technical explanation, given by someone in an operations or threat detection team (even if somewhat detached by middle management) is a real win.

Having the respect of technical teams allows them to speak more freely, provide opinions, and allows them to trust that your decisions, while not always what they wanted, have taken in to consideration their point of view. Plus, it helps support the hiring and development of middle management with similarly appropriate technical skills.

The rest of the C*s will never care. So, the business acumen is what will come through in these conversations. I’ve heard it put by others “you speak ‘boffin’ don’t you?” - so even though the role by its nature is mostly GRC, the other C*’s will appreciate a “translator“.