Transcript of https://www.youtube.com/watch?v=BPdlPgOz9oc, published 2026-03-13. Auto-generated captions, lightly corrected; the video is the canonical version.

Why Security Can’t Stop at Compliance | SOC 2, ISO 27001, and Continuous Security

So, uh, just getting started here. Give, uh, give everyone a chance to get settled in and then we'll get get going. >> Sounds good. >> All right. So, it looks like we have some people joining still. Um, well, let's go ahead and uh let's go ahead and get started on this. Hi, everyone. Thanks for joining us today. Our session's a fun one titled why security can't stop at compliance. Uh and the idea here is not to knock compliance in any way. It's to it's to build on it. Uh for most SAS teams, earning uh that first SOC 2 or that ISO certification is a huge milestone. Don't want to take anything away from that. uh

you know it's critical to unlocking deals, building customer trust and proving that uh all your hard work as you go and pursue compliance has paid off but really it's you know it's the starting line. It's not uh it's not the finish line. So I think the the reality is uh as you both are going to comment on later in the session that threats evolve faster than audit cycles especially now uh in our current shifting landscape. uh and staying secure means finding ways to keep that same level of competence in between audits that you get validation on uh year-over-year. So today we're going to talk about how to turn compliance wins into continuous trust uh excuse

me continuous security and we're going to talk through some practical ways to stay audit ready and trusted throughout the year. Uh I'm joined by Marie and an uh Marie Joseph Anh Pham uh both who whom have deep levels of expertise in compliance and technical testing and together we're going to talk through uh what's working in the field and where we're where we uh where to start. So uh with that let's uh let's dive in with some quick intros on Marie. You want to give some intros on your background? >> Sure. You want to go first or you want me to? >> I I can. Yeah. Um hi everyone. My name is Anh Pham. I'm currently

the director of penetration testing and security here at Trava. I've been here with Trava for about four years. Um started as a security engineer. Um growing to and overseeing our security program. Um help us achieve ISO compliance and now leading our penetration testing practice. Um and then I've been in the industry for about 12 years also in security operation and security engineering as well. >> And I'm Marie. I'm the manager of compliance advisory here at Trava Security. I help a lot of our clients go through their SOC 2 and ISO 27,0001 audits mainly but also do a lot of other security and come security and privacy audits as well. Um just really helping them get

to that finish line but then also getting them to go above and beyond with their security program. >> That's awesome. Thanks for the background. So looks like you guys are well verssed in this topic. So uh so let's just let's jump in, right? Let's be honest. uh for a lot of SAS leaders, early stage founders, uh rapid growth organizations, uh getting SOC 2 it feels a bit like climbing Everest, right? You've got competing priorities, you're trying to push product, trying to drive new revenue streams, uh hard to take your eye off the bottle of that. So, it's a major milestone. It's expensive. It's hard to do. Uh and you should celebrate it. Um but what

but what we have seen in the market is that compliance isn't sort of the end of the journey as I mentioned right it's the beginning of uh the story as it were uh and so what we want to talk about today is sort of that next chapter as you think about maturing your compliance and security program so you know I think if you look across LinkedIn there's lots of conversation around checkbox compliance and it's really easy to take a point of view that that is um you know a negative but uh like from my my point of view it's kind of like going gym. Going to the gym once a week, it's a great start.

Uh but uh I think everyone would agree, right? Going to the gym a couple times a week on a more consistent basis is definitely better for your health. So uh sort of the concept here. So it's about how can teams build on the success of their initial compliance activities to become more resilient, trusted and scalable. And then our goal today is uh obviously to share some ideas around how to do that. So let me just ask the uh the panel here. So if compliance isn't the finish line, what really is? And that's where I want to start. So from your point of view, Marie, what's next after you get that initial certification? >> Yeah, I

