Who owns the controls?
Claude Code is inside the session. Identity verification gets it to the door, but the gap between “Claude Code authenticated” and “Claude Code ran a query against prod” is where risk lives. And it moves at machine speed.
- Recorded
- April 22, 2026
- Length
- 45 min, live demo on real infrastructure
- For
- Engineering leaders, platform engineers, security teams, DevOps and SRE
$ claude "query user emails from prod"
> SELECT email, ssn, phone FROM users LIMIT 3
sarah.chen@hooli.io 284-19-7653 +1 415-892-3041
marcus.webb@globex.com 531-77-0294 +1 212-555-8817
elena.ruiz@initech.co 719-42-8106 +44 20-7946-0958
No masking. No audit trail. No gate.$ claude "query user emails from prod"
> SELECT email, ssn, phone FROM users LIMIT 3
hoop masking PII in transit
sarah.chen@hooli.io 284-19-7653 +1 415-892-3041
marcus.webb@globex.com 531-77-0294 +1 212-555-8817
$ claude "drop the staging table"
hoop blocked: DROP TABLE
routed to #infra-approvals for reviewPAM governs the door. Not the room.
Default Claude Code has 0 in-session controls. 100% of queries are visible to the model context. A destructive command executes in <1s.
- The doorClaude Code authenticatedPAM and identity checks pass
- The roomNo masking. No gates. No audit trail.Nothing governs what it sees or executes
- ProdClaude Code ran a queryDatabases, APIs, kubectl, at machine speed
Most access tools stop at authentication. Once Claude Code opens a session, nothing governs what it can see or execute inside that session. It queries databases, calls APIs and runs kubectl commands, all at machine speed, all without review.
The session opens. No masking. No gates. No audit trail. Just Claude Code and your infrastructure. The recording shows what changes when a gateway sits between the two.
What the session covers.
Protocol-layer enforcement for Claude Code in production.
- The in-session gapPAM gets you to the door. We show what happens after Claude Code opens the session, and why identity verification alone is not enough.
- Data masking at the protocol layerLive demo: mask PII, PHI and credentials in transit before they ever reach the model context. No schema changes. No workflow disruption.
- Command-level gates and kill switchesDefine what Claude Code can and cannot execute. Block destructive operations deterministically. Route risky commands for human approval in real time.
- Audit trail as proofEvery action logged at the command level: who connected, what ran, what came back and what was masked. Compliance-grade evidence.
No slides. Live infrastructure.
- The gap0 to 15 min
How Claude Code interacts with production infrastructure today and where controls are missing.
- Live demo15 to 35 min
Deploy the gateway. Mask data. Block a command. Show the audit trail. All in real time.
- Q&A35 to 45 min
Open discussion. Bring your architecture, your compliance requirements, your edge cases.
- Deploys in a day
- No changes to developer workflows
- Risk profile adjustable on the fly
- Works with any LLM-powered tool