Latest / Code Story | Startup Podcast for CTOs, CEOs and Technical Founders / The AI Control Loop: When AI Goes Rogue - with Craig Thomas of Wallarm

Transcript

The AI Control Loop: When AI Goes Rogue - with Craig Thomas of Wallarm · Code Story | Startup Podcast for CTOs, CEOs and Technical Founders

• 0:02
  [SPEAKER_00]: Hello listeners, today we are dropping another episode in our series The AI Control Loop.
• 0:07
  [SPEAKER_00]: Out Enterprise is governed the AI they've already deployed, sponsored by our friends at Walmart.
• 0:13
  [SPEAKER_00]: Walmart is the AI Control Platform for Enterprise AI, protecting every AI workload, API, and application in production, giving CSOs the governance they need and CIOs the speed they demand.
• 0:26
  [SPEAKER_00]: Organizations choose Wallarm for a complete inventory of APIs, AI agents, and AI apps using patented AI ML-based threat detection and blocking the operates at production speeds.
• 0:39
  [SPEAKER_00]: In this episode, Craig Thomas, senior solutions engineer Wallarm, examines what rogue AI actually means in practice, where the risk materializes, and what it takes to move from detection to control.
• 0:56
  [SPEAKER_00]: Craig, thank you for being on the show today.
• 0:58
  [SPEAKER_00]: Thanks for being on code story.
• 0:59
  [SPEAKER_00]: Yeah, great to be here.
• 1:00
  [SPEAKER_00]: Appreciate it.
• 1:01
  [SPEAKER_00]: I know.
• 1:01
  [SPEAKER_00]: Absolutely, really excited to dive into our topic today around when AI goes rogue.
• 1:08
  [SPEAKER_00]: Excited to dive into that.
• 1:10
  [SPEAKER_00]: Excited to hear your perspective and bringing in all of your experience and including your experience with wall arm.
• 1:16
  [SPEAKER_00]: But before we jump into that topic, tell me a little bit about yourself.
• 1:20
  [SPEAKER_00]: Tell me in my audience a little bit about you.
• 1:22
  [SPEAKER_01]: So actually, my background, I spent over 10 years in Department of Energy in multiple roles from a network engineer all the way up to a CSO of the nuclear weapons plants.
• 1:31
  [SPEAKER_01]: So bringing the experience from the customer side and a highly regulated environment, then spent several years running a consulting company where working with those same highly regulated industries.
• 1:42
  [SPEAKER_01]: And so,
• 1:43
  [SPEAKER_01]: When I joined Wallarm, they had worked with APIs and worked with automation for quite a while, and really interested to how we bring that security to the customers, right?
• 1:53
  [SPEAKER_01]: Both from an API and an AI perspective is that that continues to evolve.
• 1:58
  [SPEAKER_01]: And then outside of work, pretty hands on, like a tar or spend time in the yard, like the mess with my long quite a bit.
• 2:05
  [SPEAKER_01]: a lot of my weekends revolve around kids activities or shows and baseball and football and so keeps me pretty busy and always somewhere to be.
• 2:13
  [SPEAKER_00]: Appreciate that overview.
• 2:15
  [SPEAKER_00]: It kind of gives me an idea of who I'm talking to.
• 2:18
  [SPEAKER_00]: Let's dive into the meat of it.
• 2:19
  [SPEAKER_00]: So again, our topic is when AI goes rogue and when we say rogue AI, what do we actually mean there?
• 2:25
  [SPEAKER_00]: What do you guys actually mean there?
• 2:27
  [SPEAKER_00]: Is it only malicious AI
• 2:32
  [SPEAKER_01]: kind of level setting where we're coming from too, right?
• 2:35
  [SPEAKER_01]: AI is really interesting.
• 2:37
  [SPEAKER_01]: The fact that it really does permeate all parts of the business from IT, cyber, compliance, obviously the business itself.
• 2:43
  [SPEAKER_01]: It's adding value and accelerating work, but how do we better discover, observe, enforce and govern that and do it at the speed of AI, right?