think what what you said earlier about how it needs to be celebrated definitely need to take the time to celebrate that you got that certification, you went through that all that hard work to build that program because that is usually that initial building is getting that start first certification. Um, and it's really not a finish line and more of a starting line because now you have this program to upkeep. So you're now you kind of will probably have more time now to prep for the next audit because it now is an annual thing once you get one certification and you now have to go through that on an annual basis. So now you get the

opportunity to make that more routine kind of like going to the gym and like making those like scheduling out when you're going to do X Y and Z and making it easier for yourself. And then you can also look for those opportunities of improvement which can kind of be in like any area in your compliance area like compliance framework and then focusing more so on security as you continue to grow just because both security and compliance are an everchanging landscape. So your program should also be growing with it >> on any uh any additional perspective or just double click double uh thumbs up on what Marie said. Yeah, I think Marie said pretty much everything

that has to be said. I mean, the I was going to say that there's really no finish line in security and compliance, right? Because the threat actor don't stop, the hackers don't stop, like nothing is ever stopping in security and compliance. So, if you approach compliance as the end goal, you already fail before you begin. I think um compliment like you know um doubling doubling down on the gym metaphors like you go to the gym once you know what equipment were there you learn how to use it but unless you continue to do it right frequently you don't really know how to use it effectively you don't really know how to use it to to

achieve your goal so complian help you you know determine what control you need but you got to really keep practicing it to get better at it >> yeah and some might even say it's a little painful that first time right uh I think little sore, right? Especially if you start stop. So sometimes it's easier to just keep going. So let's uh let's continue on this thread, right? Why are we having this conversation right now? Uh I think AI as a backdrop is certainly an interesting topic and what that means from an audit, security, compliance perspective, but what are you all seeing in the industry? Why are we having a conversation now? I mean, I feel

like the security like we were talking about um like everything is getting kind of worse in a way with like all the hackers. Like there's more threats like every single day. So people like your prospects and customers are really looking for you to have a better security for your company internally. So like that's very important to them that you have some certification usually or that you have um you probably fill out security questionnaires where they'll ask about different types of controls and seeing like what type of program you have even even if you don't have assert. So I'd say that's why it's super important just because everything's constantly changing and I would say most like

I see most of my customers start with SOC 2 or ISO 2701 really to start that baseline and kind of get started on their journey. >> Yeah, I would agree with Marie. I think then you brought up a good point about Mar about AI as well because not only that threat actor aren't slowing down they're moving faster right they're moving a lot faster with the advancement of AI we already seen example of people using AI to help them conduct more attack and faster attack and more targeted attacks so um it's very relevant to today is why we need continuous security continuous validation continuous compliance at the same time I'm also seeing that um enterprise customer

getting smarter and even not enterprise customer like customer in general are getting smarter right they don't more people are asking to see real evident of security these day not just compliant audit you know getting a good audit getting a good report is good but I'm seeing more evident of customer asking for more on top of those things right >> yeah that's such a that's such an interesting uh comment there on I think it actually a fantastic segue to the next question I want to talk to you all about is what does SOC 2 really, you know, capture. Same with ISO, right? But, but the way I think about it is, uh, if SOC 2 is

like a professional headsh shot, right? You have the opportunity to prepare for it your first time and then on your reertification, um, it captures you looking at your best on that particular day, right? You get the opportunity to get all the evidence in order, prepare for it. You have to have demonstrable evidence over the course of that period of time, especially for your, you know, your second, third, etc. year. Continuing on the gym analogy, right? can keep going at it. Um, but it doesn't tell the whole story of how you look. Uh, you know, that next morning after you've completed it, right? You get, uh, sort of like an allnighter. Um, so, so Marie, maybe

for you, for anyone less familiar with the concept of SOCK or not concept, but of SOC 2, you know, what does it really entail? and and often times we're hearing it sort of like the seal of security with uh when customers come to us. Um what does it really entail uh from your you know your experience? >> Yeah, great question. So I would say every framework they they basically pick kind of like it's kind of like a grocery list and they pick their favorite security topics and throw them into a framework and that is like what you're going to be audited on. Um, when it comes to SOC 2, they have a lot of aspects

