The Security Strategist

Imagine a customer logged in to your online portal. Their token is valid, and so is their session. Then one number at the end of an API call changes, and the response comes back with a different customer's account. The WAF sees a well-formed request from an authenticated user. The schema check passes. Nothing in the log says attack.
That is an abuse of business logic; cybersecurity analyst Jonathan Care refers to it as a series of "perfectly valid calls in a sequence you never anticipated, doing something you never intended."
In this episode of The Security Strategist podcast, Jonathan Care, lead analyst at KuppingerCole, sat down with Uri Dorot, Senior Product Marketing Manager at Radware, to talk about possibilities and impossibilities of API tooling, how detection can tell the difference between an attacker and an unusual customer, and the steps a CISO can take when working with a limited budget.
Also Watch: Can Runtime Security Keep Autonomous AI Under Control?
Key Takeaways
Majority of enterprises fail to detect more than 90% of their APIs.
Developers are familiar with Shadow APIs, whereas zombie APIs are not.
Endpoint tools can be located cheaply via AI tools and crawlers.
Attacks based on business logic make use of valid calls; schema checks can’t detect them.
Business logic attacks use valid calls, so schema checks miss them.
Response inspection catches reused tokens and PII leaving.
Identity alone is insufficient; behaviour and context also matter.
A gateway does not replace an API security platform.
Every discovered API needs a named owner.

Chapters
00:01 Business logic abuse and the 90% figure
05:34 Shadow, zombie and deprecated APIs
11:18 Telling abuse from legitimate use
22:20 AI agents and behavioural detection
42:35 Budget and ownership

Connect with Jonathan Care on LinkedIn
Connect with Uri Dorot on LinkedIn
Explore more episodes on The Security Strategist podcast
#APISecurity #Cybersecurity #Radware #TechPodcast #CloudSecurity #Infosec #ArtificialIntelligence #businesslogic #APIGateway #AITraffic #AIBotTraffic #GuardrailsforAI

In the recent episode of The Security Strategist podcast, host Shubhangi Dua, podcast host and producer at EM360Tech, sits down with Chenxi Wang, Managing General Partner at Rain Capital, a cybersecurity veteran of more than two decades, a Fortune 500 board member and a VentureBeat Women in AI Award winner. They talk about self-improving AI agents (SIA) and their more advanced cousin, recursive self-improving agents (RSIA), from what they are, why they're suddenly dominating research conferences, and why most enterprises, especially regulated ones, aren't remotely ready to run them without a human in the loop.
Key Takeaways
RSIA updates the mechanism that improves the agent, not just the agent
Sandbox "no" feedback pushes agents toward workarounds, not compliance
Governance depends on evidence chains and observability, not approval gates
Self-improving agents haven't reached production at scale
Regulated industries aren't ready for zero-human-in-the-loop agents
C-suites should focus on adoption pressure and provable policy enforcement

Chapters
00:00 Introduction to Self-Improving AI Agents and Security Risks
02:30 What Are Self-Improving AI Agents and Their Current State
05:15 Challenges and Risks of Recursive Self-Improving AI
08:38 Real-World Use Cases and Deployment in Enterprises
11:08 Security and Governance Challenges of Autonomous AI
15:50 Case Study: Hugging Face Cyber Attack and AI Behavior
21:25 Future Outlook and Risks of Self-Improving AI in Business
22:12 Key Takeaways for C-Suite Leaders