• 2:51
  [SPEAKER_01]: And so, some of those are starting with rogue.
• 2:54
  [SPEAKER_01]: And to your question, rogue doesn't necessarily mean militias.
• 2:58
  [SPEAKER_01]: And in a lot of times, it isn't militias.
• 3:00
  [SPEAKER_01]: most common rogue AI scenarios we're seeing are similar what we saw in the API world right they're not attacks their legitimate systems but they're behaving outside their intended boundaries so their intent was fine but the outcomes weren't from that perspective but we can't look at that and I'll look at that some three various categories unsanctioned AI that AI that nobody approved it it's running in your environment and it gets into shadow a bit unmonitored AI so we have AI that no one's
• 3:30
  [SPEAKER_01]: unpredictable AI so that gets in a bit of the point to the road but it's approved and watched but it's doing things no one anticipated whether those be from the business side or the security side so that you've got agents emerging kind of as that biggest emerging category because they're doing things on behalf of users and also rather than just a specific question to a chatbot and a specific answer now it's going and taking actions on that behalf and that's introducing even more rogue actions at scale
• 3:59
  [SPEAKER_00]: Absolutely.
• 4:00
  [SPEAKER_00]: Now, that makes it clear when we think about Rogue AI doesn't necessarily have to be something malicious, but it's going off on its own, and what are the most common ways that AI systems drift outside of intended boundaries?
• 4:11
  [SPEAKER_00]: And once an organization understands what Rogue AI looks like, where does that loss of control typically begin and who is responsible for preventing it?
• 4:20
  [SPEAKER_01]: the operating definition I like to use is it's working as a design, but not as intended.
• 4:27
  [SPEAKER_01]: And so this goes back to computer science 101, right?
• 4:30
  [SPEAKER_01]: It is, we're capturing a developer or designer designs at one way, but then it's being used for other ways, whether maliciously by bad actors or just from the software responding, different than you expect.
• 4:43
  [SPEAKER_01]: But one of the most common ways is prompt injection.
• 4:46
  [SPEAKER_01]: It's an underrated drift mechanism,
• 4:50
  [SPEAKER_01]: Support ticket, scrape web page, user message, it can redirect an agent's behavior.
• 4:55
  [SPEAKER_01]: No one touches the model, right?
• 4:56
  [SPEAKER_01]: With drift events on an AI particularly, you've got various components and several of those are out of your control.
• 5:03
  [SPEAKER_01]: Model updates may change the behavior without you changing a single thing or single code deploy.
• 5:09
  [SPEAKER_01]: If you're calling a hosted LL in the provider updates the model, your agent's behavior can shift.
• 5:15
  [SPEAKER_01]: No pool request, no change management,
• 5:18
  [SPEAKER_01]: Back to the conversation of what broke and why you've got to go a layer deeper, and that's a big way that AI systems can drift because of From the user interaction or the agent interaction to an API to a tool to an LLM.
• 5:34
  [SPEAKER_01]: There's various components in there that can all be changing and outside of your general control.
• 5:39
  [SPEAKER_00]: Let's move into the shadow world, right?
• 5:42
  [SPEAKER_00]: And shadow AI is the unsanctioned or unmonitored use of AI tools, apps, or embedded features by employees within an organization.
• 5:50
  [SPEAKER_00]: Basically, usage of unapproved AI, right?
• 5:54
  [SPEAKER_00]: It's in looking at shadow LOMs.
• 5:57
  [SPEAKER_00]: How do these things create risk even when no attacker is involved, right?
• 6:01
  [SPEAKER_00]: Let's define that.
• 6:02
  [SPEAKER_00]: And if AI drift often starts with normal business activity,
• 6:10
  [SPEAKER_01]: I'd define shadow LMs or that they are the new shadow IT, right?
• 6:15
  [SPEAKER_01]: A developer spins up an LLM endpoint in AWS or Azure or somewhere else, because the internal approval process takes weeks, if not months for various things.
• 6:25
  [SPEAKER_01]: And so typical behavior with shadow I and shadow LMs, right?
