Not based on a specific customer deployment. The company, figures, decisions, and outcomes below are a constructed example that shows how Intended’s mechanism applies to this kind of problem. They are not measured results from a named customer. Where we publish a real, attributed customer outcome, we will say so explicitly.
Proving AI-Agent Tenant Isolation for a SOC 2 Audit
Consider a B2B SaaS platform whose AI agents handle customer onboarding, data migration, support automation, and cross-tenant analytics — and whose SOC 2 Type II audit requires proof of tenant isolation.
01 · the challenge
The kind of problem this addresses.
02 · how it works
See the difference.
AI agent (Tenant A context)
Authenticated as TenantA support agent
Requests Tenant B customer data
query: SELECT * FROM customers WHERE tenant_id = 'B'
Data returned
Application-layer check missed edge case
Tenant B data exposed
No audit trail of cross-tenant access
03 · the solution
What they deployed.
- — Installed SaaS Operations domain pack with tenant-aware intent classification
- — Configured tenant context validation on every AI agent action
- — Cross-tenant access set to automatic DENY with zero exception policy
- — Evidence bundles generated for every tenant boundary check (pass and fail)
- — SOC 2 auditor received a complete tenant isolation report in under 60 seconds
04 · implementation
From zero to governed.
Week 1
Instrument
Added Intended SDK to all AI agent services. Configured tenant context propagation from auth tokens.
Week 2
Configure
Installed SaaS Ops domain pack. Defined tenant isolation policies, cross-tenant deny rules, and alerting.
Week 3
Audit-ready
Generate SOC 2 tenant-isolation evidence. Every tenant boundary check becomes independently verifiable from the cryptographic chain.
05 · illustrative outcomes
What this is designed to deliver.
Modeled figures for this scenario — what the workflow above is built to achieve, not measured results from a named customer.
0%
Cross-tenant access denied
Zero-exception policy on tenant mismatch
0%
Boundary checks evidenced
Pass and fail, in the audit chain
<0s
Audit evidence generation
Design target for isolation proof
0-click
Auditor verification
Independent of application-layer logs
06 · decision replay
Example decisions, full trace.
Sample decision records that show the shape of the evidence Intended produces. Illustrative, not drawn from a live customer’s logs.
saas.data.tenant-queryRISK: 8/100ALLOW14msSupport agent queries customer list for Tenant: Acme Corp (tenant_id: acme-001)
Resolved by: Policy: same-tenant data access, authenticated agent
saas.data.cross-tenant-accessRISK: 100/100DENY11msMigration agent (Tenant: Acme) attempts to read schema from Tenant: GlobalTech
Resolved by: Policy: cross-tenant access forbidden (tenant mismatch)
saas.onboarding.provision-tenantRISK: 32/100ALLOW22msOnboarding agent creates new tenant workspace for Pinnacle Industries
Resolved by: Policy: provisioning allowed for onboarding agents with valid contract
saas.analytics.cross-tenant-aggregateRISK: 45/100ESCALATE18msAnalytics agent requests anonymized usage metrics across all tenants
Resolved by: Data Privacy Officer (approved aggregated-only access in 3m 18s)
the takeaway
Tenant isolation is hard to prove with application-layer logs alone. When every boundary check is recorded in a cryptographic chain, an auditor can verify isolation independently — turning a multi-week evidence exercise into a query.
Why this pattern matters — not a customer quote.
Start proving tenant isolation
Free to start. See every AI decision from day one.