Smart Security Investments Start with a Strong Foundation
As cyber threats continue to increase and technologies like AI introduce new challenges, organizations are increasingly looking to strengthen their security defenses. While that often means investing in new solutions, maintaining strong security foundations remains critical. New technology must complement those foundations and never replace them.
I recently spoke with Matt Cerny, Director of Cybersecurity, about how organizations can make smarter security investments. Our discussion covered evaluating existing security stacks, maximizing the value of technology already in place, identifying gaps that warrant new solutions, and recognizing when it's time to cut your losses on a technology that isn't delivering the expected results.
Q1. With the number of security technologies available today, how are you approaching evaluating your existing stack to determine what's working, what's underutilized, and where you may have gaps?
I think you're going to end up with three grounding principles, at least from my perspective. I'm a firm believer that strong security fundamentals come first. When it comes to the technology stack, it's about measuring the outcomes of the technology you 're utilizing. And then lastly, holding the strategic vendors accountable as partners. You'll see those three themes resonate throughout the conversation as we continue here.
Q2. You mentioned measuring outcomes. How are you going through that process?
I always tell the teams, if you can't measure it, nobody can prove that it happened. You have to have some measurable outcome when dealing with something, whether that's reducing noise, showing a decrease in threats, or demonstrating an increase in productivity. There's always got to be some measurable outcome that we're ultimately tracking, so we can demonstrate the return on investment we're getting from this particular technology.
Q3. How often do you think organizations should be conducting comprehensive reviews of their security stack, and is it an ongoing process, or are there specific triggers that warrant maybe a deeper evaluation?
I think there's both. I believe you should be measuring things differently depending on what you're evaluating. I have been able to measure to the point that we understand certain cycles are cyclical. For example, right now, we do have evidence to prove this is our busiest attack season. We've gathered enough metrics to say that between October and January, we're going to see an increase in threats across the board. We're going to see it dive down toward the end of January, and then we're going to see it peak back up in March and April.
As for regular metrics reviews, maybe conducting them on a monthly basis so you can understand where the trends are. But you also need to do deeper annual reviews to ask yourself: "Are we getting the most out of our investment? Is the technology doing what it's supposed to be doing? Is the trending showing that we're moving in the right direction? Is it moving up or down appropriately?
Q4. We hear about companies that have more security tools than they can effectively manage. How do you identify redundancies or overlapping capabilities, and how do you determine whether consolidation makes sense in those circumstances?
I think it comes down to capabilities rather than product names, and understanding the measurable risk associated with them. It goes back to having strong cyber security foundations, which can't be overlooked. Those foundations don't necessarily mean implementing a particular name-brand technology. Instead, the technology should complement the security foundations already in place. Sometimes, gaps in those foundations can expose weaknesses in specific areas. I personally believe you can't get away from having strong security foundations. You need to build on that foundation with technology that complements and strengthens it.
Q5. With threats continuing to evolve, particularly with the emergence of AI, how do you determine whether your existing technologies can address these new risks, or whether a new investment is necessary?
Again, you've got to look at all your existing capabilities and what you have in place. I don't necessarily believe that because there are new threats or emerging technologies out there, we have to grab a new piece of technology from a particular vendor. Let's understand what risks are really being identified, or what threats are being identified. What existing capabilities do we already have, where's the gap, and can we layer on a piece of technology to address it?
AI might introduce new threats, but some of those foundational controls remain critical. Identity, governance, least privilege, strong authentication, and data security are all important elements. If you don't have those in place, AI might ultimately expose areas where more work is needed. That's where I go back to the question of what gap you're ultimately trying to solve for. Do you address it by strengthening your foundational security controls, or do you look at emerging technologies that can solve that gap?
Q6. AI is also being incorporated into nearly every security product today. How do you distinguish between capabilities that deliver meaningful improvements and those that are largely marketing hype?
I think this one is a tough one. We talked about gaps a moment ago. What is the gap that you've identified? What are the needs? If you're incorporating AI into it, and I'm speaking strategically around the cybersecurity front, is it improving detection quality? Is it reducing some of those false positives?
Investigation time becomes important. We talk a lot about all these AI capabilities being able to identify issues and help you with that investigation time, but is that real in terms of the time you're spending? Is it a true positive in terms of what it was able to reduce, such as the amount of legwork required to identify where the problem is? Can it automate a repetitive task, as well as increase response time?
Q7. There's a lot of hype surrounding newer security vendors and what their technologies can deliver. How do you evaluate those claims during a proof of concept (POC), and how much weight do you place on what a vendor promises versus what the technology can deliver in your environment?
I think that's a great question because we have a lot of vendors in a lot of different spaces, and not every company is solving the exact same problem or gap. It's about understanding what the business case is when you speak to these partners. I'm trying to solve X, Y, and Z. I understand they may have sold this particular product to other companies, but those companies may have been trying to solve a different problem or be a different maturity level.
When you have that conversation with them, you need to be upfront. "We're really trying to solve this. These are our particular challenges." And then, to your point, during the proof of value or proof of concept, can you produce the metrics that show you're reducing those various levels of risk or addressing the gap we identified?
I'll be honest with you, I've seen some technology partners do it extremely well, to the point where the qualification becomes, "Look, you've done what you needed to do. We need to capture this piece of technology." But we've come up against others where it's clear they're just not meeting what we're ultimately trying to achieve, and therefore we're going to go with a different vendor.
Q8. When a new threat or technology emerges, there's often pressure to respond quickly. How do you balance that urgency to adopt something new against the need to properly evaluate whether it's the right solution?
That's another great question. I think at times we're very quick to react, similar to what happened with cloud and even mobility. We're seeing it again with AI.
Again, you've got to look back at your foundational aspects: What are we doing from a foundational perspective? Is there truly a new risk that's being addressed here, or is it just a gap that we didn't address effectively at the foundational level, and then we can reassess? Is that really an emerging risk for us? You have to really look at it from that lens.
But I do think sometimes, as technology individuals, we become reactive and don't go back to the fundamentals to identify where the gaps are. We need to ask ourselves whether there's a larger risk we can address by strengthening those fundamentals, or whether we really need a newer piece of technology to address it.
Q9. It's not uncommon for organizations to discover they're using only a fraction of the capabilities available within their existing technologies. How do you assess whether you're truly maximizing the tools that you've already spent the money on?
I've seen this a lot throughout my career. We all are inundated with work, whether that's the work that we have, new technology or the demands of family and work-life balance. We have all these different things that are competing priorities as well.
So finding underutilized technology is not something new, but I do think as leaders we need to approach this in our QBRs and have these conversations with our partners.
"We acquired this piece of technology, and it's doing what it was supposed to be doing, but what else are we ultimately missing from this particular technology stack? Are you guys seeing us utilizing it to its fullest capabilities, or are there other things out there?"
Those conversations with your vendors should probably happen at least quarterly to determine the value of the particular product, review the metrics that demonstrate its effectiveness, and understand where you're not fully utilizing the technology or where you could be getting more value from it. It's about bringing those opportunities to the forefront and having that dialogue with your vendors.
Q10. When you identify several areas that can benefit from an additional investment, how do you prioritize what gets funded and what can wait?
You have to look at the severity of the risk, the probability and impact, regulatory and contractual requirements, potential exposure to the business and its resiliency, the cost of reducing that risk, and then the operational benefits.
Sometimes, acquiring a $500,000 piece of technology, adding another $500,000 in resources, and then factoring in additional costs for infrastructure and capabilities just doesn't pan out in the long run. It's about understanding what's giving us the best return on investment and ultimately being able to implement that technology where applicable and where needed.
Q11. How do you build the business case for new security investment, particularly when the value is often measured by incidents that never happen? How do you factor ongoing operational costs beyond that initial purchase into making the case for the funds?
I think you have to look at improvements in your security coverage, what can reduce friction in the business, and the increase in the security maturity of your particular program.
At the same time, I don't believe technology is a replacement for strong foundational controls. I don't think you can buy your way into having a mature, secure organization. I think you have to balance that with understanding what exposures we ultimately have, what we can do from a foundational perspective, and then what we can layer on top of that. And then be able to show that particular value, whether it's meeting specific requirements, eliminating licensing or infrastructure costs, or increasing productivity as a result of those changes.
Q12. When you've invested in a technology, implemented it, and then six months to a year later realize it's not delivering what you expected, how are you determining whether to invest more time into making it work or cut your losses and move on?
I think this is where it comes back to defining your success metrics up front. What are you trying to solve versus what is the security community or multiple business units trying to solve for? Because at the end of the day, the maturity of your program is different from the folks down the street from you.
Having those success metrics upfront is important, but when the technology isn't delivering, you ultimately have to determine why. Was the implementation poor? Were we missing integrations? Did we have staffing limitations, insufficient training, or even vendor support issues? What is the particular reason?
I think you've got to have these conversations during your quarterly business reviews. That's part of the importance of having regular business meetings with your vendors. You need to be able to go back to them and say, "We set out to solve for this, this, and this, and it's just not working. "Then give them the opportunity to explain why they think that's happening. Is it a staffing issue? Do we need to train our individuals? Is there an integration issue going on?
You have to try to give each other the benefit of the doubt, explain the particular problem, and see if you can make adjustments to achieve a better implementation.
But if it continues not to deliver, I think cutting your losses is something you're going to have todo. You're going to have to explain that it wasn't achieving what you ultimately set out to do and determine that it's time to cut your losses and move on. I don't think individuals should be afraid of that.
If your program is mature and well-balanced enough to add a particular security tool, removing or replacing that tool shouldn't be that difficult, provided you have everybody on board and there's a shared understanding. But building that relationship with your vendor, where you can have those direct conversations through quarterly business reviews, is super important.
Q13. What lessons have you learned about evaluating vendors up front to minimize the risk of making the wrong investment? Are there red flags or questions that you now consider essential before committing to a solution?
I think before committing to a solution, you've got to talk to other people who have implemented it. I just don't think there's a way to get around that. I think having that dialogue with another partner is important.
They might explain, "Great product, but it took us nine months to integrate." And you think, okay, I wasn't expecting that. In our evaluation, we also found it was going to be a good product, but don't think we anticipated a nine-month implementation.
Now I can take that information back and say, "Look, how do we make this go faster? What were some of the missing elements that contributed to that?" So getting that information is important.
Support is another big one when you're doing a vendor evaluation. How good was the support you received when you ran into a problem? Were you able to get the support you needed in a timely manner? Were they escalating issues through the proper channels when you needed help?
I think a big aspect of it is talking to other people who have adopted that technology, understanding how they progressed through their implementation, and then how they managed ongoing support after it was implemented.
Q14. If you were advising another security leader who's preparing to evaluate their security stack and plan investments for the coming year, are there two or three things that you might encourage them to focus on first?
Truthfully, I think it comes back to what we talked about a little bit at the beginning. Look at your foundational security controls and have conversations with other customers and cyber security leaders to understand how their implementations went.
I still think you have to go back to the strong security fundamentals of your existing program and identify where you have potential gaps. Then you look at the technology. The technology should augment or complement your existing security foundations by addressing the risks or gaps you've identified.
And then ultimately, you've got to continuously measure what's going on. I do think there comes appoint where those measurements become a little more linear. You're not seeing as much additional risk reduction, but that's also a testament to the tool working, once those measurements start to balance themselves out.
Then there's accountability on both sides, the vendor and the customer. Did we deliver what was promised and meet the expectations on both sides? And where can we make improvements?
I think you have to have those continuous conversations with your partner. The best relationships a long-term relationship. If I can get a 10-year technology investment out of a particular partner, that's a successful engagement.
But sometimes the vendor's roadmap doesn't necessarily align with what's happening in the real world, particularly from an emerging threat perspective. You've got to have those difficult conversations with them and say, "Look, guys, you need to adjust because the threat landscape is moving in this direction. You ultimately need to change with-it, or we're going to have to reevaluate our partnership"
Q15. Did you have anything that we didn't cover that you were hoping I'd ask you or that you wanted to include in the article?
I would just reiterate that building a strong security program takes more than simply investing in technology. It starts with having the right foundational controls in place and making thoughtful investments that strengthen them and reduce friction. Partnerships with organizations like Cyber Security Tribe are also very valuable in the decision-making process, helping security leaders gain insights, share experiences, and make more informed investment decisions.

