261 episodes
- Black Friday and peak holiday shopping is looming around the corner. Imagine this scenario: The retail enterprise’s fraud team is on alert and going through chargeback cases raised by its customers. Many shoppers seemed to have asked a personal AI agent assistant, something like Meta’s Muse, to find the best phone under $1,000 on the retailer’s website and buy a single phone.
Many of these customers asked for one, not four. For some reason, hidden page text instructed customers’ AI agents to ignore tasks and fill carts. The AI agents left logs showing valid sessions and payments.
In this episode of The Security Strategist podcast, host Shubhangi Dua, Podcast Producer and B2B Tech Journalist at EM360Tech, speaks to Dhanesh Ramachandran, Product Marketing Manager at Radware. They cover the rise of AI agent traffic, the risks with AI agent activity on websites, why banks are wary of unapproved AI agents, and how agent trust management helps CISOs enable trusted agent engagement before the holiday season.
“Now it’s like anybody can ask an agent to do something malicious for them.”
Key takeaways:
• Knowing an agent's identity doesn't mean it can be trusted
• OWASP ranks Agent Goal Hijack as a top AI agent risk
• 66% of organisations rank unverifiable agent identity as their top AI agent risk
• Bad bots made up nearly 43% of last holiday season's e-commerce traffic, against 46% for humans
Read the full recap: https://em360tech.com/podcasts/friend-or-foe-which-ai-agents-should-your-website-let
Learn more: https://www.radware.com
Follow EM360Tech on X: https://x.com/EM360Tech
Follow EM360Tech on LinkedIn: https://www.linkedin.com/company/em360tech
Website: https://em360tech.com - AI is changing how software is developed, creating new challenges for security teams tasked with managing vulnerabilities and securing increasingly complex software supply chains. In this episode of the Security Strategist Podcast, host Richard Stiennon speaks with Anthony Barkley, Chief Strategy Officer at Veracode, about the implications of AI-driven software development for application security and vulnerability management.
Drawing on more than 30 years of cybersecurity experience, Barkley discusses why traditional approaches to vulnerability management are no longer sufficient as AI agents, traditional developers and citizen developers contribute to software development. He also explains Veracode’s move from a broad marketplace towards a vetted partner ecosystem.
Why AI Software Supply Chain Security is a Priority
For years, the software supply chain meant open-source libraries and third-party code. Barkley states that definition is now far too narrow. Agentic development adds AI agents, foundation and private models, Model Context Protocol (MCP) services, and a growing set of development tools. Each is a new place where risk can ultimately enter.
“I don’t personally believe we ever had a problem finding enough issues,” Barkley says. Security teams have always had plenty of security debt. The real problem is deciding which findings are exploitable and fixing them without breaking the application.
Stiennon adds that finding 140,000 vulnerabilities and turning them into 140,000 tickets helps no one. Barkley agrees that a human-in-the-loop approach to every fix is not sustainable. For him, the biggest challenge is understanding what goes into your code and its provenance, not just how fast you can write it. His longer-term goal is ambitious: “I want the models to not have problems.” Frontier Labs will build the base models, he says, but reducing vulnerabilities at the source will take partners working closely with each company’s own standards, processes, and code.
Veracode’s Ecosystem Strategy
Customers told Veracode that no single vendor can build every solution they need. They also described a flood of venture-backed startups, with 20, 40, or even 60 vendors claiming to solve the same problem in each category. Even after choosing one, they still faced procurement, security reviews, legal terms, and financial checks.
Veracode’s answer is to move from a marketplace to an ecosystem. While a marketplace offers customers a range of options, an ecosystem provides a curated shortlist of trusted vendors the company is prepared to stand behind
The first partner is DryRun Security. The partnership combines traditional deterministic scanning with AI-based probabilistic scanning, then helps customers with reachability, exploitability, and remediation. Barkley reports six proofs of concept so far, with two customers already moving forward with deployment. Veracode is evaluating five more vendors, though not all will join.
Barkley’s vetting criteria are:
Customer-driven need: Start with the gaps customers actually describe.
Durable technology: Look for real architecture, not “just some fancy UI on a bunch of prompts.”
Enterprise readiness: Check scale, integrations, and support for traditional developers, agentic workflows, and citizen developers.
Workable licensing: Make buying easy as the industry moves beyond per-seat pricing.
His advice for startups hoping to join is to get your shared customers to make the introduction.
Assure Loop for Secure AI Software Development
Barkley’s central framework is a continuous security loop with four stages, which are:
Govern: Gain visibility into the environment where code is created, whether through agent hooks, deterministic scaffolding, gateways, or a combination, without stifling innovation.
Guide: Keep developers, AI agents, and citizen developers within corporate standards using application specifications, skills files, and secure-by-design guidance.
Verify: Go beyond finding flaws. Understand the code’s context within the broader application so a fix doesn’t cause cascading breakage, which Barkley says has long been a problem with open-source library fixes.
Assure: Collect evidence at every step, run regression tests against the original specification, and confirm software is safe before it reaches production.
Adoption follows a crawl-walk-run path. Humans review checks at first, then organisations automate more as trust grows. Eventually the human role becomes an audit rather than a bottleneck.
The most important part is the feedback. If teams repeatedly generate the same kinds of vulnerabilities from certain languages, packages, or tools, that data should go back to the start of development. Over time, the flywheel prevents vulnerabilities instead of chasing them. Barkley also stresses that large enterprises will live with traditional code for years, so security has to cover legacy and AI-driven development together.
What Security Leaders Need to Know
Map your AI software supply chain, including agents, models, MCP services, tools, and code provenance.
Pair vulnerability detection with prioritisation, reachability, and validated fixes.
Build visibility and guidance for every kind of builder in your organisation.
Use security data to stop recurring vulnerabilities at the source.
For more information on Veracode’s approach to application security, visit its website. Alternatively, follow Anthony Barkley on LinkedIn.
Takeaways
No single vendor can deliver every solution customers need.
A connected ecosystem brings complementary technologies together.
A marketplace offers options; an ecosystem provides a trusted shortlist of solutions.
Customer feedback should shape priorities and identify the biggest gaps.
AI model reliability, visibility and governance must be priorities.
AI agents, traditional developers and citizen developers must operate within clear guidelines.
Continuous monitoring and verification are essential to managing AI risk.
Human oversight is shifting from direct involvement towards auditing and validating AI decisions.
Chapters
00:00 Why AI is reshaping software security
02:14 From marketplace to a trusted partner ecosystem
07:01 Dry Run Security and combining scanning approaches
09:27 How Veracode evaluates partners
14:36 Why vulnerability management is becoming urgent
16:29 Agents, models, and MCP broaden supply-chain risk
20:08 Why more findings can mean more ticket overload
21:37 The continuous loop: govern and guide
24:28 Verify fixes, then assure software with evidence
27:17 Feeding lessons back to prevent vulnerabilities - A quarterly review declares VMware migration a success. The licence bill is down, the final cluster moved on time, and the programme lead is gaining commendations. Then along comes the auditor to look at the security configuration of the new platform and discovers 15 years' worth of exceptions copied over line for line. It seems that none of them has been looked at by the security team at all. The security team was only brought in to the project after the hypervisor had already been selected. Nothing has overspent, nothing has failed; the old risk has simply been relocated.
In this episode of The Security Strategist podcast, host Alejandro Leal and Analyst at KuppingerCole speaks to Sam Marland, Senior Manager and Virtualisation Sales Leader for EMEA at Red Hat, about virtualisation and what happens to security when an enterprise moves away from its virtualisation platform.
Cost is typically the reason for such a stray. The risk that Marland emphasises in the conversation with Leal is who is in the room when the new platform is selected and who then takes on the outcome.
As head of virtualisation sales at the world's leading provider of enterprise open-source software solutions, Marland also puts up a compelling case for OpenShift. Red Hat OpenShift is an enterprise-ready, Kubernetes-based application platform used to build, modernise, deploy, and scale containerised and virtualised applications across hybrid clouds, public clouds, and edge environments.
“They look at disaster recovery, high availability, and resilience. All those key topics come up very early in the decision lifecycle. Security less so,” Marland says, alluding to individuals on the lookout for a virtualisation platform.
Also Watch: Can Open Source Ensure AI Works For Everyone, Not Just The Largest Enterprises?
Episode page: https://em360tech.com/podcasts/does-open-source-reduce-virtualisation-vendor-lock
Red Hat: https://www.redhat.com
Red Hat on the 2026 Gartner Magic Quadrant: https://www.redhat.com/en/resources/gartner-magic-quadrant-server-virtualization-analyst-report
EM360Tech: https://em360tech.com
More B2B tech podcasts: https://em360tech.com/podcasts
Follow EM360Tech on LinkedIn: htVirtualisationdin.com/company/em360
Follow EM360Tech on X: https://x.com/EM360Tech @enterprisemanagement360
Follow Red Hat YouTube: @redhat
Follow Red Hat LinkedIn: https://www.linkedin.com/company/red-hat/
Watch more from The Security Strategist Podcast: https://youtube.com/playlist?list=PLXoSlBGE35NooDaiZh9e1OtBCEpUfLfZ3&si=mWlU_se3Wfn9QGIv
#VMwareAlternatives #OpenSource #Virtualization #CISO #EM360Tech #RedHat
virtualisation, open source, vendor lock-in, VMware alternatives, VMware migration, Gartner Magic Quadrant, Red Hat, OpenShift Virtualization, cybersecurity, CISO, hybrid cloud, digital sovereignty, The Security Strategist - When a critical PHP vulnerability emerged last week, Richard Stiennon moved quickly to check every web property he manages. The host of the Security Strategist Podcast had been fortunate as he had recently moved away from WordPress, while the one site he still manages for someone else had automatic PHP updates enabled. But the incident highlighted a much bigger challenge for organisations responsible for thousands of third-party relationships.
Now imagine having to assess that level of exposure across 10,000 suppliers. For Sean Cronin, CEO of ProcessUnity, this is the reality facing third-party risk teams. Annual questionnaires and periodic assessments cannot keep pace with vulnerabilities that emerge, supplier relationships that change and risks that extend deep into supply chains. As Cronin suggests, organisations need to start thinking about third-party risk as a live signal rather than a periodic exercise.
In this episode, Stiennon speaks with Cronin, a risk management veteran of more than 25 years, about how continuous monitoring, automation and AI are changing supplier risk assessment. They discuss how to verify actual exposure, uncover fourth- and fifth-party dependencies, cut through alert noise, and pair automated intelligence with human judgement.
Third-Party Risk Management Has Outgrown Paperwork
Cronin has spent more than 25 years in risk management, in the field since before “governance, risk and compliance” was a recognised term. He remembers when banks and other heavily regulated firms employed hundreds of assessors who travelled to suppliers, inspected premises and worked through stacks of paperwork. Spreadsheets and software followed, but the underlying problem has only grown.
“The ecosystems that our clients are powered by and working with and depend upon are growing at a rate faster than the employees that can staff up and assess them,” he says. The task has changed, in his words, “from a paperwork problem to a resilience challenge and opportunity”.
AI Cyber Threats Are Speeding Up Vulnerabilities
Part of the pressure comes from the other side. Cronin says criminals’ adoption of AI has changed how critical vulnerabilities are. Teams once reacted to the occasional major flaw by working out who was affected. Now new ones arrive daily, sometimes several times a day.
Speed is the answer. If a company can quickly establish that 10 of its 15,000 vendors are exposed, it can ask those ten whether they have mitigated the problem and set the rest aside. Cronin says the old just-in-time approach no longer works. “We have to be dealing in real time.”
Vendor Vulnerabilities Hit 58% of Ecosystems
Cronin says 58 per cent of the vendor ecosystem across ProcessUnity’s client base was affected by vulnerabilities in two weeks, and the figure rose once the PHP flaw was added. He admits he did not believe it at first. Being affected is not the same as being compromised, but the burden of proof still falls on the risk professional. “Verify to me that they’re not,” Cronin says, “and then I can put them into the good bucket.” Without automation and workflow, he warns, “we’re literally chasing ghosts”.
ProcessUnity pulls together external scans, financial, firmographic and technographic data to show what a supplier looks like to an outsider, then pairs it with a controls-based risk index that reveals how well the supplier manages risk internally. The aim, Cronin stresses, is to help suppliers improve, not merely to rank them. “It’s about making the ecosystem safer for all of us.”
Supplier Risk Questionnaires
Anyone who has completed a supplier questionnaire will recognise Cronin’s next point. He says some clients now send questionnaires of 300 questions or more, with branching logic running to 600. His advice to suppliers is blunt: “Stop filling out questionnaires.” Instead, he says, secure automation can pre-populate answers from documents a supplier has already provided. Risk teams can then check those answers against external data and ask for evidence only where something looks wrong. The aim is “fewer questions and better questions”. The test is no longer whether a vendor returned its form but whether the two sides have talked about the risks that matter.
Human Oversight in AI Risk Assessment
None of this, Cronin insists, means handing judgement to machines. “A human in the loop is a critical part of our conversation with clients.” AI can handle the routine reading and clear lower-tier suppliers quickly. That leaves risk managers to dig into critical vendors and to spot those that looked moderate-risk on paper but could cause real harm.
The exposure also extends past direct suppliers. A firm with 10,000 vendors, Cronin says, might have 40,000 fourth and fifth parties it knows nothing about. Mapping them reveals regional concentration and hidden dependencies, and it sometimes startles the suppliers themselves. “Wow, you know a lot about me before I even know it,” is a common reaction.
Third-Party Risk Is Now a Boardroom Issue
For organisations still relying on spreadsheets and periodic reviews, Cronin’s advice is to treat third-party risk as “a live signal” and to act on it according to how important each vendor is. The subject, he adds, has moved beyond the CISO and the chief procurement officer to the boardroom, because everyone now understands how interconnected they are. “You need to use data, you need to use AI, but you need to actually use the humans that are risk professionals,” he says. Listen to the full episode of the Security Strategist Podcast for the complete conversation. Or, if you would like to find out more, visit the ProcessUnity website or follow Sean Cronin on LinkedIn.
Takeaways
Why annual assessments can no longer keep pace with evolving supplier and AI-driven risks.
How continuous monitoring identifies vulnerabilities and verifies actual vendor exposure.
Combining external scanning and business data to build a clearer picture of vendor risk.
Using SBOMs as risk indicators, supported by evidence and mitigation controls.
Reducing alert fatigue by prioritising critical vendors and high-impact relationships.
Automating questionnaires and evidence collection to improve risk assessments.
Balancing automation with human oversight and informed decision-making.
Mapping fourth- and fifth-party relationships to uncover hidden dependencies.
Why third-party risk is now a board-level operational resilience concern.
Chapters
00:00 Why annual questionnaires can’t keep pace with third-party risk
02:30 From on-site audits to rapidly changing supplier ecosystems
04:32 Real-time vulnerability response across vendor networks
08:16 Combining external signals with control-level data
10:08 SBOMs are useful signals, not ground truth
12:31 How continuous data makes assessments more relevant
16:28 Automating questionnaires and asking fewer, better questions
19:44 Keeping humans involved in AI-enabled risk decisions
21:57 Seeing fourth- and fifth-party exposure
24:41 Moving from periodic assessments to live risk signals - Two analysts select an alert from one of your noisier detection rules. The activity is limited, and they don't see the technique often, so they triage it on instinct. It takes them two hours, and they close it as a false positive. Behind that alert, a Chinese APT group has been inside a customer's network for weeks, and the first people to say so are threat researchers at the security vendor.
In this episode of The Security Strategist podcast, host Richard Stiennon, Chief Research Analyst at IT-Harvest, speaks with Georges Bossert, Chief Technology and Product Officer and Co-Founder of Sekoia. They question whether the alert-driven SOC has a future, what a CEO should measure in the enterprise for cybersecurity, and how far autonomous security operations can go while still passing an audit under NIS2 and DORA.
The average e-crime breakout now takes 29 minutes, and the fastest on record took 27 seconds. Steinnon says the typical SOC leaves 28 per cent of its alerts uninvestigated, and one in four malicious breaches is now AI-enabled, at about $6 million per breach. To this number, Bossert said, "We've been continuously executing trade-offs and intuition-based security."
Workflows today have been deeply impacted by the decades of scarcity of experts in cybersecurity. “In a year, we’ll transition to a new dimension of security where enterprises will begin to grasp what is actually providing security rather than individual people,” says Bossert.
Key Takeaways
The average e-crime breakout is 29 minutes; the fastest recorded is 27 seconds.
Bossert's metric: the share of alerts that got a proper investigation.
A proper investigation covers network, endpoint, and other domains, at speed.
Large MSSPs still focus only on the top critical alerts.
Sekoia researchers found a Chinese APT intrusion by tracking its infrastructure.
Analysts dismissed the APT alerts as false positives after a quick triage.
Replayed with AI agents, the same intrusion gets fully identified.
A frontier model needs a harness, the company's own data and a learning loop.
Bossert rejects a fixed list of decisions agents may never make.
Rules of engagement set what agents and people may do on their own.
Human on the loop governs the rules; human in the loop follows playbooks.
When an operation goes wrong, fix the methodology and replay it.
Chapters
00:05 Welcome and the 28% problem
01:09 Measuring SOC outcomes
04:01 Can a SOC investigate 100% of alerts?
05:15 How MSSPs filter alerts
07:38 Attacker pace and the APT case
11:48 Build or buy an AI SOC
14:35 Which decisions agents make alone
18:27 Where tier one talent comes from
20:53 The one takeaway for executives
Full episode page:
More from The Security Strategist podcast: https://www.youtube.com/playlist?list=PLXoSlBGE35NooDaiZh9e1OtBCEpUfLfZ3
Sekoia: https://sekoia.ai
Richard Stiennon on LinkedIn: https://www.linkedin.com/in/stiennon
Georges Bossert on LinkedIn: https://fr.linkedin.com/in/georges-bossert-a0059018/en
Related reading from EM360Tech:
Autonomous SOCs: https://em360tech.com/tech-articles/autonomous-security-operations-centre AI cyber attacks and human decision time: https://em360tech.com/tech-articles/ai-cyber-attacks-human-decision-time
Alert fatigue in SOCs: https://em360tech.com/tech-articles/deep-dive-alert-fatigue-and-its-management-socs
SOC as a service: https://em360tech.com/tech-articles/soc-service-how-choose-right-managed-security-provider
NIS2 obligations: https://em360tech.com/tech-articles/nis2-directive-obligations-eu
AI agent governance: https://em360tech.com/tech-articles/ai-agents-enterprise-governance
Follow EM360Tech: X: https://x.com/EM360Tech
LinkedIn: https://uk.linkedin.com/company/em360
More podcasts: https://em360tech.com/podcasts
#AutonomousSOC #AgenticAI #Cybersecurity #SOC #AISecurity #SecurityOperations #NIS2 #DORA #Sekoia #EM360Tech autonomous SOC, agentic AI, AI agents, SOC, security operations, cybersecurity, alert fatigue, NIS2, DORA, APT, Sekoia, Georges Bossert, Richard Stiennon, The Security Strategist, EM360Tech
More Business podcasts
Trending Business podcasts
About The Security Strategist
With cyber attacks more common than ever before and each attack becoming increasingly sophisticated, security teams need to be one step ahead of cybercrime at all times.
“The Security Strategist” podcast delves into the depths of the cybercriminal underworld, revealing practical strategies to keep you one step ahead. We dissect the latest trends and threats in cybersecurity, providing insights and expect-backed solutions to protect your organisation effectively.
Tune into this cybersecurity podcast as we dissect major threats, explore emerging trends, and share proven prevention strategies to fortify your defences.
Podcast websiteListen to The Security Strategist, PBD Podcast and many other podcasts from around the world with the radio.net app

Get the free radio.net app
- Stations and podcasts to bookmark
- Stream via Wi-Fi or Bluetooth
- Supports Carplay & Android Auto
- Many other app features
The Security Strategist: Podcasts in Family








