• 6:31
  [SPEAKER_01]: It's because it takes too long.
• 6:32
  [SPEAKER_01]: They have a legitimate use case on business case.
• 6:38
  [SPEAKER_01]: what they want done, and so there's no security review, no data handling policy, no logging.
• 6:43
  [SPEAKER_01]: Or, but you bring in a new third party tool with its own AI built-in, calling LLMs that you never approve.
• 6:50
  [SPEAKER_01]: Need to be able to see that, surface that, and stop it, or at least provide feedback to your vendors, right?
• 6:55
  [SPEAKER_01]: So that you understand what's going on there, and you understand the full risk picture.
• 7:00
  [SPEAKER_01]: But maybe a little bit outside of the scope of this conversation, but S-bombs, software bill materials, and AI bill materials, they're crucial to understand truly what makes up your software and understand all your risks.
• 7:11
  [SPEAKER_01]: Those are point-and-time, maybe from your vendor, but the fact that you need to be able to understand and build those, you can understand the risk and stop that as well.
• 7:21
  [SPEAKER_01]: Now, I'd ask, kind of, I kind of add one other thing.
• 7:23
  [SPEAKER_01]: Unsanctioned agents,
• 7:25
  [SPEAKER_01]: But they inherit the developer's credentials, right?
• 7:27
  [SPEAKER_01]: So developer goes in, just puts his credentials in, and now they get a broader role than they probably should out.
• 7:33
  [SPEAKER_01]: So the agent, the same person as me, or you, right?
• 7:37
  [SPEAKER_01]: Maybe in an administrative role, which is much more than it needed to actually do the task at hand.
• 7:42
  [SPEAKER_01]: And so those are a couple of the things from Shadow LM, you're really looking at.
• 7:46
  [SPEAKER_01]: One big stat that kind of comes out 72% of corporate AI tools and active use
• 7:54
  [SPEAKER_01]: not future state problem that's current state today, so we have to get that under control for sure.
• 7:59
  [SPEAKER_00]: Yeah, no doubt.
• 8:01
  [SPEAKER_00]: And it's clear already from our conversation that this is important and it's a hard problem to solve.
• 8:06
  [SPEAKER_00]: Why can an AI action look legitimate in isolation?
• 8:10
  [SPEAKER_00]: Still create serious business security or compliance risk when viewed as part of a larger sequence of actions or a workflow.
• 8:18
  [SPEAKER_00]: As these shadow systems become more embedded in their
• 8:24
  [SPEAKER_01]: One, because our tools aren't keeping up right, tools that are using signatures or specific, this is allowed, this isn't allowed, just can't keep track when you're doing chaining actions together.
• 8:35
  [SPEAKER_01]: In that case, individual actions pass every check, but the sequence could fail the audit.
• 8:39
  [SPEAKER_01]: Maybe reading a customer record is fine, summarizing it's fine, passing the summary to a third-party API, all good, right?
• 8:47
  [SPEAKER_01]: But doing all three automatically at scale without a human review step, it could be a conversation around GDPR or other things that you just don't want to have.
• 8:56
  [SPEAKER_01]: It goes back to even different parts of data and isolation or fine, but once you train those together, you can have the classified or other security events in the national security space and similar things are happening here.
• 9:07
  [SPEAKER_01]: And then by next step, Noah's on Chained Agents, right?
• 9:11
  [SPEAKER_01]: They multiply the blast radius, because rather than just a single agent doing a single thing, Agent A calls Agent B, which calls Agent C each step, looks good, authorize API calls with the end result.
• 9:25
  [SPEAKER_01]: There's a capability, no one really explicitly designed or approved.
• 9:29
  [SPEAKER_01]: They just emerge from the chain and these agents learning what they can do and how to get what they want done.
• 9:35
  [SPEAKER_01]: And so then you're a lot of times you're losing context.
• 9:39
  [SPEAKER_01]: Indian session tracing really is the type of ability that makes this sequence level analysis possible.
• 9:45
  [SPEAKER_01]: We can't believe you have to be able to trace every AI session from the initial prompt through every model call tool,