that are going to be security focused and driven and also kind of like personnel driven like with like a lot of HR functions. So, with a type one, they're really looking at just kind of like they're looking just at a moment in time like did you have all these policies, processes, and technology in place. They're not really looking to see if they truly operate effectively yet. And that's really where the type two has more value to a lot of people that review your certifications because the type two is going to look at usually about a year. Some people will do as short as three months of like all those controls and policies operating the way

you've written them to. So like a lot of times you'll say you do this annually, this quarterly, this monthly. So the type two is when the auditor will come in and see say like well you say this you do this weekly here are 10 weeks I would like to see the evidence of you performing vulnerability scans on a weekly basis and you actually triaging those scans on the weekly basis. So that's kind of where they look into that. Um it's really SOC 2 does a lot of that especially with the type two the sampling approach to see if the controls are operating. Um, I would say in some cases too, people can get lucky and

if they know they have a miss and the auditor doesn't pick that week or that month where there was a miss, they kind of got lucky. But that also means your security program wasn't operating effectively where it doesn't. That is where I would say it's kind of like the misunderstanding of it's not really a 247 constantly secure program if that makes sense. >> So, so maybe like a a continuation on that. Um so what's an opportunity that you often see as a area for continuous improvement uh even coming out of a SOC 2 uh type one or type two uh engagement? >> That's a good question. I would say sometimes it also changes depending on

the year and with auditors. But I would say two of the bigger ones that auditors for SOC 2 have really been digging into are vulnerability management and access reviews. Um they tend to sample a lot more on those right now. I've noticed um when it comes to like the vulnerability management, which I talked about briefly, a lot of people will say they do these things monthly, but they've really been digging into, well, you had a 100 critical vulnerabilities show up. I need to see proof that they were all resolved within what you wrote in your policy. So that's been really catching people within their SOC 2 program because they think that okay I was doing

it I was running the scans and like at least looking at them but not doing the part where you are actually triaging and following your policy that way where um it kind of goes back to what we were talking about earlier with the misunderstanding of the 247 security. And then the other example is like the access reviews that auditors have been digging into. Um a lot of the times like best practice is to do these quarterly. Sometimes I would say that can also be a pretty big miss for people because in one case they're like, "Oh, nothing's changed. We haven't hired or offboarded anyone." So like, do I really need to look at that where

you really should be evaluating the access and to and what people have access to? Probably more frequently than quarterly if I'm being honest. Like anytime something new comes into your system or anytime someone new is added or gone, it's a good time to just review those things if possible. Um, but it's I would say those are kind of the bigger the two things. >> Yeah, makes a ton of sense. An do you have a point of view on that too that you would uh echo or add to? >> Yeah, I think I'd like to drill [clears throat] into something that Marie said there and really go back to your original question of why software is

often misunderstood as a 27 247 s of security, right? Because like Marie said, a lot of auditor, software auditor really like to drill into vulnerability management and access review because those are easier area to get good evidence of. So evidence of good control, right? You show, you know, some sort of policy that show you're doing an access review, you show a scan report, that kind of thing. And you pass of that control. But really where it transition from compliance to security is all right. Now that you show what good looks like and how you need to design a control for it to be good, how do you know when it's stop being good? Like how

do you know in the you know 365 day when they fail one day? How do you know that? Right? So that's not really in scope of any sort of compliance audit, right? It's it's you know they they help you define what the control is but they don't really spell out exact step on how to continue to validate that validate or control monitor those. Even in a soft two type two with a 30 365 day monitoring windows as Murray said most actors going to sample certain things right they're not going to look at logs and evidence from every day so it's really hard to justify and say that soft two should be a 247 set of

