This is an audio conversation from the CIO Talk Network podcast. The timestamps in the chapters and transcript below refer to the audio recording.
About this conversation
A CIO Talk Network conversation with John McClure (Sinclair Broadcast Group), Rob Hornbuckle (Allegiant Airlines), hosted by Sanjog Aul.
What the conversation established
The conversation established that security cannot be bolted on after digital decisions are made, and that both leaders see the function as a business enabler rather than a blocker. McClure said security will stay somewhat reactive because the business moves faster than security can rearchitect, and that early wins come from presenting risk in business terms, not from vanity counts like remediating 10,000 vulnerabilities. Hornbuckle argued for shifting left and shifting right at the same time, crediting that approach for more than 200 releases in a year, and for ranking exposure through a crown jewels assessment where misnavigating a plane is high protection and a two-hour payroll delay is not. Both agreed the CISO role is new, needs business and relationship skills, and should over time report outside IT, with McClure pointing to proposed SEC rules that raise board-level cyber visibility.
Host Sanjog Aul talks with John McClure, Chief Information Security Officer at Sinclair Broadcast Group, and Rob Hornbuckle, Chief Information Security Officer at Allegiant Airlines, about embedding security into fast-moving technology and digital work instead of adding it later. McClure describes security’s reactive position and the move from the office of no to the office of know, while Hornbuckle lays out shifting left and right, a crown jewels assessment for ranking risk, and treating vendors like members of the team. They compare how a broadcast media company and an airline set security priorities by risk, and debate where the CISO should report and what leadership skills the role now demands.
Contributors
- John McClure, Chief Information Security Officer, Sinclair Broadcast Group
- Rob Hornbuckle, Chief Information Security Officer, Allegiant Airlines
Host: Sanjog Aul, Founder and Host, CIO Talk Network
On this page: Key takeaways · Chapters · Explore more · Transcript
Key takeaways
- John McClure, CISO at Sinclair Broadcast Group, says security will always remain somewhat reactive because the business moves faster than security can rearchitect or redesign. He argues the gap shrinks when security builds relationships across sales and business operations and gets pulled in early, but the catch me if you can dynamic never fully goes away.
- Rob Hornbuckle, CISO at Allegiant Airlines, says embedding security takes shifting left and shifting right at the same time, not just shifting left. He pushes some security responsibilities to other departments and runs security champion programs to build the other side, and credits that method for more than 200 releases at Allegiant in a year.
- Rob Hornbuckle, CISO at Allegiant Airlines, says it is not the CISO’s job to fully secure the organization but to make sure the business understands the risk it accepts. He ranks exposure with a crown jewels assessment, where something that could cause misnavigation of a plane is high protection and a two-hour payroll delay is not.
- John McClure, CISO at Sinclair Broadcast Group, says security should report risk in business terms rather than vanity metrics. He notes that telling leaders the team remediated 10,000 vulnerabilities means little, while reducing the probability of breach and the potential financial loss lands, and he frames the shift from the office of no to the office of know.
- Rob Hornbuckle, CISO at Allegiant Airlines, says the CISO is the youngest senior executive role and lacks the mature path that builds business skills in other functions. Unlike a CFO who learns business and relationship skills climbing the finance ranks, he says CISOs must deliberately learn them, and he spent his first of 2.5 years in role shaking hands and kissing babies.
- John McClure, CISO at Sinclair Broadcast Group, says the CISO should over time report outside IT, on par and peer with the CIO. He points to proposed SEC rules raising board-level visibility of cyber risk, and warns that staying embedded in IT makes it harder for the business to see security as a growing area that needs its own voice.
Chapters
- 0:00 Introduction: embedding security in technology capabilities
- 2:52 Why security plays catch up with digital
- 5:19 Shift left and shift right together
- 7:38 Does security training change behavior
- 10:57 The CISO’s job is to inform risk, not remove it
- 14:02 Building the right ecosystem of partners
- 18:47 From the office of no to the office of know
- 22:26 Why the CISO role demands business skills
- 27:53 Focusing on the highest risk areas first
- 37:12 Where security should report
- 45:52 Treating solution providers like your team
- 49:09 Leadership skills for the modern CISO
Explore more
- Your Security Checklist
- Government and Technology
- Should you marry your Technology Vendor?
- Managing IoT Security
- How Effective is Your Security Team?
- Top Technology Talks
Transcript
Introduction: embedding security in technology capabilities 0:00
Sanjog Aul [00:00:23]:
Today’s topic is Embedding Security In Technology Capabilities. What do I mean here? So when we are trying to go the digital route, we are building custom software applications. We are using third party software packages and tools. We are moving workloads to the cloud. We have infrastructure being recreated in the cloud, and there are also some things that we are trying to do to standardize our overall management of how things will work in the cloud or even a multi cloud environment. So all of that being done. Where is security in all of this? Has security been invited to the table, but with so much action going on, has security been able to holistically and consistently be embedded in all of these activities and finally whatever we end up creating, artifacts or workloads, etcetera, and when you try to do as security leaders, what has been the journey? What’s the pushback? What’s the support? What creativity have you tried to show to make sure at the end of it, the security is embedded in all of this by design upfront versus an afterthought? So what challenges are CISOs facing in doing so? And what are they using as strategies and techniques to address those challenges so that we get the best outcome? To discuss this, I have with me John McClure, who’s the chief information security officer with Sinclair Broadcast Group. Hey, John. How are you?
Sanjog Aul [00:02:12]:
Great to have you, and we have Rob Hornbuckle, who’s the chief information security officer with Allegiant Airlines. Hey, Rob. How’s life?
Sanjog Aul [00:02:24]:
So let’s start with you, John, first. Catch me if you can. I’m sure you and I and many of us have watched that movie. Is that what’s happening with security trying to chase the IT and the business leaders who want to go 1,000 miles an hour on the digital to keep security at par or embedded in the changes that they’re bringing about? What do you think is happening today?
Why security plays catch up with digital 2:52
John McClure [00:02:52]:
I think you’re right. We are playing a bit of catch up. I also think that you and I both know that movie might date us a little bit to some of our listeners here, but the catch me if you can, I think, is going to remain consistent in that way, unfortunately. I think it’s just a natural way of doing business. I don’t mean that it’s unfortunate that that’s the way the business operates. I just mean that I think in many cases, we will remain reactive. I think that we spend a lot of time working with the business, trying to be well integrated, well embedded, but normally the company or business lines will be coming out with technologies, offerings, integrations, ideas on how to grow the business in different ways, and then we need to be a bit adaptive to that, and that’s not just security. That’s the whole organization normally. I think that especially innovative companies that are gonna push that boundary, whether it’s on the business side, the technology side, operation side, we will need to remain reactive. I think there’s a lot of things we can do to help alleviate some of that pain that comes with that. I think being well integrated in the right parts of the business, creating the right relationships definitely across sales, business operations, and some of the other organizations within the organization help minimize how much of that gap you’re dealing with, how quickly they’re pulling you into things early on. I think you can shorten that gap, but I think we’re always gonna be playing a little bit of reactiveness, just because the speed of business frequently can move significantly quicker perhaps than the speed of rearchitecting or redesigning. Realizing that the cloud and other technologies have really made us much more nimble and agile in terms of being able to move quickly, I still think there will be a bit of that catch me if you can.
Sanjog Aul [00:04:50]:
So, Rob, John did say it accurately on where we stand today, but this digital fever is not new. So would you say any difference, any positive news for the people who may have had the same question as, say, 4 or 5 years ago when the digital started that fever started and now that people understand that security hopefully, they understand that security is a very critical component of digital.
Shift left and shift right together 5:19
Rob Hornbuckle [00:05:19]:
I think it is pretty well understood. There’s a lot of people throwing out security first as a statement when they start talking about cloud initiatives, which is really, really easy to say. It’s a little harder to do, but it at least shows that there is that knowledge and that understanding that security is something that needs to be important and needs to be considered. As far as being able to make sure that we’re there for it, getting out in front of it is important, as John was speaking to. I would say also integrating as much as you can to cloud native utilities is more important than you would think it is, and the thing that’s going to really get you there and which has really helped me to completely stay in front of what I need to is the worst buzzword I hate saying in my entire life, but that’s primarily shifting left. I would argue that that’s not really the end goal of it, though. From our perspective, in security, we are shifting left. We are pushing some security responsibilities over to other departments in order to create that velocity that’s necessary to move at the speeds that they want, but at the same time, they also need to be shifting right. So it’s not just a shift left scenario. It’s a shift left and a shift right scenario so you can meet somewhere in the middle. There’s programs I’ve had to institute. There’s trainings I’ve had to do where we bring other parts of the business in, and we train them in different types of security in different ways, security champion programs and things of that nature, in order to institute that shift right piece of it that needs to happen on their side of the fence while we’re simultaneously shifting left to meet them in the middle. That’s what really creates the velocity and the capabilities for velocity that we need. I know at my organization, we had more than 200 releases last year using this kind of methodology.
Sanjog Aul [00:07:14]:
So, John, by the way, Rob, very interesting response because the shift left and shift right is the in thing nowadays, and people are rightfully thinking about it. So coming to that, John, when Rob mentioned about shifting right, he mentioned training. Do you think training does give us the mileage which we all expect by just telling people, hey. You’ve got to keep things secure. Do they behave, the users?
Does security training change behavior 7:38
John McClure [00:07:38]:
I think training is critical. I think training’s come a long way also kind of from where we were in terms of the training being more focused, the training being more applicable. If we just looked out even just a few years ago, you’d see mandatory training, and it was really focused on a few items, whether it’s phishing or data loss or very generic training delivered across the entire organization. The same type of training, delivered over the entire organization. I think you’ve seen that shift, and I think it’s been a critical change, actually. You’re really seeing some significant training opportunities out there being delivered by third parties, for everything from secure coding, to secure data releases, secure pipeline, CICD, etcetera, that I think all of that ultimately continues to create a continual maturation of a security kind of focused organization, and there’s still kind of the more generic end user training. There is some different training that might be given to privileged access users, etcetera. So I think that the training is getting better and that it’s more focused. It’s more engaging. It’s more frequent, I think, to many organizations than it once was, and I think that they’re finding ways to get people more engaged with training, whether it’s mandatory. That’s one way I suppose to get people engaged or through gamification or some other approaches and make it more fun, make it more engaging. Also, I think people realize that doing that kind of work upfront, learning how to do that kind of work upfront, really in the long run, is a huge opportunity to reduce costs later in buggy products and insecure products. So I think the uptake in trainings helped just a ton over the last few years.
Sanjog Aul [00:09:50]:
So, let’s talk about security when you are talking to maybe IT because, invariably, security ends up being in the IT group, but then when you’re trying to exert influence on the business side, maybe you could still say, yes, I have some influence because we are still part of the same company, but here in the digital world, we are very externally focused. We are very partner dependent. We are ecosystem dependent to deliver the capabilities, and those capabilities could you join hands with us? First, you’re gonna look in your backyard and say, is it gonna help me? And or you might have your own priorities, and you might push back. You may not be the most collaborative and, more helping, if you will, in that nature. So how do you achieve that end goal at the digital level, not just at the organizational level? Even though you’ve been paid by that organization, but digital success means across value chain.
The CISO’s job is to inform risk, not remove it 10:57
Rob Hornbuckle [00:10:57]:
It was a little difficult in my current role to answer that because I don’t have that scenario happen at all with my current business model, but, ideally, you would be trying to go towards the same goals, and from the standpoint that you’re referring to, there’s not a lot of motivation to do that. It’s really up to the person who’s asking and requesting to create the motivation for the other side to really want to make that move. That’s the position I find myself in more often. My customer is the public. We sell airline tickets. We move people. We’re like any kind of commercial business you would see out there. It’s just our product happens to be the moving of people instead of an item. To that effect, I push those things onto my service providers on the regular, and you use what’s needed, contract language, discussions, considerations of moving to different vendors in order to create what you need as far as getting the security levels there. Every pressure that you can use to create what’s necessary is what you have to move forward with. Now some of that will come down to the risk appetite of your organization, what you’re willing to accept, and there is cost differences that are associated. You have to get over the fact of as a CISO, it’s not your job to completely secure the organization, and if you think it is, you’re going to be sitting there pulling your head out or pulling your hair out, just terribly stressing yourself out, maybe getting ulcers. I’m not really sure. Not sleeping well, but it’s not your job to fully secure the organization; to think that it is, you’re setting yourself up for failure. It’s your job to make sure that the organization understands the risks that it’s taking on with certain activities and is fully informed of those and fully understands those when it makes the business decisions that it makes. To that effect, it also is helpful to understand business so that you can frame it in a good way for them to understand better, but you really have to handle it that way, and that translates in then to how you extend it to third parties. There’s going to be a cost associated with the levels of risk that you’re willing to accept, and you have to be able to illustrate and orchestrate that for your company so that they make the right decision for what they need to do as a business, which may not be the most secure decision, but it’s the right decision for the business if they’re fully informed and understand when they make that decision, and then you do the best you can to most effectively push that to the partners that you’re working with.
Sanjog Aul [00:13:40]:
So, John, when you look at your organization, so Rob said, you know, he doesn’t have that ecosystem based security assurance, as a need today, and that’s fine, which is, you know, that organization’s business model. What do you see, especially when you are in a business where most things are digitally handled?
Building the right ecosystem of partners 14:02
John McClure [00:14:02]:
I mean, I think a lot of what Rob said resonates. I mean, we talk about this frequently within our group, and I’m the 1st CISO here at Sinclair Broadcast Group. Almost everything we’re doing on the security front is a bit new for this organization, and it’s a large organization, Fortune 500 company here in Maryland, that has an incredible outreach, obviously, to the public and to its perception. We want to make sure that product, whether that’s getting the news out, whether that’s getting sports out, or whatever else we may be broadcasting or some of the other ventures that Sinclair has, we do want to make sure we’re being thoughtful in doing that in a secure way. The ecosystem itself of partners is, I think, always challenging. Depending on where you are, in terms of industry wide, if you are putting people in space, there’s an ecosystem of partners, and even within your own organization that’s very focused on safety and very focused on x or y. So some of the things Rob said really resonated with me because I’ve talked about it a lot here in my early days in that you can’t just buy yourself to perfect security for sure, nor is that your mission. We’re not an information security company. As Rob was pointing out, there are missions to move people safely from one location to another. Our mission specifically is to be able to deliver the news and deliver sports and deliver that over the airwaves or however people might be consuming those, and so creating the right ecosystem is surely critical. It doesn’t mean it’ll always be the most expensive and the most best of breed within that ecosystem, but it’ll be the right ecosystem for that business to be able to operate at the level of maturity that they want to operate at, the speed and revenue targets that they need to be able to target and hit, and so our job, I think, is to make sure we continue to build a strong ecosystem of partners, who are well aligned with our organizational goals, and look at that more of a partnership than just us consuming or delivering product.
Sanjog Aul [00:16:33]:
And, John, I’d like to come back again and talk about, especially when you said you started out and when you come in and you’re trying to lock down the fort for the right reasons, of course, and also even in your ecosystem in any way, you’re trying to exert control on the partners. How are you preventing that act, seen as, someone who is a naysayer and or a hindrance to the growth. How do you eat the cake and have it too?
Sanjog Aul [00:18:13]:
So, John, you came in, started telling people that what’s right, what’s not right, and maybe started putting some regimentation, if you will, within the organization, and if at all there are any ecosystem partners you need to rein in, you would rein in, right, before the right reasons and for what you’ve been tasked to do. How do you prevent that from being seen as dictatorial and or, hey. You’re coming to slow us dying down or you’re just unnecessarily creating stumbling blocks?
From the office of no to the office of know 18:47
John McClure [00:18:47]:
I think that’s a great question, and like you highlighted, and I did a bit in the last response to the earlier question, I’ve been here about 10 months, and I’m their 1st CISO, and you’re right. I knew coming in that there’d be some challenges. I think in a lot of ways, Sinclair has been fantastic in terms of not only recognizing that they needed a CISO, but really getting the support for me and the rest of the team to build that out. I think, and I’m hoping, that this older kind of version of the CISO, if I think back maybe as few as 5 years ago, really was that you were the guy that said no. People would find ways to work around you, and that you really could be a hindrance to whether it’s organizational growth, whether it’s speed of business, you name it. Could it be a hindrance to M&A activities, etcetera? I think that’s changed a lot. I’ve worked on changing that perception a lot. I know some other CISOs that I collaborate with frequently have as well. Instead of we’re the office of no, we talk about being the office of know, and really being able to be a good resource to the business, realizing that we are not here to lock everything down and shut the doors and encase it in cement. At that point, we would be a hindrance, and we wouldn’t be supportive of the business. I talk to my group and the executives here frequently about we need to be an enabler so that they can move as fast as they want to move, but as securely as they need to. I was joking around earlier, before we started the recording that some of these early days for me, it feels like there’s a little bit of shaking hands and kissing babies, and I think that’s the right approach. We gotta create allies across the business. We gotta create trust across the business, and I think with that trust, obviously, people trust that I have the best intentions in mind. We’ve got the best approach in terms of not only securing things, but allowing the company to move quickly. So I think that’s changed quite a bit over the years. It’s something I’ve definitely focused on that we are no longer the office of no. We really are a business enablement opportunity.
Sanjog Aul [00:21:24]:
So, Rob, when you look at, your role or the stance more than the role, the stance that you take as a security leader, is it polite, congenial, but firm? If you had to define, what would that be in this the same way or the way I tried to describe it?
Rob Hornbuckle [00:21:45]:
I think that my description would be more along the lines of, here’s my suggestion, but what are you trying to do? How can I help you accomplish what it is you’re trying to accomplish here? If that goes against what’s happening, okay. What exactly are you trying to do? Let’s see if we can figure out a way to handle this.
Sanjog Aul [00:22:08]:
You’re saying that you’re being inclusive in even the analysis of what they want to get done? Or because the reason is many times people or most of the time, business doesn’t understand security. So they look up to you, but if you come back, they could be like deer in headlights. Then where do you go?
Why the CISO role demands business skills 22:26
Rob Hornbuckle [00:22:26]:
So the answer to there is kind of what John was referring to earlier. It’s having those business relationships established. Once you get to an executive level, and this is true in any role. It doesn’t matter if it’s in finance or operations or IT or security. Once you get to a senior executive level, a good portion of your job is developing the business relationships necessary with the rest of the company and understanding the business of the organization as well as the political environment and landscape for which the business sits in. Once you have that and you’ve proven it out, which, unlike John, I’ve been in my role for 2.5 years now. My 1st year is all shaking hands and kissing babies because you need to meet everyone. You need to gain their trust. You need to have it so that they understand you do both understand the business itself and you understand security, that you’re not there as an opponent, that you’re there as an ally, that you’re there as an enabler, that your goal is the same as theirs, that you’re on the same team. These things have to be understood, and logically understanding them is completely different than feeling it, than knowing it, than having those relationships built with the rest of the executives and the rest of the leadership of the organization that are truly necessary to gain that inclusion and that trust that you have to have in order for your department to operate smoothly, and that’s not unique to security. That is any company or any department within the entire company. Their executive leader needs to do that in order for the company to operate smoothly, in order for their department to operate smoothly. We like to think in security that we’re different, that we’re unique, that we have this role that’s completely different than anywhere else in the company, which to a certain degree is true, but the way that we operate within the company is going to be universal, and you have to accept that fact and accept that at that senior leadership level, there’s skills that you need to learn. There’s skills that you need to have that you would not have natively gained on your way up the ranks through security to get to that level. It’s a different skill set that you have to bring in. This executive role within security, this CISO role is the, well, I mean, you could argue the data one, but it’s basically the youngest senior executive role in an organization. It doesn’t have a huge amount of maturity. It hasn’t been through the ringer nearly as much as a lot of the other roles. Most of the other roles of the organization, they get training in this before they get there. So just as an example, if you were going to go become a CFO, you would join a finance organization. There’s these very distinct paths that you follow to go up the ranks to get to where you’re going. It’s pretty much set in stone how you accomplish that, and along the way, you learn more than those finance skills as you’re going up those rungs. You learn those business skills. You learn those business relationship skills. You learn those business management skills as you get higher and higher up. It’s matured out enough to design and build CFOs in that manner. CISOs don’t have that yet. They will eventually get to the point where that is the case, but the role is just too new for it. So a true understanding that those skills are necessary has to be comprehended and has to be accepted by whoever’s taking that role on, and because we don’t have the maturity, you have to actively go out and learn those skills, learn those abilities, and then pursue using them, and the best way of doing that in the beginning, as John said, is shaking hands and kissing babies as you go around the organization, introducing yourself, and getting to know everyone that’s there and what their roles are and how they function and how they work with the company and how they make the company successful. It just becomes part of your responsibility set, and most of the things that we’re referring to here about getting out in front of stuff, about knowing things ahead, about catch me if you can, all of that ties into this because you have to be that trusted adviser. You have to be trusted to be looking out for the best interest of the business as a whole, not just your specific organization within it.
Sanjog Aul [00:26:52]:
So getting down to the brass tacks, John, when we are actually trying to get things done, one is, of course, when you mentioned about how you get people to buy in, etcetera, but now you want to put the security controls and the programs in place. It’s the speed at which the changes are coming. Not sure if you can be all over and try to boil the ocean. At the same time, if you try to say, I’m gonna try one small bit or a group or an app at a time, then the vulnerability still sits there and nobody will care which project you were focusing on, but if there is an issue, then the all fingers are pointing at you. So you cannot boil the ocean. You can’t eat an elephant 1 bite at a time. So how do you handle security, especially in today’s context where things are coming from all direction at a warp speed with a lot more volume and variety that you would want?
Focusing on the highest risk areas first 27:53
John McClure [00:27:53]:
I think it’s an interesting question and one that, again, especially I’m dealing with here, and I’ve dealt with another organization as well. Very large organizations have very distributed activities, complex activities across different business units. I think the key will always remain that the approach needs to be risk focused. For me, just to do numbers for numbers’ sake, which might look good from a quote, unquote, holistic boiling the ocean kinda technique versus the small bites and you’re never gonna get done your meal kinda problem, is really the approach that has to be made. For you to understand that, there’s obviously a lot of work that goes into really understanding where those risks exist, understanding how those can be addressed, and then tackling those first. Sometimes they’re proverbial low hanging fruit. Sometimes it’s an exceptional amount of work, but the real goal, like, again, we’re saying the same thing, which is great to hear, Rob. I feel like I’m on the right track there. Our jobs as CISOs are to identify the risk, help categorize that risk, and then help echo what that risk is back to the business in the way that the business understands. Me coming to them with this great, quote, unquote, win that the security team might feel is, hey, we just remediated 10,000 vulnerabilities last night doesn’t mean anything to anybody else except the security team. I think really being able to go back to the business and talk about that we’ve reduced our probability of breach by x amount, which could have resulted in x amount of financial loss, is huge. They understand that. They understand why you did it. They’re glad you did it. Something to celebrate for sure. So I think that instead of trying to build this whole organization at once or trying to build a whole function within the organization, whether it’s zero trust, whether it’s identity, you name it, is gonna be tough. Those are gonna be multiyear initiatives that the business won’t necessarily feel or recognize that value back to the business, but if you’re able to really focus and tackle some high risk areas that show clear benefit back to the business, those are gonna be your early wins, and I think the more you start stacking up those early wins, you start gaining more trust. You start being able to take on more mission, and you do start being able to tackle things in a broader scope, but I think if you’re focused on anything different than the high risk areas, if you’re investing significantly more time in lower risk areas than you are in higher risk areas, I think your time is probably being misplaced. That would need to be reevaluated. Instead of looking at the ocean or looking at the small plate, I think we really need to look for those risk points and figure out how we attack those together.
Sanjog Aul [00:31:06]:
So, Rob, when you look at the same question, given your environment where you’re trying to get things going, given you’re part of a rather, you said, right, it’s an airline and people’s life could be at stake and risks could come from anywhere. Can you really slow down on seeing okay. Suppose you find 5 places where you have risks. Can you say, okay. I’m gonna deal with the first because your downstream effect can be huge and devastating?
Rob Hornbuckle [00:31:42]:
Like, wow. You really set me up there with, like, people’s lives are on the line. It all comes down to a happy medium between what your business model is and what your organizational risk appetite is, and what would be called a crown jewels assessment of your organization. Generally, you’re dividing your organization up in the areas of protection between your high protections, your medium protections, and your low protections, and in our case, things that would cause a misnavigation of the plane would be on a high protection. Things that would cause a loss of our ability to dock payroll for 2 hours might not be as high of protection. It just comes down to what is important from the company from a risk standpoint, and then you find that happy medium of the stuff that needs to be addressed first, the stuff that needs to be addressed after that, and you have to take the elephant 1 bite at a time. There’s no way to boil the ocean unless you end up in a scenario where they’re just gonna throw a whole bunch of tons of money at you, but normally something bad’s happened before that scenario plays out.
Sanjog Aul [00:32:58]:
In all of those things that you mentioned, I’d like to connect it back to saying embedding security in technology capabilities. Until you don’t do it holistically, you would not know that the attack could come from any place where you haven’t. So I know it’s not an easy question, but still someone who is leaving it to you and say, hey. That’s a black box. Go deal with it. What are you recommending we do as security leaders?
Rob Hornbuckle [00:33:30]:
Well, first, you have to have a really good understanding of your environment. If you have a good understanding of your environment, then you don’t run into many of those problems that you’re referring to. The other thing that I do personally is I have a red team on staff that then tries to poke holes in that theory the entire time. It’s not perfect. There’s no way to make it perfect. We don’t work in an industry of perfection. We can’t, given the nature of what we have, but it buys me a lot more ability to find things that we may not have seen or find more of those unknown unknowns that could be out there. Once we have those two together with a full understanding of our environment, a full understanding of our business model, and the ability to try to poke holes in what we have, it gives you a pretty confident understanding of what you’re dealing with, and then from there, just compare it to the pieces I referred to earlier about where the business wants to go and where the business wants to put things, and you can be fairly confident in what you’re looking at. I would never say you’re 100% confident. Anybody in this industry that says they’re 100% confident is, well, for lack of a better term, full of it. They don’t know what they’re talking about. I did some work with the US government and black sites and things that were more secure than any business would ever operate in existence, and we still never assumed that it was 100% secure.
Sanjog Aul [00:35:01]:
And, John, when we come back, let’s talk about the reporting relationship. It can be a sensitive issue because many cases when security reports to IT, it is a blessing and or it can be a curse given how you’re perceived, and at the same time, a lot of people evangelize that it’s essentially a risk management role. So it should sit at the top level, but then people don’t understand the Greek and Latin security people speak. So where should it sit given the world that we are entering into are already the world we are weaving around us? Should it be a business or an IT role?
Sanjog Aul [00:36:50]:
John, reporting relationship for security leadership and or the security as a group. What would that organization look like top down and where security should sit for it to be most effective?
Where security should report 37:12
John McClure [00:37:12]:
I think it’s a great question. I think it’s also changing in terms of where you see a CISO sitting within an organization. I think the last numbers I saw still had them very frequently continuing to report into the CIO, so into the IT organization. I’ve talked to a couple of other CISOs. Some of them reported into a chief risk officer. Some of them report into a CFO. It’s very interesting how it’s been changing. It is changing, the importance of the role. I talked, at another engagement recently, and we’re talking quite a bit about this, that CSOs are more often being asked to sit at the table when a board meets. You’re seeing real regulation come out around there. The recent proposed SEC rules in terms of really increasing the visibility of cyber, the risk of cyber, making sure that cyber is being well considered, that there’s somebody, actually on the board who understands cyber. So I think, as organizations continue to realize the importance of doing business in a way that is thoughtful and responsible, especially, in the case of the SEC, obviously, to their shareholders, as well as their customers, it has really gained a lot of focus and importance. In terms of where they should report, I think, ultimately, it will not be within IT. I think that you’ll still see that for a long period of time. I think it’ll take some time for that to shift, and it’d be a higher business function that probably is on par and peer with the CIO’s organization. When you live within the IT organization, it’s a little tough. In some ways it’s great. You got IT right next to you. You know what they’re doing. They know what you’re doing. Hopefully that helps with some alignment, but IT spans the organization in a very different way than a legal function might or an HR function might or a security function might. So I think that’s slowly being recognized. I think it does need to change over time. Operating within the IT construct has not been, at least it hasn’t been for me, a hindrance. I’ve had fantastic support over my career from the folks that I’ve been able to support, but I think that as long as it stays embedded there, it’s hard for other parts of the business to really clearly see that it is a growing area of importance that needs additional voice and that it needs a different access and needs different consideration within their organization.
Sanjog Aul [00:40:15]:
So, Rob, I have heard from enough IT leaders over time that for them to be effective or their organization, that IT department to be effective, they are taking their staff and embedding them in business. There could be a dotted relationship or a hard line between IT and them and also a dotted line or a hard line with the business unit. When we are saying security or calling security as a risk management, effort, shouldn’t that be the case with security as well?
Rob Hornbuckle [00:40:52]:
Not a 100% certain I followed that question, but
Sanjog Aul [00:40:56]:
Let me rephrase it so that you can respond. So should you embed security personnel like you do with IT in a given business unit so they very well deeply understand business and then focus on making sure that they take care of that business unit or that business function and dedicate to securing that versus sitting in a central command and control type of an outfit.
Rob Hornbuckle [00:41:23]:
So the short answer is yes, but the long answer is it’s significantly more complicated, especially with my organization. I have 3 distinct areas of my organization. I have a risk and compliance side, which is embedded across everything everywhere. They have to be to function, and they handle a lot of our auditing, a lot of our early warning, and they feed into the other areas within my organization. I also then have a security analytics side, which is mostly heads down. They’re mostly tool management. They don’t have a huge need to embed themselves into the business because it’s not part of their job function. They have a need to understand the business so they know what they’re looking at, and it’s important to make sure that they’re kept up to date and they have a good understanding of our business model and how things function, but they don’t necessarily need an embedding. In fact, embedding them in the business might actually be detrimental to them getting their jobs done, and then I have a security engineering side, which I do have embedded across the business as well. So the answer comes down to it really depends on what function within my org that you’re filling on where and when and if it’s beneficial that you get embedded into the business. A lot of that has to do with how often you directly work with them and how much teamwork is necessary between you and them within my org structure.
Sanjog Aul [00:42:52]:
Now let’s talk about, solution providers. So, John, when you are dealing with especially when you’re coming to this new organization, yes, you might have had some old relationships, some trusted partners who may have helped you with the security management in terms of other tools, products, and or services, but are they stepping up and showing that, yes, they understand and are willing to go to extra mile to help you get ready with this newer crazier world of, multiple things happening in cloud and or in digital space? Where do you rate them?
John McClure [00:43:32]:
I think they really have. Over the years, there’s folks in companies that I’ve worked with across industries. I used to support the intelligence community for decades, and then I was within education, and now I’m within this media and entertainment industry. Across all of them, I think there are some fantastic solution providers and some other ones that weren’t able really to deliver at the way I needed them to. I think that over the years, I’ve really been able to build some strong relationships and some folks that have really been invested in understanding what we wanted to do, how we operated as a company to really help us mitigate risks. There’s so many things sprouting up very very quickly in terms of solution providers out there. Some very niche players, especially, you’re seeing a ton of them right now, whether it’s on the attack surface area or whether it continues to be within multi cloud, and it’s super exciting to see some of these new folks pop up and having some good partners and helping you assess that and helping you kinda realize the right folks to navigate to and forward or perhaps away from has been fantastic. Some of these solution providers or partners that we’ve had out there, they’ve really been a bit of a force multiplier for us. Instead of me hiring a bunch of folks to go do a bunch of big calls or technology evaluations or understanding more about other organizations out there and how they can help us mitigate risk, our partners have been super critical in helping guide us and really feeling like partners and not just somebody trying to sell us something. That’s who we’ve stuck with, and I think it’s been really critical to our success.
Sanjog Aul [00:45:35]:
Rob, any suggestions for the technology solution providers in this context as you go about your interesting journey of embedding security into technology capabilities? Where can they, you know, improve their game, if you will?
Treating solution providers like your team 45:52
Rob Hornbuckle [00:45:52]:
Well, it’s always nice if they improve their game, but ultimately, it’s more your responsibility to ensure that their game is improved. The way I’ve always handled it is when you’re using a technology solutions provider, unless they’re some scenario where they’ve given you this one product and you take it and you leave and you don’t really have any interaction with them anymore, if they’re doing some kind of a service with you, you have to treat them like they’re just another employee at your organization, and I don’t mean that in a derogatory manner. I mean that you need to be invested in them. You need to find out about them. You need to understand them. You need to have a point of contact, and you need to know on a personal and business relationship type level who that person is and how they work and what they do and how they operate in order to fully integrate them as if they are simply a member of your team. Performing that function alone will step up the game of service and solution providers that you have on staff more than even if they were to make changes themselves.
Sanjog Aul [00:46:57]:
One last question, and I need response from both of you, which is about the leadership chops. You and other aspiring or current CISOs have to build so that on one hand, they are able to better handle what’s oncoming in terms of the crazy volume and variety of challenges and initiatives that their respective businesses are trying to undertake, and secondly, to embed security in their technology capabilities, which are changing, which is almost like flying the plane while building it. Start with you, Rob.
Rob Hornbuckle [00:47:36]:
Be adaptive. You need to understand where to use a term that several of the integrators I’ve worked with have used before. You need to come to a good understanding of where your 1 way doors are and where your 2 way doors are. You need to have a good understanding of what your timelines and your deadlines and your business objectives are. When you do that, you can come up with multiple maturity iteration plans in order to build the plane while it’s flying, as you said. You have your minimum, what you need to get things done, to get in with the timelines to meet the business objectives, and then the 2 way door aspect is anywhere where you need to make changes, you’re making sure that you’re putting in the hooks and you’re putting in the things necessary that it’s easy to do those changes going forward, and then you start maturing and you’re moving from there. It ultimately really comes down to what your business model is, what your business goals are, and what your business objectives are, and what you can do to help meet those objectives, and then illustrating the risks associated with meeting those so that a business decision can be made on moving them forward. If you don’t do all of that correctly, then the plane will fall apart as you’re flying, and that’s where it starts to get complicated, and that’s where the skill of not just a good CISO, but good directors and good managers comes into play so that you can keep the team all on board and all knowing what’s happening as it’s moving forward.
Sanjog Aul [00:49:08]:
John?
Leadership skills for the modern CISO 49:09
John McClure [00:49:09]:
That was a lot embedded in this question. A few things come to mind. You just talked about what changes might be warranted within an organization. Again, I think it’s changing the mindset, continuing to highlight the importance of security as appropriate within your organization and with your industry is key. I think that the news is helping us a lot with that right now with what’s going around in the world. Cyber is surely on the front page frequently enough to continue to gain some view and some people picking up on the importance of it. The leadership style, I think, is an interesting question. In the past, it was a very different leadership style and the whole function of the CISO was significantly different. The guy that would jump up and down and pound on the desk and say no and really tried to take a hard line on a lot of activities really did a bit of disservice to the CISO position. I think that’s changing quickly. The CISO role is growing in importance. That means the leadership style has to change. You can no longer run around with the hammer lighting everything on fire. I think you really need to be focused on building these incredibly important leadership skills, continuing to develop that. There’s a lot of things right now that talk about CISO burnout and somewhat Rob highlighted that before as well. Two articles I just read recently about this nebulous, not well defined career paths. A lot of us come up through tech, and then all of a sudden we’re expected to have this executive presence in the boardroom, and I think that’s tough. I think that needs to continue to be developed, and that leadership style will continue to evolve. As that evolves, I think it makes you exceptionally more effective in making sure that security is embedded into these technologies, is embedded into these organizations, and then ultimately it’s a win for everybody. Everybody begins to realize that you’re a business partner. You’re an executive within the business. You’re just not that security guy who keeps saying do your training. As all of that continues to evolve, the mindset of the business, the leadership style, and ensuring that we’re continuing to communicate the effectiveness and the role that the security team and the CISO is bringing to the organization is ultimately what’s gonna make it all effective.
Sanjog Aul [00:51:58]:
Once again, thank you so much again, John and Rob, for sharing your insights about how organizations and the security leaders combined can join hands and truly embed security in their technology capabilities. Thank you.