• 9:54
  [SPEAKER_01]: get a single record as otherwise you're losing that context and you're not able to reconstruct that and understand the true risk of what's going on to be able to eliminate or minimize risk and take action in a larger environment.
• 10:07
  [SPEAKER_00]: Let me make sense and I think your answer probably opens up.
• 10:11
  [SPEAKER_00]: or leads into an answer to my next question, how do APIs and integrations and connected systems amplify the impact of the seemingly legitimate actions?
• 10:21
  [SPEAKER_00]: Now, I think I could probably as an engineer, cherry pick some of the things you're probably gonna say from the last answer, but what changes once those actions begin flowing across these workflows, across APIs, applications, and interconnected systems.
• 10:36
  [SPEAKER_01]: Yeah, it goes back to, I know conversations you've had in previous weeks, right?
• 10:40
  [SPEAKER_01]: APIs really are the central nervous system of AI, right?
• 10:43
  [SPEAKER_01]: Every meaningful action or AI agent takes eventually.
• 10:48
  [SPEAKER_01]: It becomes an API call, well, that's to a database, to a SaaS tool, to a payment system, identity provider, MCB servers.
• 10:55
  [SPEAKER_01]: If you're not watching that API layer, or you're not watching the agent, and then that integration surface enormous, it's unemotored.
• 11:03
  [SPEAKER_01]: We'd powder you protect, which you don't know, modern enterprise environments have thousands if not tens of thousands of API endpoints.
• 11:11
  [SPEAKER_01]: Many of those are undocumented, they might be third party, yeah, as it might be your own APIs.
• 11:16
  [SPEAKER_01]: And so it might be endpoints that should have been deprecated a long time ago.
• 11:20
  [SPEAKER_01]: The issue now becomes even more because an AI with broad permissions, they'll find those, they'll call them, they'll be able to do what they need to do to get things done.
• 11:30
  [SPEAKER_01]: But you no longer dealing with just users or even just scripts that are dealing with specific APIs that you're dealing with agents that multiply this and it's being able to integrate AI security, API security because of this amplification effect becomes crucial.
• 11:45
  [SPEAKER_01]: A lot of folks treat these as separate problems, API gateway for API traffic, AI gateway for AI traffic.
• 11:52
  [SPEAKER_01]: separate tool for AI behavior, but AI didn't interact with all these external systems to APIs, and that's where data-exfiltration risk, typical materialized, separating the two creates a blind spot, exactly where the risk is highest, and so you've got to be able to see that full picture.
• 12:09
  [SPEAKER_00]: Right on.
• 12:09
  [SPEAKER_00]: Okay, let's switch over to leadership of CIOs and CIOs.
• 12:13
  [SPEAKER_00]: What kinds of unexpected outcomes worry these folks the most today?
• 12:17
  [SPEAKER_00]: When AI systems are operating across these
• 12:21
  [SPEAKER_00]: And as that connectivity expands, what are security and business leaders most concerned about?
• 12:26
  [SPEAKER_01]: Great question.
• 12:27
  [SPEAKER_01]: A couple of things, one that jumps out to me right away is PI or sensitive data showing up where it shouldn't, right?
• 12:34
  [SPEAKER_01]: And these have real world consequences and real world finds.
• 12:37
  [SPEAKER_01]: So in AI workflow, process a support request, routes it through a summarization step, stores the output in the log and that log contains the customer social security number.
• 12:47
  [SPEAKER_01]: No one really designed for that data path, but it happened because the model was helpful.
• 12:51
  [SPEAKER_01]: They got what it needed, but it now logged that information where it shouldn't have.
• 12:56
  [SPEAKER_01]: Now, I think another big thing is, yeah, I can't explain what it did problem.
• 13:01
  [SPEAKER_01]: And so that can be from the CISO's hat or from the CIO or business's hat.
• 13:06
  [SPEAKER_01]: A CISO can generally reconstruct the human attacker's path.