security of security because it's just really not. So um yeah, just some some area I like to drill into and just to show why, you know, it's important to continue to to you know, um grow from the initial soft to audits component. So something that stands out to me right is uh audits have historically been conducted by humans uh and part of the reason a sampling approach is taken is because of just the sheer number of hours that it would take to review all of the evidence over the period of time um in the you know the past 24 excuse me the past 12 months AI as a technology is certainly a force multiplier u

maybe it's a hot take, but I could see a world in which AI is a way to like drive a more comprehensive audit and a greater sample size and do some validation at scale, right? And I think that is almost a catalyst for hey, sampling is not going to be enough in the future. And do you want to be prepared for a continuous security posture that look I I'm not saying what the AICPA is going to do or what ISO is going to do but is there a world in which an audit is more continuous and so you have to be prepared for that in the future. Oh yeah, I 100%. I mean we already

see in I mean if you just look at today and compared to a year ago, we already see a lot of new use cases of AI application that we've never thought about like in the last in you know last 100 years or so of history of technology. So I can I totally think it's reasonable to think that AI will you know start to play a bigger part in audit and that's when it will create a really big disruption in how company pass audit right and maybe you know it will create a bit of a chaos ates first but I think that's good chaos to have because that's really start to push people to move into

more of a continuous validation mindset making sure that at any given point in time if somebody look at your environment you're good right >> yeah so so coming back to the you know the topic uh that we're really trying to address uh around is SOC 2 247 security uh SOC 2 not sock operation center but it sounds like if I were to boil it down it's not that compliance is failing in any sort of way it's it's a snapshot in time looking back even over a period uh and ultimately attackers aren't taking snapshots right they're taking opportunities and they're trying to do it on a continuous basis so um while audits may be a catalyst

for continuous security uh in the long term especially with the adoption of AI uh what we're seeing right now is that teams are looking for ways to more continuously validate security between audits um so you know looking across the the landscape of customers that you've worked with that have come to Trava uh I think it's fair to say that sometimes compliance can can create complacency right you feel like you've done it, but the threats are evolving daily. So, Marie, you've seen and helped a lot of companies go through this landscape uh and their compliance cycles. You mentioned user access reviews. You mentioned um vulnerability management. Curious from your point of view, what are some other

common gaps or oversightes that can leave an organization exposed maybe even after they've passed an audit uh that you want to talk through? Yes, I would say one of the big things I focus on after we get through that celebrating, we got that certification um is really focusing on better organization for the next year to make their lives easier and my life easier too when I help them manage their program is like so better planning and then looking for those gaps. I would say we sometimes get a like a good amount of opportunities for improvement both from like things I analyze while going through the audit with you and then also from the auditor themselves

where we start planning on let's make these things better because they there's a possibility they dig into those next year or if I was the auditor I would dig into these areas and I'm considering this like a kind of a gap for you. you got lucky they didn't catch it or ask about it but like let's mature your program where I think a lot of the time um some of those items can also come from like the typical risk assessment we do with the customer just because we typically do evaluate your security posture on a different framework than a than the certification you're going for. So like that risk assessment with the risk register and

risk mitigation roadmap are the best stepping stones I like to focus on right after the audit and kind of make that switch back from compliance to security because it's also maintaining that security program that you just built. >> Yeah, I like to always think about security posture as like a perishable item kind of thing, right? It's like you know once you set it up if you don't do anything with it it's going to ages over time every time some you know somebody change like personnel chain asset chain application change you know it's going to impact your security posture in most likely a bad way compliant help you establish that initial posture but if you are

happy and just stop there let the moment a compliant audit report your perishible period begin right posture is not going to stop paris so you need to take care of it you need to maintain it you need to evaluate and validate and monitor improve it, you know. >> So, with that in mind, right, uh every program's different like I uh I get that. Um are there any reoccurring areas where you typically would recommend uh organizations start uh coming out of that compliance uh that first compliance certification or is it different for each organization? >> I think it it's usually going to be different. Sometimes it really depends on your results. Um, I like to look

