+Intertrace Insights
Technical papers
Architecture and engineering papers on runtime enforcement: the mechanisms, the trade-offs and the evidence behind them.
- Pieces
- 57
- Threat research
- 16
- Updated
- Oct 20, 2026
6 pieces · newest first
Technical paper9 min read
The loosening hidden in a tightening: shipping agent policy changes with replay
One pull request against a procurement agent's policy, followed through rule tests, a 30-day decision replay, monitor mode, staged enforcement and an audit link to the commit, showing why peer review backed by a decision diff beats a change board.
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
Technical paper9 min read
The cost of a guardrail: latency and inference budgets for runtime AI security
Every runtime security check spends latency and money on the request path, and the share of traffic sent to an LLM judge sets both your bill and your p99. Six decisions, in order, for building a guardrail product teams will keep switched on.
Intertrace
Technical paper10 min read
Securing agents that click: computer-use and browser agents
A hotel receipt tells an expense-filing browser agent to change the reimbursement bank account. A step-by-step teardown of how that works, then the controls that hold even when the injection lands: isolation, allowlists, gated clicks, credential handling, redaction and takeover.
Intertrace
Technical paper10 min read
Red teaming AI agents as a continuous program, not an event
A red-team report describes the agent you had last quarter. The case for running it as a regression suite instead: technique-indexed cases, sandboxed tools, scoring by consequence rather than refusal text, benign twins, and reruns on every change.
Intertrace
Technical paper10 min read
What to record for every agent action: a security telemetry schema
Agent logs inherited from performance monitoring say how long and how much, not who, on whose authority, or why it was allowed. A five-band event schema mapped to OpenTelemetry GenAI conventions, with privacy rules and retention tiers.
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.