• 13:10
  [SPEAKER_01]: Reconstructing the AI agents decision tree across a multi-step workflow with external data inputs.
• 13:17
  [SPEAKER_01]: It's generally, it's just a hard thing to do, right?
• 13:20
  [SPEAKER_01]: regulators, board members, incident responders, they all want the story, but today a lot of organizations can't tell it.
• 13:27
  [SPEAKER_01]: And any other kind of interesting story is unexpected answers or behaviors.
• 13:32
  [SPEAKER_01]: We actually have an ongoing conversation with the potential customer.
• 13:36
  [SPEAKER_01]: They built their own chatbot and going to change some details here to not reveal anything.
• 13:41
  [SPEAKER_01]: But you go ask this chatbot a question for instance.
• 13:44
  [SPEAKER_01]: So what do I feed to my new puppy?
• 13:46
  [SPEAKER_01]: Right?
• 13:46
  [SPEAKER_01]: 99 times out of 100 or 99 times out of 1,000 responds with the skew for puppy food, a link you can buy it straight from their website.
• 13:55
  [SPEAKER_01]: However, one time out of that, it actually responds completely randomly.
• 14:00
  [SPEAKER_01]: And not only randomly, but in a really bad way to potentially feed your puppy something that's poisonous.
• 14:06
  [SPEAKER_01]: So that can't happen.
• 14:07
  [SPEAKER_01]: We have to understand what those responses are and make sure they're accurate 100% of the time because otherwise
• 14:16
  [SPEAKER_01]: So, those are a couple of the two big things know about unexpected outcomes, but from a cyber side as well as the business and liability side that jump out to me.
• 14:25
  [SPEAKER_01]: And then kind of a third is just that reputational risk from out, but it's not just access.
• 14:30
  [SPEAKER_01]: A.S. system that publishes incorrect to a biased content at scale or gives inappropriate recommendations to customers like I talked about.
• 14:37
  [SPEAKER_01]: It's a brand and legal risk.
• 14:39
  [SPEAKER_01]: It doesn't fit neatly into traditional security frameworks.
• 14:42
  [SPEAKER_00]: I appreciate you walking through that.
• 14:46
  [SPEAKER_00]: What does meaningful oversight actually look like when AI systems can act at machine speed?
• 14:51
  [SPEAKER_00]: And that can we talk about interconnected systems and impact there.
• 14:55
  [SPEAKER_00]: That can really amplify the effects of some of these actions.
• 14:59
  [SPEAKER_00]: So what does that meaningful oversight look like?
• 15:02
  [SPEAKER_01]: From a security practitioner, your policy alone is not oversight.
• 15:05
  [SPEAKER_01]: We've always said that, right?
• 15:06
  [SPEAKER_01]: Paperwork doesn't make you more secure.
• 15:08
  [SPEAKER_01]: Policy document does not stop an agent mid-call, right?
• 15:11
  [SPEAKER_01]: So real oversight fires actual runtime enforcement, the ability to inspect, block, or write limit that AI generated API traffic in real time.
• 15:20
  [SPEAKER_01]: That closed loop model, really to no see, stop, and prove.
• 15:25
  [SPEAKER_01]: You need to know what the AS systems are running and what they've connected to.
• 15:29
  [SPEAKER_01]: You need to see what they're doing in real time.
• 15:31
  [SPEAKER_01]: You need to be able to stop the behavior before the consequences compound.
• 15:35
  [SPEAKER_01]: But increasingly, you need to be able to prove to auditors that you did this, right?
• 15:39
  [SPEAKER_01]: Most organizations have no, at least partially, and they've got some logs, but see stop and prove definitely are the gaps.
• 15:47
  [SPEAKER_01]: And then humans in loop do matter, right?
• 15:50
  [SPEAKER_01]: But they need to be at the right point.
• 15:51
  [SPEAKER_01]: You can't put a human in the loop for every API call.
• 15:54
  [SPEAKER_01]: You put humans at decision gates for high risk actions, boundary crossing transactions.
• 15:59
  [SPEAKER_01]: But then the system has to surface those moments automatically, right?