at what were the biggest pain points during that audit, which I kind of already talked about, like what was something that took us a lot longer to gather all that evidence and why? Is there a better way we could automate that control in some way? Can we utilize AI? Can we utilize buying a new tool? Or should we get rid of a tool in general and maybe it's easier to do it manually? Like did the tool create more of a headache? So, kind of re-evaluating the tech stack. Um, and then also looking at if the auditor gave us opportunities for improvement, definitely focusing on those or that's like the first thing I do because they're

definitely going to come asking for those again next year and want to see you improve. So like those are easy wins for you. Okay, makes a ton of sense. So since it's different for every organization, maybe here's a a fun question. when does it make sense to start shifting your uh point of view or your approach from that compliance first point of view to a riskbased point of view because it sounds like ultimately it's a business decision. There's no clear roadmap to do this for every organization. Um so when does it make sense to do that and and sort of what's your recommendation around like how do you come to that decision of [clears throat]

when? Yeah, I would say on you want to talk about that first? Oh, I was going to say I think personally I think the best time to shift from sort of that compliant driven lens of view into a you know risk driven or security driven probably right after your first audit right because at that point you have an established structure for your security and complant program you have the control in place but as I said it's going to stop paris so now you need to start looking at how to validate them continuously how to make sure that they operate continuously right And the earlier you start the better because the more you lay the more

tech debts are going to get built up and then it's just going to get really hard to get back to the initial stage right before you start person. >> Yeah, I was going to say the same thing too about that really like post audit is what I usually recommend for most companies that I work with. But if you're lucky enough in just starting a product too, you do have that opportunity to kind of start with security and build with like security in mind and kind of do it both in parallel at the beginning where you're a little luckier than people that have already had a company for a while now and then have to find

a way to kind of build it in and do that checkbox compliance and then focus on it after the audit. >> Yeah, make it makes sense. And it sounds like tying it back to one of your earlier comments on uh enterprise buyers, mid-market buyers are not looking at this strictly from a report uh and certification perspective. Uh it matters to them from a demonstrable evidence perspective, you know, a day over day. Um so it's a trust conversation, not just a one about compliance, right? And trust is certainly the currency for for SAS growth. So, uh, with that concept in mind, if compliance is our foundation, what's the simplest way that you found to to keep

that foundation strong throughout the year on, um, on would love to hear your perspective on that. >> I'm going to keep beating on a dead horse here, but it really come down to two basic thing, right? Visibility and validation. Um, you know, you get past your initial audit, you shouldn't stop there. You need to make sure that you have a way to to get continuous constant visibility into everything that's in your environment, assets, environment, services, application, system, everything, right? At any given point in time, somebody should be able to go to you and ask you what do you have? And you should be able to answer that with confidence. And then after that, you really

need to start looking at continuous validation. And you don't have to get too fancy, right? Just start simple. Pick a pick something that you have just passed um you know your first audit for and just ask yourself how will I know when this drift how will I know when this change right what can I do today to make sure that I always have visibility into this and validation that this is working start simple be scrappy and then use that as a stepping stone in your foundation to do more of that to other control right so once you have once you really get into this repeatable habit of reading validation It's easy to be validation for

a lot of other control in the combined program, right? >> Yeah. And on this is where the concept around pen testing uh comes into play, right? And maybe more frequent pen testing than just the once a year. So um can you share a bit about how penetration testing or PTAZ uh is bridging the gap between you know the audit and testing and validating that the controls and the technology are actually working. >> Yeah. Uh definitely. Yeah. So pest I mean as the name implies penetration testing as a service is really about embedding security testing deep into your operation um your operating processes right your your daily operation um not just once a year but continuously

on continuously and on demand you know traditionally most people think of pentest as these big heavyweight exercises that's done one a year for compliance but the moment a traditional pentest report delivery change and that's even more true in smaller and mediumsiz companies right because they ship fast they change all the time um to make sure they continue to grow so pas bridge that gap right so you know if you conduct pach you can use that towards achieving the complian but at the same time you also now have a mechanism to validate that your control continue to work post compliance right um by you know by doing continuous testing on anything that change within your environment

