+Intertrace Insights
Identity, credentials and access
Whose key the agent holds, what a connected account really allows, and where access gets decided.
- Pieces
- 57
- Threat research
- 16
- Updated
- Oct 20, 2026
6 pieces · newest first
Guide9 min read
OAuth connects the account. Policy governs the action.
An integration broker solves OAuth plumbing, but a connected account's scopes describe what the provider's API allows, not what your agent should do. Seven beliefs about brokered agent access that fail in practice, what the RFCs actually say, and the calls that test each seam.
Intertrace
Guide10 min read
Whose key is the agent using? The credential lifecycle from first grant to revocation
A dispatch agent loops at 2 a.m. and nobody can stop it without breaking four other jobs or waking the engineer whose token it uses. One incident, followed through identity, scoped grants, rotation, measured revocation and offboarding.
Intertrace
Guide10 min read
Your internal assistant answers anyone with anything in the index. Fix it before retrieval.
Internal RAG assistants leak because the index is built with an administrator's access and queried by everyone. The case for putting the permission check inside the retrieval query, the two strongest objections, and why caches, summaries and revocation belong to the same argument.
Intertrace
Technical paper8 min read
Tenant isolation when every customer shares the model
Cross-tenant leaks in AI products rarely come from model weights. They come from prompt caches, vector indexes filtered by a client-supplied field, memory, shared tool credentials and logs. Seven checks, why each matters, and the canary tests that prove them.
Intertrace
News9 min read
When agents delegate to agents: what A2A verifies, and what your chain still has to
The Agent2Agent specification makes card signing optional and leaves authorization to each implementer, and public research shows a remote agent steering a client agent into an unauthorized trade. The questions to ask before your agents accept work from other agents, answered from the spec.
Intertrace Threat Research
Guide10 min read
Vendor agents in your systems: scope, logs and a kill switch that works
Vendors now ship agents that act inside your CRM, inbox and repositories with credentials you granted. The six decisions to make for each one, in order: identity, scope, contract, logs, a kill switch you control, and a clean exit.
Intertrace
+Stay current
New research, the week it publishes.
Subscribe with RSS, or email support@intertrace.ai with a topic you want covered. To see the controls in action, try the Simulation Lab or read the documentation.