Hetz Presents: 'From Laying Bricks to Cyber Security' with Rapid7's Ian Amit
"If you're not challenging yourself, if you're not creating disruption in the market, you're not gonna be a successful business."
Hetz Presents: Ian Amit, the Advisory CSO at Rapid7, on understanding the true meaning of zero trust, breaking down the requirements and capabilities of an IT stack, and aligning products with needs.
Watch or read our Q&A with Ian for more:
What did your first job teach you?
First job; I'll start with a non-cyber one, because I think it is important. I was a bricklayer. I was doing construction in a building. I was trying to make some money as a kid. To get some money, to get something accomplished, you do need to put in the sweat, whether it's physical or mental. My first cyber job, however, which is probably a little more relevant, was actually in consulting. It was at a time where I somehow realized that what I've been doing for fun, and what I would've been doing anyway as a hobby, is something that actually is a job, a legit job that people will pay me good money for. I've learned that, again, if you're not loving what you're doing, there's no way you can be great at it, or at least progress at it. And I'm still learning. I've been fortunate to keep learning with every new role that I have. So that first job in consulting, kind of focusing on Linux and Unix security, grew to a 25+ year career in cybersecurity.
What’s your approach to building a unified zero trust solution?
My approach to zero trust has been, rather than trying to find a one solution to tick them all off or finding a 'zero trust in a box', was really to get to the true meaning of zero trust. Think about what zero-trust architecture means, and go back to the drawing board and do some homework. And for my organization, having a clear definition of what we expect and what I need as the Chief Security Officer from the zero-trust architecture in my organization. So it was really breaking down to the basics of what we expect in each and every area of the IT stack and of our operational technology model from a zero-trust architecture. We essentially distilled it to a list of requirements and capabilities, and then started shopping around for products and services and architectures that would fit the maximum number of requirements that we've had. There wasn’t at the time, and honestly, I don't think there is now, any one solution that you can take off the shelf and it would just hit all those requirements. So we ended up, again, playing around with the idea of sort of a zero-trust architecture 'Tetris', trying to find the minimal number of pieces that would cover the most requirements that we've had. I think that we can prioritize some of those requirements, based on what we deem more risky, or more focused, for our security program, and find the best combination of different products that would address and provide us the capabilities to achieve a zero trust architecture. So, again, that was our approach. That was my approach back at the time. I think it actually still fits to this day, and we're talking about four years ago. So, as much as zero-trust products have advanced, and you've got a lot more offerings these days, I do support adopting that approach of identifying what it truly means to you in your specific organization, your specific needs, breaking that down, and then evaluating the different solutions to find what's the best fit. I do think that's still a relevant approach for modern organizations, and will be in the future.
How should CSOs handle the M&A challenge of integrating new tech stacks?
Approaching mergers and acquisitions as a CSO, as part of an executive team, is super fun and challenging, because it is part of the company's growth strategy. And as a security function, as the risk function in the company, you are tasked with making sure that strategy can be executed, which means you're there as a support function, you're there to identify any upcoming risks, you're there to make sure that whatever actions the company is taking are fairly supported and you can provide coverage, a security blanket or whatever you want to call it, or safety net, to those operations. I think there's two main challenges to performing a successful M&A. The first one is, obviously, due diligence. It's sort of a funny dance that the two companies make, where they try to figure out what's under the covers, so to speak, of one another. From a security perspective, obviously, you're tasked with understanding, at the end of the day, what the risk that we're gonna assume by acquiring a certain company is. Because at the end of the day, you are taking on any legal responsibilities for any risks that they bring with them, any prior or existing compromises, any increase in attack surface, any regulatory scrutiny that they bring with them, and that's all part of that due diligence process. You're trying to uncover as much as possible. And again, you want to inform the rest of the executive team that's involved in that M&A and have an impact over the process. This can manifest itself in legal means, in legal changes to the agreement that is being struck. It can manifest itself in further negotiations around price. And, again, your role there is really to inform and to support that process. And then comes the flip side, which is, "Alright, we're executing, or we're committed to the acquisition." At that point, the challenge becomes a little different, because now they're one of us. So there's, first of all, a cultural gap that needs to be bridged. That concept of us-and-them needs to go away. So, whereas a typical CISO would focus on security culture within the company, now you have to adapt and understand that there's a security culture that needs to be extended. Maybe the company that we've acquired already has something in terms of culture and processes. So the question then becomes, how do we take advantage of that? How do we modify it as needed to make sure that we're providing something a little more holistic? And, obviously, there's the technical terms. As I mentioned before, what is the technical debt? What is the security debt or risk that we've acquired, and how do we address it as quickly as possible and as seamlessly as possible? I think that for me, typically, the process has been we're gonna create kind of a phased transition. At the beginning of it, the company still operates pretty much by itself. It's pretty much segmented away from the acquiring company. And as we manage to bring on more visibility and monitoring and control capabilities, and apply them to the company that we've acquired, we can kind of open up the floodgates and allow for more interactions. Again, as a support function, as a security and risk function, what we're there to do is make sure that that happens as quickly as possible, so that the business can start taking advantage of that acquisition and can start reaping the fruits of the acquisition. So we're not saying, "No, you can't do all the marketing and fun stuff, and expand the products and execution, because we're still dealing with security." Our job is typically to fast-track that, or put that towards the beginning of the process as quickly as possible. Sometimes I would actually bias towards, "Let's get visibility first." You know, if we can see stuff, we can at least respond to it. So the controls might not be perfect on day 1 or day 10, but at least we can see stuff and give the rest of the business the go-ahead to execute on their integration plans, and we'll make sure that we are at least having the right level of visibility to identify things as they're developing, stop them if we need to, but still really allow the business to execute and reap the benefits of that acquisition as soon as possible.
What’s most interesting about your advisory CSO role at a cyber company?
Taking on an advisory CSO role with a cybersecurity company is interesting to me because it allows me to not just work on the security of one company, of Rapid7, and help understand the risks and the attack surfaces and the roadmap and the strategy, but also work on what the company is offering, as far as a product and the roadmap. The Advisory CSO mostly works with the top strategic customers, and is there to provide a slightly more independent perspective, a service to those companies to strengthen their security programs. Coming from someone who's done it before a couple of times themselves, they really tap into the target market, the target audience of Rapid7, of whatever security company you're working with, and identify recurring patterns with those strategic customers. That's something that typically a salesperson or a field CISO is challenged to do, from an objective perspective. And again, that's why I think that that role is interesting, because I'm actually independent from Rapid7, and Rapid7 hires me to go to customers and work with them, and then bring back that understanding of what we need to do, how we need to change the platform, the offering. You know, what should we prioritize? What areas do we need to get into that we're not covering right now from the big spectrum of security practices and security programs? Rapid7 covers quite a bit of it, but, again, no one can offer the full gamut, and everyone needs to make sure that they're focusing on the areas that they're gonna execute on best. So that's basically that role. Again, it's kind of switching gears a little bit from a traditional CSO role that focuses on executing on one security program to someone who's in-between and running between many different security programs and garnering an understanding of what the market segment needs and how I help one company to expand and execute on its product roadmap.
How can CSOs be business-progressive while executing their security function?
The role of a Chief Security Officer is really not to lock things down, and I think I alluded to that in a couple of my previous answers. The role is really to allow the business to move as fast as possible, as wide as possible, and at the end of the day, from my perspective, to take as many risks as they want. Because if you're not taking risks, if you're not challenging yourself, if you're not creating disruption in the market, you're not gonna be a successful business. The safest thing to do is just not to do anything. That's not what we're there for. We're there to challenge the executive team and tell them, "Go further, go harder, ask for more." Challenge me to provide you with that safety net that I mentioned before. Challenge me to expand the guardrails to allow you to drive faster, to cut corners, to go faster, to break faster where needed, that's really what we're there to do. So I would focus less on the tools and capabilities and controls that will make you feel better and safer, because you know what their limitations are, and you're kind of narrowing the guardrails, you're making sure that everyone follows that one lane. That's not fun. And that's probably not business-savvy. You wanna run 10 lanes. You wanna have minimal margins at the corners. You wanna have wide corners that you can cut through, rather than having to stop, turn, go again, and all those kinds of stop-and-gos that are really affecting the business. I would challenge any CSO, or CISO, to sit down with their management and ask them simple business questions. "What is it you're trying to achieve? What are the risks that you're seeing? Where is the competition? What are our goals?" And try to take those as the guiding principles to, "Alright, I need to make sure that that happens. And I need to make sure that if they wanna go a little further, they can." And really challenge the executive team back and tell them, "Why aren't you trying to go further? Why aren't you trying to attack or address additional markets?" We can do that. We can allow you to do more aggressive research, to be more aggressive with the market competition. Just ask us and we'll find a way. That's our job.
What is the most painful mistake a CSO can make?
Most painful mistake you can make is probably saying no. That's a no-go for me. And I just said no. Every no is essentially a stop to the business, and forces someone to find other solutions around the problem. You're there to solve those problems. You're there to say, "Well, we can do that, but we'll need to..." You know, "We'll need to enhance monitoring." "We'll need to put some encryption around it." "We'll need to do some more due diligence on this supplier that you want to use or product that you want to use." Or, "We'll need to figure out a safe environment for you to use it, because it's kind of flaky and it's dangerous," or whatever it is. So the answer is the worst thing you can say is just no. You need to be the partner that comes in and comes up with those crazy solutions. And you know what? Sometimes you need to negotiate around. "If you wanna do this, it's gonna cost you.", “It's gonna cost you either with time, with money, with people, whatever it is.”, “But if you wanna do it, I'm not saying no.” I'm just saying that you have to think about the full picture. And at that point, once you figure out that cost, it makes it really easy to think, "Alright, what's the benefit for the business?" You know, what is the potential upside of that activity now that you fully understand what it costs to execute on it? And at that point, it's an easy management decision. If it's less than the upside, go at it. I'll work with you, I'll haggle with you, I'll make sure that the price is kept at that point so that you can actually execute and bring money to the business. If it costs more to execute on something than the yield it's gonna bring back, I think we need to reevaluate this decision.
What’s on your cybersecurity solution wishlist?
What's the cybersecurity startup product or solution that I would love to see? I'm not sure you can pay me enough to say that here. Seriously, though, I've been working on this concept of what I call elastic permission, which is essentially an encapsulation of my personal approach to security. It basically says, "Go ahead, do things," you know, "be creative, be disruptive. I will find a system that will allow you to still operate in it, but keep you safe." So, when you're not doing risky things, when you're not creating friction I wanna make sure that your permissions are shrunk down to the minimal set possible, and really reduce that attack surface that you're leaving behind, if you're demanding to do so many different things at the same time. Because no one really does everything at the same time. So it's that concept of having a lot of different permissions so I could be creative and execute on things. It works, but at a single point of time you're only exercising a small portion of your permissions. So having something elastic, that kind of morphs with the way that you operate, and really protects everything else, everything that you don't need to expose, reduces the friction from the user, so that the user can actually go about doing their creative things, and marketing and sales, and whatever it is. That's something that I think is really ready for disruption. It's kind of an extension of that zero trust concept of allowing people to do a certain action in a certain time, based on the environmental conditions and on what they're trying to do. It's really expanding that in a continuum across different assets, across different people, for the entire company. Another area is probably more holistic. I hate calling it XDR, but detection and response, classic SIM, or MDR, or whatnot. Tons of potential for automation there. The old school SIM, SOAR, SOC, it doesn't really work. I mean, it's very, very expensive, and it's all based on things that everyone's been doing for over 20 years. So we need to take all that knowledge, like communal industry knowledge, and pack it in a magical UIML super-cyber box, and start delivering on it a little more effectively.
How should the CSO role evolve over the next few years?
Well, I personally think that the CSO, or CISO, role continues to change, has been changing over the past few years, and will continue to change towards a full executive role. I've been fortunate to have a seat at the table as an executive member, to have board reporting capabilities, to really engage with the rest of the executive team. Taking on more risk functions is also in the cards for a CSO or a CISO, either by partnering more closely with the CFO, with a COO, with a CRO in certain organizations. But definitely, I'm taking from my own experience, being part of an enterprise risk management committee. I believe, for a CISO to fully realize the capability of being an executive in that position, they need the opportunity to cover both technology as well as operations, a little bit of finance, a little bit of risk, and really use that as a key function as part of the executive team to make sure that companies are being successful, are being aggressive in a thoughtful and calculated manner. And that's what a lot of companies are kind of struggling with these days, and you can see that. A lot of boards are looking for a board member with cybersecurity expertise, because they're lacking that ability to guide the company and tell it, "Look, you can go further," or, "You need to step back." "You need to think about risks, or governance, or compliance of different things." So that's where I'm seeing the role keep evolving towards, and hopefully a little faster.
What do you do for fun?
So I do a lot of things for fun. I mean, security is fun by itself. But for fun, I do many things, from playing with my kids to gaming on my computer. I've recently taken up flying as a hobby, especially during COVID days, where we've had a little bit of a flight restriction. I was like, "No one's gonna ground me." So I picked that up, and that's a fun new hobby that kind of put me in the learner seat again. As someone who's been doing one thing, or an array of things in a certain field for a long time, getting back to square one and experiencing that learning curve again, is super-fun. So that's definitely a new hobby that I'm focusing on right now.
𝐇𝐞𝐭𝐳 𝐏𝐫𝐞𝐬𝐞𝐧𝐭𝐬: is a series featuring tech leaders and execs from around the world, exploring how they arrived at their professional milestones, how they approach management and leadership, and what comes next in their industries. Watch the full series on Hetz Ventures' Youtube channel.


.jpg)