And PTAZ is not a full-blown red team type exercise. Like what would you characterize as the difference between PAS and and something like a red team? >> Um yeah. So PAS is a lot more scope right compared to to red team. It's scope down to what change. So it's a very targeted, very focused, very uh surgical kind of activity. um you know it's it's a continuous engagement but every time you conduct a test you are being surgical about it. You only test what change you only validate your control. A red team is a little more loose in scope. Um it's also a little more ambiguous right the goal there is to see if somebody can

go in to your environment and extract data. Um you know it can cover control that haven't changed control that have changed. You know it really doesn't look at things from a control layer. that look at the environment as a whole. >> Yeah. And so for those organizations that we tend to work with fairly often, companies that are driving change within their product, it sounds like PTAZ is going to be a super valuable next step after an annual style punest and before maybe get into a red team style engagement. Is that fair to say? >> Yep. Exactly. Yep. So it's gonna so PTA is going to give you more visibility, greater control uh between the audits

and it's like an early warning system uh for you instead of reacting just once a year and and driving all those activities. >> Yep. Yeah. Pas I mean I like to think of PAS like a control validation mechanism that you put in place, right? A red team conduct strategically will help you detect if new control are needed and then once you implement those control in those then become part of pas again right this this continuous validation so they really be on top of each other >> so with with that in mind um it's not this isn't a conversation about compliance or security right it's compliance and security conversation so how do you see these frameworks

like SOC 2 or ISO uh 2701 helping to guide the continuous security programs Um for organizations >> I would say >> go ahead say the big thing is like it really is creating that baseline. Um like we were talking about earlier it's like the good stepping stone. Let's get started. Let's start a program. And then I know you guys keep alluding to kind of like the habit in the gym analogy but like also like building that habit is like one of the bigger things. Um, I know I work a lot with my customers of in order to build that habit. It's just kind of like scheduling it out in the year. Whether that means like

they sit on a call with me and I watch them do it or I help them do it or do it for them. It's kind of collabing together so that they also are getting into that habit and then can choose a way to build their security program better and like take some of my advice to like make it easier on them throughout the year. >> Yeah, it makes uh makes it makes a ton of sense. Um, and I think one of the things I I uh would ask if I were sitting in the seat of a SAS founder is this gonna make SOC 2 easier next year? >> Yep. 100%. You know, instead of scrambling

to do things, you know, three months out of a year to make sure that you have everything. If you embed security and continuous security into your compliance and security program, you don't really have to worry about an audit period, right? when it happened, you already have all the evidence. You already have, you know, all the control. You already validate that they all working. So, it's really just it's almost like you would be welcome. You would be encouraged to invite people to look at your environment, right? It's almost like rack and dry at that point. >> And do you think paz is something reserved for more mature organizations, larger organizations, or are there others that can

benefit from it too? Huh? >> Well, that's that's the problem. I think um [clears throat] the industry right now there's a false saying in in industry that PAS and more like continuous security practices are only for large enterprises right which I completely disagree with because it's actually very valuable to smaller and fastmoving company grow company because they are the company that change more often like probably three four 10 time faster than large enterprises right so they could really benefit from having these validation in place having these practice having these controlling place and then they are also the company that don't really have the in-house resource to conduct these right so PAS as a you know

penetration testing as a service and other kind of you know as a service offering um really complement them that way they get the benefit the artistry and compliant benefit but they don't at you know at a fraction of the cost if they were to hire a full-time pentest team for example >> so it it sounds like from a ROI perspective um fewer surprises at the time of your audit, definitely stronger credibility, your customers, being able to show continuous testing. Um so less less of a firefighting type environment and more of like enabling your sales organization to go drive really uh trustworthy conversations with your customer. Is that fair to say? >> Yep. You're not just

