Library Header Image Library Header Image

Addressing the Tradeoffs of Adopting a Unified CNAPP


Posted on in Podcasts

Consolidating siloed cloud security tools into a unified cloud-native application protection platform (CNAPP) can cut alert fatigue, reduce tool sprawl, and sharpen risk correlation, but the move carries real tradeoffs that vendor pitches rarely spell out. In this episode of the RSAC Cyber at the Top Podcast, Steve Turner, Head of Security Platforms at Guardian, brings a platform leader’s perspective to what CNAPP consolidation actually costs, what it delivers, and when it’s the wrong call.

Listeners will come away able to:

  • Compare a unified CNAPP with alternative cloud security architectures
  • Anticipate common CNAPP migration risks and plan practical mitigations
  • Recognize when security tool consolidation may not fit your environment
  • Apply a clear framework for deciding whether, when, and how to consolidate

For security leaders and cloud security architects evaluating their stack, this conversation offers a practitioner’s view of CNAPP beyond the promise.

Podcast Transcript

Host:                     Welcome to the RSAC Cyber at the Top podcast, where security leaders across industries share the strategies, hard lessons, and real experiences shaping modern cybersecurity and AI. Insights are grounded in community and built for every level of profession.

 

Tatyana Sanchez:        Hello, listeners. Welcome to this edition of the RSAC Cyber at the Top podcast series. Thank you for tuning in. I’m Tatyana Sanchez.

 

Kacy Zurkus:              And I’m Kacy Zurkus.

 

Tatyana Sanchez:        And we are your RSAC podcast hosts. Kacy, what are we going to discuss today?

 

Kacy Zurkus:              Well, we are not talking about AI which is really cool. Instead we’re going to talk about cloud security. So, today we’re looking at a big decision in cloud security: whether to consolidate your tools into a unified cloud native application protection platform which is also known as CNAPP. The pitch is compelling, for sure, with less alert fatigue, better risk correlation, and fewer consoles to judge, but it isn’t necessarily a free win.

 

                              So, we’re excited to be joined today by Steve Turner who will explore how a unified platform stacks up against alternative architectures, the migration risks to plan for and how to mitigate them as well as looking at the situations where a consolidation may not actually be the right call.

 

                              Super excited today for our conversation, Tatyana.

 

Tatyana Sanchez:        I know. I am too, but before we get started we do want to remind our listeners that here at RSAC we host podcasts twice a month and we encourage you to subscribe, rate, and review us on your preferred podcast app so that you can be notified when new tracks are posted.

 

                              And now, we would like to ask our guest to formally introduce himself before we dive in. Steve, over to you.

 

Steve Turner:              Thanks, Tatyana and Kacy. It’s great to be here. I’m Steve Turner. I currently head Security Platforms over at Guardian. I spent the majority of my career bouncing around different architecture and leadership roles between Microsoft, Prudential and a few other companies.

 

                              I’m a huge security automation nerd and a big believer in building paved roads for developers rather than throwing up roadblocks.

 

Tatyana Sanchez:        Well, thank you so much, Steve, for being here today And as Kacy mentioned, a unified CNAPP promises less alert fatigue and better risk correlation. But beyond these two promises, what’s really driving the push towards consolidation?

 

Steve Turner:              So, as both of you know, security has been littered with alerts. So, for a lot of practitioners out there in the field it really boils down to context and sprawl. When you have all of those separate siloed tools for things like posture management and container security and identity governance, security teams are just drowning in those disconnected alerts from all of those different platforms.

 

                              The push for consolidation has been driven by this dream of logging into one single pane of glass or one platform and seeing the full attack path end to end knowing that things like overly permissive IAM rules are directly tied to a public-facing vulnerability rather than hunting and pecking through alerts in their SIM.

 

Tatyana Sanchez:        And you mentioned the goal is to see the full attack from end to end. So,  when someone does consolidate their tools into a unified CNAPP, how well does that promise really hold up in cloud environments?

 

Steve Turner:              So, I love that question because in reality it takes work. I think that there’s this misunderstanding out there in the industry that you don’t just buy a CNAPP, plug it in and magically get perfection.

 

                              A lot of the platforms have evolved incredibly well over the years but you still have to integrate them deeply into your developer workflows like Terraform pipelines or other code pipelines that you have in your organization because the context actually has to make sense to the builders and the other folks that are looking at these platforms at the end of the day.

 

                              If the tool can’t speak the language of your organization, then the promise completely falls flat.

 

Kacy Zurkus:              Steve, I’m wondering, though, how does a unified CNAPP compare with alternative security architectures like a best-of-breed cloud security stack or even your cloud provider’s native tooling?

 

Steve Turner:              So, I love this question, Kacy. So, it’s this classic jack-of-all-trades versus master-of-none dilemma. Best-of-breed tools give us the absolute deepest visibility into very niche areas but your SOC team has to manually correlate those container alerts with things like an AWS IAM alert from a completely different dashboard.

 

                              But on the flipside, a native cloud provider tooling is absolutely fantastic because it’s virtually frictionless to turn on, but the problem that comes to a head pretty quickly is that it struggles the second you introduce a multi-cloud strategy where a unified CNAPP—like you were mentioning earlier—sits right in the middle, is tying those disparate environments together.

 