What happens when the walls of your organisation can no longer keep your data safe? AI, remote work, and fast-moving data are changing how organisations operate, and the traditional perimeter model is becoming harder to maintain. In this episode of the Security Strategist Podcast, host Chris Steffen sits down with Dr Bill Anderson of Mattermost and JP Ayyappan, Director of Product Management at Virtru, to explore why the future of security isn't about stronger walls. It's about protecting the data itself.
Zero Trust Beyond the Network
Anderson, who trained as a cryptographer, says this blind spot has been around for decades. Organisations built networks like fortresses, assuming that anyone inside could be trusted. But that approach no longer reflects how people work. Employees use phones, home networks and third-party platforms every day, meaning the traditional security perimeter is no longer enough. Major breaches have shown how risky that assumption can be.
This is where zero trust comes in. But Anderson argues that many organisations still apply it mainly to networks and devices, rather than to the data moving through them. Collaboration tools have made this gap even clearer. People are creating and sharing sensitive information every day through meetings, chats and shared documents, often without a way to identify and protect that data as soon as it is created.
How AI Changes Data Classification
The conversation then turned to one of the biggest challenges facing security teams: AI can combine information in ways that are difficult to predict. Anderson described how a series of seemingly harmless questions about flight paths, weapons ranges, and timing could be combined by an AI system to produce sensitive information, even if no one set out to create it.
Steffen gave a similar example. A simple first prompt can lead to a series of follow-up questions, with each response shaping the next. By the third or fourth exchange, the AI could produce highly sensitive information without a clear record of how it was created. This creates a problem for traditional data classification. Rules designed for static documents are harder to apply when information is generated and combined in real time.
Ayyappan pointed out that AI can also help address this problem. It can be trained to classify and tag information as new context emerges, but only if organisations already have a clear and consistent tagging structure.
Security That Protects the Data
Rather than relying on network access to determine who can be trusted, Virtru's approach applies permissions directly to the data through an open framework called the Trusted Data Format. Ayyappan explained that files can carry their own access rules, allowing organisations to control who can access them regardless of the network or device being used. This approach keeps protection with the data, even when a file is shared outside the organisation. It can also make it easier to give external partners or emergency teams access to specific information without giving them access to the wider network.
AI Agents Need Access Controls Too
Both guests agreed that AI agents, integrations and plugins need to be treated as identities within an organisation's access control model. Anderson explained that Mattermost applies the same user, resource and action controls to AI agents as it does to people. This allows organisations to control what each AI system can access.
Ayyappan added that two executives using the same AI agent and accessing the same data could receive different answers based on their individual permissions. This allows organisations to use AI without giving every user or system access to all available data. For security teams, both experts recommended starting with clear limits on which AI systems different groups can access. As organisations develop clearer classification rules, more of these controls can be automated.
Ayyappan also stressed that data privacy and protection need to be considered from the start. Once sensitive information has been exposed through an AI workflow, fixing the problem afterwards may be too late. The shift towards AI means organisations need to rethink how they classify, protect and control data. Instead of relying only on network security, organisations need controls that stay with the data wherever it goes. Listen to the full episode and learn how Mattermost and Virtru are helping organisations take a data-first approach to security. Visit mattermost.com or virtru.com to learn more, and follow Dr Bill Anderson and JP Ayyappan on LinkedIn.
Takeaways
Rethinking zero trust by putting security closer to data.
The role of AI in enhancing data security and decision support.
Challenges of data classification and access control in AI environments.
The concept of data self-description and attribute-based access control.
Treating AI agents as quasi-human entities in security models.
The importance of disciplined data tagging and classification.
Risks of data spillage and the need for proactive safeguards.
Evolving from perimeter-based to a data-centric security model.

Chapters
00:00 Introduction to data security challenges in the AI era
01:59 Bill Anderson's background and experience in security and cryptography
03:53 The role of AI in security and decision-making in defence and intelligence
07:00 Breakdown of traditional security models and the shift to data-centric security
09:53 Zero trust principles and moving beyond network perimeter
12:58 The importance of human decision-making in security and AI integration
16:46 Data sharing, control, and the concept of self-describing data
22:00 AI's influence on data classification and the risks of data leakage
25:54 Treating AI agents as resources with their own identities
30:12 Best practices for organisations embracing AI and collaboration

Your engineering team assigns an AI agent a seemingly routine overnight task with limited human oversight. By morning, the agent has moved beyond the task’s intended scope.
The AI agent spots a weakness in the sandboxed infrastructure. This weakness gives the agent a path to data it is not permitted to access.
But your Endpoint Detection and Response (EDR) dashboard doesn’t flag the problem. To the tools in the environment, the AI agent's activity looks like routine processing. That visibility gap is central to the broader question raised by a July 2026 incident, when OpenAI models circumvented sandbox controls and accessed evaluation data hosted on Hugging Face.
In this episode of The Security Strategist podcast, host Richard Stiennon, Chief Research Analyst at IT-Harvest, is joined by Brandon Dixon, Co-Founder and CTO of Ent. Together, they unpack how OpenAI models, operating inside an evaluation sandbox with reduced safeguards, circumvented the controls designed to contain them. The conversation moves from that incident into a much bigger question: as AI agents start acting directly on laptops, servers, and enterprise software, what does the control point of the future actually look like?
Key Takeaways
OpenAI’s Hugging Face incident shows how agents can cross intended boundaries even when individual actions appear permitted.
EDR can observe processes and system activity, but it does not inherently understand the context or intent behind them.
Agentic tools, remote-control features, ClickFix, FileFix, and malvertising can make risky activity look like normal work.
Prompts and tool calls can now provide clues to an agent’s stated objective, but behaviour and context are still needed to determine risk.
Built-in agent guardrails provide an important first layer of protection, but they are not a complete security control.
For certain workloads, local AI can offer meaningful advantages in cost, speed, privacy, and data sovereignty.
Some enterprises are reconsidering endpoint compute and local GPU investments as the economics and risks of cloud-only AI become clearer.
Isolated-tenant design, learned at Microsoft, now shapes Ent's architecture.
The opportunity is to rebuild endpoint security around context, intent, and real-time prevention.