audit ready. You're now audit ready, customer ready, market ready, grow ready, scale ready, right? You're always ready. >> Yeah. Yeah. makes makes sense. I'm just looking at the time here. We're getting close on it. So, uh I want to make sure we leave some opportunity for questions from the audience. But before we do that, right, um we've talked about the foundation. We've talked about how you build on it. Uh let me ask you an and Marie uh what's one thing that every SAS leader founder or CEO or you know leader throughout the organization regardless of whether they're two people or 50 or you know more uh headcount organizations what should they do after this conversation?

>> Mar you want to start? >> Sure. Uh, I would say after this conversation, I personally would review my compliance program and security program and just look at what have been my biggest headaches over the past year and then kind of looking at the looking for a better approach on how you could make them easier. Do you know solutions that could make them easier? Do you need to contact someone and collaborate to make those things easier for you? And like looking at those things because there probably is a solution out there to make it a little better. And then really creating that habit and figuring out is there a way I can create a habit

out of this to make it more so part of my daily routine and not feel like it's something I dread getting to every month or quarter when it comes up. >> Yep. Yeah. My recommendation is a little more technical. Um I like you know I think I would advise that you just go back to your recently passed sort of audit and complant book and and report. Pick one control and again figure out how you're gonna validate it. Don't wait until next year for your auditor to validate it. Right? So if you can like think about it as like if you've been forced to validate this every single day, how would you do it? Because that's

really is going to force you into building you know healthy validation habit and framework that you can use to apply to your entire program. [snorts] >> And so on that thread on if someone wanted to explore EAZ, what does getting started look like? uh with Java for example. >> Yeah. Uh it's actually [clears throat] pretty simple. I mean we'll start by having a discussion to make sure that we understand your environment, your priority, your business objective, you know, how you operate and then from there you know we'll conduct a scoping exercise so that we can define you know what's important to you, what need to be in scope for testing, what need to be excluded,

what can wait until you know um future maturity state that kind of things. And then once we have all of that then we basically define an engagement structure and process and then we just get right into testing and we just repeat that and deliver value and report to you and you fix them and we test them again and then the cycle just keep repeating itself. >> That's awesome. Okay, that's perfect. So um that that sort of concludes the session that we had planned for today. Uh so if if maybe I just wrap it up real quick and summarize, right? So I think one of the things I I hope everyone takes away from this is

uh one compliance is not the launch pad. Excuse me. Compliance is the launch pad is not the landing zone, right? Especially in the age of AI becoming so much more prevalent. Um, continuous validation super [snorts] valuable, not just from a reducing your risk and exposure perspective, but also as a sales tool to drive trust with your customers and whether that's through PAZ or vulnerability management or policy automation, right? Like these are all positive net positives to your uh posture as a business. Um, and it's giving you the confidence to say to your customers, yes, we're compliant, but also we're secure. uh which is you know equally important. Uh and if you're curious uh what that

looks like in practice uh that's exactly where we come in. We're working with organizations that um want to keep their SAS uh products secure, keep their businesses secure and stay audit ready on a continuous basis and uh grow as a organization. Uh so we'd welcome the uh opportunity to chat with you at any point in time. Uh let's let's open it up to questions and um scrolling over the chat here. Uh so uh first question I see um question to you. How do you see AI changing the way pent testing or continuous security will be done in the next few years? >> Yeah, I mean this [clears throat] is a good question. is also a

very relevant question. I think as I said earlier in this conversation, we keep seeing new application of AI popping up every day even including things that we never thought before and a lot of these new application are in security in general and also in pentesting right actors are using AI to scale attacks um create new fishing template run malware even scoping you know scanning internet scanning the internet to identify new target and then defender I'm using it for smart smarter detection you know lock analysis, lock correlation and that kind of stuff. In pentesting specifically um we're seeing a lot of evidence of AI being used for recon work writing exploit chaining attack together you know