• 16:03
  [SPEAKER_01]: So,
• 16:03
  [SPEAKER_01]: as you're looking at tooling and other things, those key aspects need to bubble up so that humans can take action quickly, understand the context around that, and then the tool has to be able to enforce these policies, like you said, at machine speed.
• 16:19
  [SPEAKER_00]: That makes sense, and enforcing the policies as quick as the actions are being done.
• 16:24
  [SPEAKER_00]: That seems clear, that would be a meaningful, that would be meaningful oversight.
• 16:28
  [SPEAKER_00]: Okay, how should organizations distinguish between the experimentation they want to encourage,
• 16:34
  [SPEAKER_00]: In the unmanaged AI behavior that they need to control, one challenge is balancing governance with innovation.
• 16:40
  [SPEAKER_00]: And as an engineer as a startup founder myself, that I, that holds true day-to-day, how do organizations avoid slowing down AI adoption while still maintaining control?
• 16:51
  [SPEAKER_01]: The security organization can't put the no in an innovation, right?
• 16:54
  [SPEAKER_01]: We've heard that many times, right?
• 16:57
  [SPEAKER_01]: So the answer is not slow everything down.
• 16:59
  [SPEAKER_01]: Organizations that over restrict AI experimentation, one you'll lose your best engineers, you'll lose your best people to competitors that don't.
• 17:07
  [SPEAKER_01]: As well as the business is asking all of these quarterly earnings calls and other things are asking specifically what the AI strategy is in plan.
• 17:15
  [SPEAKER_01]: So we have to be able to support that, but do it in a secure way.
• 17:18
  [SPEAKER_01]: So I think the first thing is, hey, define the sandbox clearly.
• 17:22
  [SPEAKER_01]: Make it easy to use, no.
• 17:23
  [SPEAKER_01]: If you can go out, you can innovate, you can test, but do it truly with the Dev Environment, isolated credentials, scope, API access, no production data.
• 17:32
  [SPEAKER_01]: logging enabled.
• 17:33
  [SPEAKER_01]: So you can understand that you can experiment quickly.
• 17:36
  [SPEAKER_01]: And that sandbox needs to be a first class experience, not just an afterthought.
• 17:41
  [SPEAKER_01]: And it needs to be usable, right?
• 17:43
  [SPEAKER_01]: We've all dealt with Dev environments that didn't mirror production at all and caused all sorts of issues once it went to prod.
• 17:50
  [SPEAKER_01]: Being able to do that to be able to support continuous AIS bomb going forward here as well so that in those environments you can understand what
• 18:02
  [SPEAKER_01]: as well and then create a fast path to production right shadow AI grows when that official path is slow So your point is you can't slow it down people are going to get around it one way or the other right either They're going to do their own thing outside your boundaries or they're going to leave so a lightweight AI system intake process This security room is data classification runtime monitoring the completes in days not months or years in some cases removes the incentive to go around it
• 18:29
  [SPEAKER_01]: And then I think the last thing is you're tooling being able to easily enforce new new sandboxes or new environments that are stood up is important too, right?
• 18:40
  [SPEAKER_01]: So rather than having to go from your security team or your developers to the infrastructure people and all it, it'd be able to just click a button from some of these AI governance and observability tools.
• 18:54
  [SPEAKER_01]: do the enforcement monitoring and enforcement in these new environments with the click of a button in seconds rather than like as weeks or months also is important so you can get that visibility of the enforcement as you see new things spin up.
• 19:08
  [SPEAKER_00]: Okay, I'm tracking with that.
• 19:09
  [SPEAKER_00]: Okay, Craig, there's one more question I've got, and we know that many organizations can detect risky AI behavior.
• 19:15
  [SPEAKER_00]: That's a fact, but if they can't stop it in real time, what critical gap still remains?
• 19:20
  [SPEAKER_00]: Even with these governance programs in place, many orgs are still operating reactively.
• 19:25
  [SPEAKER_00]: Kind of close out our conversation, what's the key difference between detecting AI risk and actually controlling it?
