Notifications
Clear all
Topic starter
11/08/2026 3:17 pm
TL;DR: Black Hat USA 2026 will surface how autonomous AI systems can cross trust boundaries, chain attack vectors, and outpace existing controls, following incidents at Hugging Face and OpenAI that exposed how agents can move from evaluation into real-world compromise. The core issue is not rogue behaviour but governance models that still assume access is human-paced and reviewable.
NHIMG editorial — based on content published by Noma Security: Black Hat USA 2026 and the AI trust-boundary problem for CISOs
Questions worth separating out
Q: How should security teams govern AI agents that move across multiple trust boundaries?
A: They need runtime controls that follow the agent rather than staying attached to one platform.
Q: Why do agentic AI systems change IAM risk?
A: They change risk because they can move from observation to execution.
Q: What breaks when AI workflow inputs can influence execution?
A: Traditional data validation is not enough when a prompt, model file, loader, or dataset can change what runs next.
Practitioner guidance
- Define agent-specific trust boundaries Map every AI workflow to the exact inputs, tools, data sources, and execution paths it is allowed to reach.
- Separate agent identity from human access paths Do not let agent actions disappear into shared user, service, or pipeline identities.
- Rework access reviews for runtime behaviour Assess whether your recertification model can meaningfully govern access that is created, used, and discarded inside one execution window.
What's in the full article
Noma Security's full article covers the operational detail this post intentionally leaves for the source:
- Specific Black Hat talking points and how the vendor frames each AI security signal for conference attendees
- Direct commentary on the Hugging Face and OpenAI incidents, including the exact sequence of trust-boundary crossings
- The vendor's full set of questions for evaluating AI demos, pipelines, and agent authority in practice
- Operational context on what CISOs should listen for when AI capabilities are presented as security controls
👉 Read Noma Security's analysis of AI agent trust boundaries at Black Hat USA 2026 →
AI agents at Black Hat: are your trust boundaries keeping up?
Explore further
11/08/2026 3:29 pm
AI agent trust boundaries are now an identity problem, not just a model safety problem. The article shows that the most consequential failures happen when autonomous systems cross boundaries that were designed for human-paced or script-driven action. Once an agent can choose actions and continue execution without a human in the loop, the trust model has to be judged as identity governance, not simply AI safety. Practitioners need to treat agent authority as a governed access surface.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared with nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: Who is accountable when an AI agent causes a security incident?
A: Accountability should sit with the business owner, the system owner, and the security function together, because agent behaviour crosses operational boundaries. Organisations need a defined owner for approval, monitoring, and retirement, plus audit evidence that shows what the agent accessed and why.
👉 Read our full editorial: AI agent trust boundaries are the new security problem at Black Hat