performing the typical um technical you know attack at scale um and then that I think that will in inevitably make those kind of attack a commodity you know kind of analysis and detection of commodity um and then naturally I think that would drive the entire industry towards continuous lighting ation, you know, using AI to continuously validate that your control are working, your defenses are working, because on the other side, the bad people are probably going to use AI to continuous to attack your environment. Here's here's one more question uh on um when is the right time to add PADS if we're just starting on our compliance program. >> I think right after you're in the

audit is probably the sweet spot. You know if you in between type one and type two um the earlier in type two you start the better because you know what after you finish your type one you already build you already have a good idea of what your controls are. You have you basically type one is to say that you implement those control and then type two is about monitoring. So right after you finish your type one is probably the best spot to embed to start embedding pas into your process because then you can also leverage all of that to help you pass your type two right because they are really pas is really good evidence

for continuous validation and monitoring making sure that your controls are working. >> So so it sounds like pas right out of the gate not something that you would recommend sort of recommend building the foundation first before you start layering on um maybe more complexity. Is that the right way to think of it? >> Yes, exactly. >> Perfect. So, does PTAZ um require any additional lift from a team that is uh engaging with Trava around PAS? >> Um not really honestly. The initial lift is probably the same as you know what you would need to do with a traditional pentest because we need to understand your environment. We need to scope your engagement. We need to

understand your asset, your exposure. But after that, you know, all the on ongoing testing activities, reporting, retesting are really done by us. Um, and all of that value is communicated to you directly. And there's really not much for you to do after that initial lift. >> Awesome. So, you're going to get more secure, better testing with relatively easy lift on your side. >> Love that. >> Um, here's one. Here's a Oh, here's a really interesting one. So, uh, the question is, how can we shift our leadership's mindset from compliance as, uh, quote unquote check the box, uh, task to, uh, valuing it more without, you know, maybe creating fear among the employees or something like

that. feel like that's a pretty it's sometimes that can be like a tougher conversation to have. Um I would say one of the things that we typically start with is really getting your leadership all like in a room and discussing security and discussing your current maturity program. Uh I would say when we look at the current maturity posture and kind of like put it out there to the leadership team that usually starts kind of that oh we should take it seriously type of moment when they see kind of their when we give them like a score and rate them like it's like getting a grade at school and we grade them like kind of low.

That's normally when I see see them being like oh I don't want to have an F or a C in this category or in total. How can we go about improving that? mainly because obviously like your security program is part of your investment of the bigger picture of your entire company and they're investing their time and money into this. So like they want to see it succeed. Um and so do your customers and prospects. So I'd say that's when kind of showing those numbers is when they kind of switch that mindset. >> Yeah. I'd like to always think about building a company as like building a house, right? Especially when you have to do compliance

like you spend a lot of time, effort, money, resource into you know getting everything designed, sketch out, laying foundation, getting it built after that. Do you want to just leave it unprotected, right? You want probably wouldn't want to leave your door unlocked. You don't want to leave your roof with uninspected. You probably don't want to skip insurance. So, you know, in that way, it's not really about fear-driven sort of approach. is just protecting what you have built, what you have worked so hard to build, right? So, it's value protection. >> Yeah. Like contingency planning, right? Like play the what if what if game almost and come away with some thoughts there. >> That's super helpful.

Uh so it looks like we've gotten to the end of the chat questions here on Marie. really appreciate you spending a bit of time with me this afternoon and talking through um going from compliance to maturing to a security program. Uh if anyone wants to get in touch with uh the Trava team, where would you recommend they go to do that? >> Traviscurity.com >> and then click the book an intro button. Right. Say, "Contact you, Dan. >> Contact me." That's right. LinkedIn, cell phone, email, respond to it all. All right. Great. Uh, Marie, really appreciate the time this afternoon. Thanks for the fun discussion. Thanks everyone for joining us. Look forward to uh chatting with

you all in the future. Take care. Bye. Bye.