Transcript of https://www.youtube.com/watch?v=sJpJYHzENSk, published 2025-12-30. Auto-generated captions, lightly corrected; the video is the canonical version.

Boost Your Cybersecurity with Continuous Threat Exposure Management (CTEM)

every day there's thousand and thousand of vulnerability data in an identifiable tool and it's just not feasible to go look through them all. So CE really help security person and team focus on really what's exploitable today and what can really lead to a compromise of you know my environment. >> Gather around as we spill the real tea on cyber security minus all the confusing jargon. I'm your host Jerroe and this podcast is where we cut through the confusion and get the truth about [music] security and compliance. This is a podcast from Trava security. So lately there's been a lot of talk about oneandone cyber security and compliance. But one thing I know for sure is

that threads change too quickly to really have that mindset. So on this episode, we're going to dive into CIM and how it's an ongoing approach that identifies and manages exposures continuously. And I have one of my co-workers an here to help us talk about that. Hey analy. >> Yeah, no problem. So just in case this is someone's first time listening to you on the podcast, please introduce yourself. >> Sure. Hi everyone, my name is Anfan. I'm currently the director of penetration testing and security here at Traava. I've been in the industry for about 12 years coming up now mostly in security engineering operation. I've been at Java for the last four year helping to mature

our security GRC program and now leading up. >> All right, fantastic. So going to go ahead and dive into it. So I mentioned it already but we really don't know what it means. So what is CTM in plain language? >> Sure. So CIM stand for adious threat exposure management. It's basically is a structure and ongoing approach or framework to finding and fixing security exposure that actually matter to an organization environment and asset. The two key words here is continuous and exposure. So that really is what separates CM now from traditional framework. It's ongoing. It need to be practiced all the time and it's focused on weaknesses that actually matter. >> Weaknesses that matter. That's important.

So CIM stands for continuous threat exposure management. >> Yes. >> All right. So how is CIM different from traditional like point in time testing? >> I mean you just pretty much describe them the major difference right? So traditional point in time testing is pretty much like a snapshot. It's done once a year. It's very static in nature. It's very report heavy meaning you know finding get dress up and then included in a one-time report get delivered and then nothing is being done to follow up on those findings. right? CM sort of change the mindset, shift the mindset a little from that static approach to, you know, approaching security more proactively. So instead of doing a

test once a year or once a quarter, you now have a repeatable process that you create to make sure that it match the way your environment change, right? And the speed that your environment is changing at. So if your environment changes a lot, you're not testing a lot. If your environment changes slower, you're not testing slower. But the the point is to continuously validate your exposure and weaknesses to make sure that you don't leave anything open for the attacker to deploy. >> Okay. Yeah, that totally makes sense. So, what are some examples of point in time testing just so people are familiar with what we're talking about? >> Sure. I think the the biggest example

or the most commonly seen example is, you know, a single annual penetration test. So a lot of company are familiar with that is a VIP is a blender exercise that happen once a year involve multiple teams right that that is coordinated. Another example is maybe a an annual audit of an environment like an assessment or that kind of thing. So very point in time and static and then occasional vulnerability scan that get run in the environment. >> So what are the main components of a CIM approach? So there are five main component of C10 and again they are a repeatable cycle. So the first one is scoping. Prior to doing anything within the C10 framework

you need to understand your asset your attack surface and your crowd jewels. What are your intellectual property? What are the thing that you need to protect? What do you have in your environment that that need to be protected? And then the second component of discovery in this component in this phase you focus on identify vulnerability and weaknesses across all of those asset and attack surface. Right? So now that you know what you know what you have in your environment you need to go and hunt and find vulnerability with on those thing that you have in your environment. The third component on the third phase is prioritization. In this phase, you basically take the result of

the second phase and the first phase together and then you combine them. So you know from the first phase you have an overview of your environment of your asset, what are the critical asset, what are non-critical all of that and then in the second phase you have a list of weaknesses and vulnerability. Now in the this perf you combine them together to really narrow down to a list of exposure that affect your most critical asset and also can lead to real penetration into your environment. Right? So once you have that then you move on to the fourth component which is validation. This is fairly straightforward now that you have a list of you know narrow

down exposure that you want to focus on in this phase. Do you actually perform testing on them to validate that those uh your theory or your assessment is valid that okay exposure can lead to cultize and then fifth phase is really the final part the final component of CM is mobilization. So in this phase take everything that was identified as reexposure or exposure that matter that had been validated that can actually be exposed and exploited and then fix that one. Right? So now that you have all you focus on fixing them and then the entire cycle repeat again. >> All right sounds like a lot of important things for sure. So, I feel like I

already have heard some of the reasons why to the question I'm about to ask you next, but why are companies moving toward CIM? What pressures and risks are really driving organizations to adopt this approach? >> Sure. So there are a few big drivers that really drive the creation of this framework and then also driving a lot of company in ter of adopting this kind of framework. So the first one is really um threat actor are evolving even faster than before because of the explosion of AI. We already >> practice of malicious actor using AI to increase the speed and complexity of the attack static point in time sort of testing and security just doesn't work

anymore attack surface is loading you know not only that we have remote work environment now I think we're moving into global workforce now so a lot of company are employing you know from abroad outside the country and multiple country multiple continent using multitude of SAS app mostly they don't build into a static one location data center anymore so your attack surface is just big and w and you need to continuously make sure that your attack surface is protected I think we're also seeing more and more leadership wanting to focus on actual security instead of a pretty dash war with some number and maybe it's the pressure is coming from regulation and complian island maybe it's

not >> pure security but either way we're seeing that more people are taking security more seriously leadership are wanting more accurate reporting of security posture and then the last one that I think is driving season is that security teams are already stretched pretty thin right in most >> every day there's thousand and thousand of vulnerability that get identifiable tool and it's just not feasible to go look through them all. So CM really help security personnel and team focus on really what's exploitable today and what can really lead to a compromise of you know my environment. >> Yeah, for sure. So let me see if I can recap some of these. So some of the pressures

include AI helping the bad guys, the fact that we are more global, our attack surface is larger, and the teams are just stretched thin with all of the regulation changes and things like that. So we are seeing more companies move into continuous approaches now. >> Correct. >> All right. So how should a business know if they're ready to adopt C10? For most business they probably should start thinking about adopting CM after they have established a foundation for the security programs right so they built they have started implementing control into the environment they have started running some basic vulnerability scan or have conducted penetration test for the first time and they have started fixing result that's

probably the best to start thinking about adopting and incor start incorporating CM faces into security framework even if they Don't start with all five faces. Is your better to start adopting some of those faces and start doing tape more continuously? >> Yeah, that sounds great. Okay, an so we've talked about CIM. I feel like I have a better understanding, but I'm going to recap this a little bit before I let you go. Okay. All right. So, CIM again stands for continuous threat exposure management. It is an approach that companies are starting to move more into as we move away from like one and done and point in time testing as our environments change and grow

because we're working on our software or the cloud or something. Is that correct? >> That's correct. Perfect summarization. >> Yeah. Perfect. Okay. So listeners, Ann and I are actually going to continue this conversation. We're going to dive a little bit more into how CIM is put into action. So if you haven't already, please make sure you subscribe so you can catch part two. Thanks for your time on >> and me. >> And that's the tea on cyber security. If you like what you listen to, please leave a review. If you need anything else from me, head on over to Trava Security. Follow wherever you get your podcast.