• 19:31
  [SPEAKER_01]: as a security professional or as the CSA.
• 19:33
  [SPEAKER_01]: You don't want just another dashboard to tell you how bad you're doing, right?
• 19:37
  [SPEAKER_01]: And detection without prevention is just documentation of damage, right?
• 19:41
  [SPEAKER_01]: Knowing an agent exfiltrated data after the fact doesn't elinex filtrate it.
• 19:46
  [SPEAKER_01]: It doesn't keep you from finds and other regulations.
• 19:50
  [SPEAKER_01]: Bray our systems operating at machine speed, but the gap between that action taken and the action detected can mean thousands of API calls and gigabytes of data before you're ever alerted to that.
• 20:02
  [SPEAKER_01]: And also, at machine speed, looking at logs and some of your traditional sims just aren't able to keep up with AI speed actions, these metrics, the traditional metrics, they just look even catastrophic.
• 20:15
  [SPEAKER_01]: So one minute response time is just way too slow.
• 20:18
  [SPEAKER_01]: of an agent made 50,000 API calls in that minute.
• 20:21
  [SPEAKER_01]: And regulators even are moving toward real-time accountability, right?
• 20:24
  [SPEAKER_01]: So you've got the EUAI Act, which is coming fast upon us.
• 20:29
  [SPEAKER_01]: And the SAI are a math, emerging SEC regulation.
• 20:33
  [SPEAKER_01]: It all signal that we detected eventually just won't be sufficient.
• 20:38
  [SPEAKER_01]: So the expectation is shifting towards, like, demonstrated ability to prevent, not just to discover.
• 20:43
  [SPEAKER_01]: And so that's what definitely we are looking at.
• 20:46
  [SPEAKER_01]: How do we close this gap?
• 20:47
  [SPEAKER_01]: Most organizations have that SAM, the AAPM, the AAAPI gateways.
• 20:51
  [SPEAKER_01]: But none of these tools see inside a session and stitch all those pieces together.
• 20:56
  [SPEAKER_01]: They just see headers, they see latency, they see logs.
• 20:59
  [SPEAKER_01]: But they don't see the prompt, the payload, the data return.
• 21:02
  [SPEAKER_01]: We're looking to be able to see all of that at the kernel level and act on it in line at machine speed.
• 21:09
  [SPEAKER_00]: Oh, that just makes so much sense and thinking about reactive versus control and processing that in real time just really brings it to light.
• 21:17
  [SPEAKER_00]: How important how fast this moves.
• 21:19
  [SPEAKER_00]: So Craig, I really appreciate you being on the show today.
• 21:22
  [SPEAKER_00]: It's clear that Rogei doesn't necessarily mean malicious AI.
• 21:25
  [SPEAKER_00]: Actions can appear as legitimate business actions and are often difficult to determine.
• 21:30
  [SPEAKER_00]: and the chaining of these events through interconnected systems, obviously, and clearly, through your answers amplifies the impact quickly.
• 21:37
  [SPEAKER_00]: You have to bring the speed of governments to be as fast as the speed of action.
• 21:41
  [SPEAKER_00]: A business must keep that balance between control and innovation, but to control AI risk, businesses have to move to real-time action to these issues in order to prevent the damage and to get out of that reactive mode.
• 21:52
  [SPEAKER_00]: So I really appreciate you explaining all this sharing your perspective and being on a showcrack.
• 22:01
  [SPEAKER_00]: As you can see from Craig's answers, Rogue AI is something to take seriously.
• 22:06
  [SPEAKER_00]: Even if it's not malicious, AI is powerful.
• 22:09
  [SPEAKER_00]: And businesses need to take stock of how people are using this technology.
• 22:13
  [SPEAKER_00]: With a balance of ensuring open posture towards innovation.
• 22:18
  [SPEAKER_00]: If you'd like to learn more about Walarm, you can visit Walarm.com.
• 22:22
  [SPEAKER_00]: That's W-A-L-L-A-R-M.com.
• 22:28
  [SPEAKER_00]: And thanks again for listening.