Chapters
00:00 Introduction to AI's impact on cybersecurity
00:27 Brandon Dixon introduces Ent and recent AI incidents
01:09 What happened with Hugging Face and AI security risks
02:19 AI models, guardrails, and the risk of AI escaping sandbox environments
03:28 Deciphering AI intent through prompts and behaviour analysis
04:45 Monitoring AI activity and understanding agent behaviour
05:52 The future of AI and human roles in security
07:16 Limitations of current endpoint security solutions
09:15 The resurgence of endpoint devices and local compute power
13:46 Economic and practical reasons for local AI processing
15:01 Leveraging latent endpoint compute for security and AI tasks
16:12 The architecture shift in cybersecurity and point solutions
17:37 The debate over cloud versus on-premises security infrastructure
20:14 The role of hardware and local compute in AI security
22:36 Limitations and use cases for current AI security solutions
23:36 Future security architecture and the role of AI in security design
25:04 Key takeaways for security leaders and the importance of rethinking architecture
26:23 Brandon Dixon on building a new security architecture for the future

Request a demo to learn more about what Ent is building and how its intent-aware workspace security platform helps security teams understand human and AI-driven activity at the endpoint, recognise risky behaviour that traditional tools may miss, and intervene before it becomes an incident.
#AIsecurity #EndpointSecurity #Cybersecurity #AIagents #TheSecurityStrategist

Every CISO’s inbox is hot with this email at least once a year: the audit is four months away, and it's time to stop everything.
As a result, progress comes to a halt, and a person then spends two weeks logging into 30 different consoles, taking screenshots in order to show that MFA has been turned on. After the audit is over, the evidence becomes invalid, and exactly twelve months later the same frantic situation begins all over again.
That is precisely the kind of situation that Jonathan Schipp, Senior Director of Product Management at Rapid7, aims to end, and it is the focus of the most recent episode of The Security Strategist podcast.
In this episode, host Richard Stiennon, Chief Research Analyst at IT-Harvest, is joined by Schipp to talk about the reason why governance, risk and compliance (GRC) is moving from being a yearly rush to becoming a continuous, API-driven element of security operations. They also address why AI is causing this change to happen more quickly than most GRC teams can keep up with.
“Compliance turns into something you have to put everything else aside for,” Schipp tells Stiennon. “When an enterprise carries out its SOC 2 audit, most of them are not well prepared; it disrupts the business flow.”
Key Takeaways
Rapid7 launched CyberGRC to connect live security telemetry to compliance evidence
Continuous monitoring replaces manual screenshot evidence with API-based checks
SOC 2 and ISO 27001 still require annual audits; continuous monitoring closes the gaps between them
Roughly 1% of discovered vulnerabilities are actually exploitable, per Schipp
AI models are finding more vulnerabilities mainly by scanning source code faster
Automated exploitation attempts generate high log volume, making them detectable
Rapid7's GRC platform supports ISO/IEC 42001 and the NIST AI RMF
Rapid7 serves roughly 11,000 customers, many now requesting AI-specific controls
GRC's role is to move the business through AI risk, not block AI adoption
Boards typically have audit and risk committees but no dedicated security committee
Vulnerability risk should be classified by business impact, not treated as uniform
Basic controls — MFA, asset inventory, patching exploitable exposures — stop most attacks, AI-driven or not
Chapters
00:00 Introduction and guest overview
02:07 Incentives for security maturity
03:06 European and US regulatory developments
03:50 Connecting security telemetry with GRC
04:16 Continuous compliance and audit cycles
05:16 The importance of continuous control monitoring
06:20 Using APIs for evidence collection
07:16 Managing vulnerabilities and exceptions
08:18 Classifying vulnerabilities and risk
09:15 AI in security and human accountability
09:53 The reality of AI discovering vulnerabilities
11:08 Managing noise and false positives in AI detection
12:10 Integrating AI systems for proactive security
13:26 Preemptive security and threat intelligence
14:17 Risks of AI in attack scenarios
15:16 AI misuse and governance challenges
16:23 Balancing AI adoption with controls
17:22 The importance of basic security controls
18:22 Key takeaways for CISOs and security leaders
20:19 Closing remarks and next steps
For further information, visit rapid7.com and em360tech.com.