Notifications
Clear all
Topic starter
28/08/2026 12:04 pm
TL;DR: Salesforce is pushing Agentforce agents to the front of the user experience, which removes visible login and approval checkpoints while leaving access, delegation chains, and audit obligations intact, according to Trust3. The security problem is no longer the screen but the agent boundary and data layer, where purpose-based policy, runtime guardrails, and traceability must replace role-only control.
NHIMG editorial — based on content published by Trust3: LLMjacking: How Attackers Hijack AI Using Compromised NHIs
By the numbers:
- Gartner projects that through 2029, more than half of successful attacks on AI agents will exploit access-control weaknesses.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do AI agents create a governance problem for IAM teams?
A: AI agents create a governance problem because they authenticate and act as autonomous software entities with tool access.
Q: What breaks when agent identity is not inventoried and approved?
A: Shadow agents can appear outside normal review, causing undercounting, orphaned access, and unknown data reach.
Practitioner guidance
- Inventory every active agent instance Build a live register of approved and unapproved Agentforce agents, including owner, data reach, and trust score.
- Attach purpose to every delegated action Replace role-only grants with per-request policy that carries declared purpose through each hop in the delegation chain.
- Enforce policy at the data source Apply row, column, and tag-based controls where the data lives so the decision evaluates the originating user, not the final service account.
What's in the full article
Trust3's full analysis covers the operational detail this post intentionally leaves for the source:
- The exact Agentforce and Headless 360 control points that Trust3 says need to move from UI review to runtime enforcement.
- The Trust Score workflow for discovering approved and unapproved agents across SaaS, cloud, and developer environments.
- The policy model for purpose-based access, JIT grants, and auto-expiring scopes across delegation chains.
- The audit and replay mechanics that map agent actions to EU AI Act, HIPAA, SOX, and NIST AI RMF obligations.
👉 Read Trust3's analysis of Salesforce Agentforce interface control and AI agent oversight →
Salesforce Agentforce interfaces: what happens to IAM controls now?
Explore further
28/08/2026 12:04 pm
Interface collapse creates an identity governance problem, not just a UX change. Once the login screen stops being the place where access is checked, the programme must stop assuming that human visibility equals control. The real issue is whether identity, purpose, and approval can still be bound to each action when the agent executes across tools and data sources. Practitioners should treat this as a shift in enforcement architecture, not a cosmetic platform change.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to The State of Secrets in AppSec.
- 63% of organisations say leaked secrets are one of their top application security concerns, according to The State of Secrets in AppSec.
A question worth separating out:
Q: Who is accountable when an AI agent delegation chain causes an unauthorised action?
A: Accountability depends on whether the organisation can reconstruct the chain. If logs capture sender identity, recipient identity, task ID, delegation depth, and validation results, investigators can pinpoint the failing handoff. Without that trail, responsibility becomes ambiguous across the orchestration layer and the individual agents.
👉 Read our full editorial: Salesforce agent interfaces shift control to the data layer