Kacy Zurkus:              But there have to be tradeoffs, right? Like you were talking about manually correlating becomes really frictionless but it’s seamless to turn on and the struggle is with the multi-cloud strategy. So, what are the tradeoffs of each of these different approaches?

 

Steve Turner:              Yes. So, like you said, with anything there’s always a tradeoff otherwise we probably all wouldn’t have a job in this industry at this point.

 

                              So, the main tradeoff with consolidation, just like any platform play, is that you might sacrifice about 10% of that ultra-deep granular capability that you get from the best-in-breed niche tool.

 

                              In return, the promise of these platforms is that you’re gaining 90% better context across domain correlation. The things that organizations have traditionally struggled with whether it’s building threat detections or anything along those lines, the big thing here is that for most enterprise teams they’re trying to reduce alert fatigue and actually prioritize real risk.

 

                              And that’s the trade worth, in my opinion, making every time.

 

Tatyana Sanchez:        And we touch on tradeoffs, but what about risk? So, Steve, for teams that decide to consolidate today, what migration risk had to come up such as coverage gaps or disruption to existing workflows?

 

Steve Turner:              As organizations have gone through their variety of different cloud journeys, disruption to workflows across the organization is the biggest one by far. I like to talk about this in the context of developer workflows.

 

                              So, for example, if your engineering teams are used to getting a specific Slack alert or Jira ticket from a legacy vulnerability scanner and you suddenly rip out that thing underneath them without warning, you’re going to break their trust and quickly become “the department of no.”

 

                              There is a path. Like I was referring to earlier, one of my favorite things is building out those golden paths ahead of time with collective agreement on what those paths look like.

 

Tatyana Sanchez:        And say for teams that don’t build that golden path, how can teams mitigate them along the way and mitigate the rest that they come across?

 

Steve Turner:              Yes. So, I’m a big fan of having the solutions running in parallel during the transition. So, go ahead and set up that new CNAPP solution and have those findings go into a staging environment.

 

                              That’s where you should be tuning the noise out, validating whether those paths you’ve created are the actual golden paths that you want within your organization and making sure the signal-to-noise ratio is genuinely better before you deprecate the old tooling.

 

                              The biggest misunderstanding I’ve seen out there in the industry especially with the advent of a lot of these solutions is that they treat these migrations as just a technical cutover where in reality it’s a large cultural shift.

 

                              Like I was mentioning, the biggest thing that I’ve seen be extremely successful for a lot of these deployments is that you’re bringing your stakeholders, such as those developers, along for the ride and proving to them that the new unified solution will actually save them time at the end of the day.

 

Kacy Zurkus:              But there also have to be those situations where consolidating just isn’t the right fit. What are some of those that you’ve seen in your experience?

 

Steve Turner:              Yes, that’s a good callout. So, the situations where I’ve seen consolidation not being a totally right fit or just maybe not the right fit at all, it’s like if you have a very hyper-specialized environment.

 

                              Maybe you’re running heavily customized on-premises infrastructure alongside your cloud deployment or your footprint when you talk about cloud is entirely sitting within a single cloud provider utilizing the specific services that that cloud provider has spun up and introducing something like a third-party CNAPP doesn’t fully support a lot of those scenarios.

 

                              So, that’s where sticking to native or specialized tools makes sense. The analogy that I like to use is you don’t force a square peg into a round hole just for the sake of saying that you have a single dashboard now.

 

Kacy Zurkus:              I just used that phrase today. {Laughter} I love that expression. And so for those listeners weighing their decision, what is one concrete step they can take to figure out whether, when, and how they should make the move?

 

Steve Turner:              For those folks out there that want to validate whether this journey makes sense for them, what I’d argue is the first thing that they should be doing today is mapping out their top three most critical cloud risks right now.

 

                              Now, when they’ve mapped those out, if their current disconnected security stack takes their team hours or days to piece together a brand new alert for those specific risks, then they’ve immediately got their answer. A unified CNAPP may solve that problem for them.

 

                              I’d tell them as a follow up to that they should be spinning up a small nonproduction cloud account giving read-only access to these CNAPP solutions and see if it actually connects the dots faster than your current teams or process.

 

                              This is a very immediate way to prove if the value is there before they go and throw their whole selves or their whole organization into investing in a CNAPP platform.

 

Kacy Zurkus:              Steve, thanks so much for being here with us today. It’s an important conversation. Practitioners are having to make these kinds of decisions every day and understanding whether, when, why, and how is really helpful.

 

                              So, listeners, thank you for tuning in. I hope you learned something from this. And a friendly reminder that registration for RSAConference 2027 is now open. So, register today by visiting RSAConference.com/USA/passesandrates.

 

            So, please keep the conversation going in our RSAC membership platform by visiting onersac.com/membership. Be sure to check onerasc.com for new content posted year-round. Until next time.


Participants
Steven Turner

Head of Security Platforms, Guardian


Share With Your Community