oktsec
Free workflow checkScope an Assessment

Where Oktsec runs and what leaves your environment.

Agent clients talk to a local Oktsec node. The node enforces the policy. Oktsec Cloud only receives evidence and distributes signed policy. This page lists what stays, what leaves and what is still planned.

  • No inbound access.
  • Code, data and credentials never leave.
  • Planned capabilities are labeled.

Architecture.

Three planes. Enforcement stays where the agent runs. The control plane never sits in the execution path.

Deployment architectureInside your environment, agent clients send tool calls to a local Oktsec node. The node applies signed policy and writes hash chained evidence. Allowed actions reach approved environments. Blocked actions stop at the node and are recorded. The node opens one outbound connection across the trust boundary to Oktsec Cloud to push evidence and pull signed policy. No inbound access.Your environmentTrust boundaryOutbound onlyOktsec CloudAgent clientsWhere work startsClaude CodeCursorVS Code14 more clientsMCP servers and skillsHooks and subagentsLocal Oktsec nodeWhere the decision happensPolicy engineSigned, deterministicEvidence ledgerHash chained recordsRuns on the workstation,server or container.Approved environmentsWhere the action landsRepositoriesInternal APIsCloud accountsMCP serversOnly actions the policyallowed reach here.Tool callAllowed actionBlocked actions stop here. Recorded, never forwarded.One outbound connection, opened by the nodeEvidence out. Signed policy in. No inbound access.Hosted control planeNever in the execution pathReceives evidenceDistributes signed policyReports exceptionsOktsec managed.Evidence and policy only.
Swipe sideways to see the whole diagram.

Agent clients

Where work starts. Claude Code, Cursor, VS Code and 14 more clients. MCP servers, skills, hooks and subagents.

Local Oktsec node

Where the decision happens. Signed policy is applied here, deterministically. Evidence is written here, hash chained. Runs on the workstation, server or container. Built by people who spent seven years hardening enforcement software on devices they did not control.

Approved environments

Where the action lands. Repositories, internal APIs, cloud accounts, MCP servers. Only actions the policy allowed.

Oktsec Cloud

Hosted control plane. Receives evidence. Distributes signed policy. Reports exceptions. Pull only, outbound from the node.

What never leaves.

Everything the node reads to decide stays on the node. Five categories, none of them transmitted.

  • Source code and repository contents
  • Customer and business data
  • Credentials, tokens and keys
  • Prompts and model outputs
  • File contents read or written by the agent

What does leave.

Only the decision record. Example payload, illustrative values.

Decision recordExample values
{
  "request_id":   "req_7c1e…",
  "principal":    "agent-runner@ci",
  "tool":         "shell.exec",
  "decision":     "block",
  "policy_version": "v14",
  "policy_hash":  "sha256:9f3a…c41e",
  "record_hash":  "sha256:2b77…e9d0",
  "prev_hash":    "sha256:d4c4…1e07",
  "signature":    "ed25519:…"
}

Request metadata, decision, policy version and hashes. Parameters and content stay on the node.

Inbound access.

None. The node pulls signed policy over one outbound connection and pushes evidence the same way. Nothing on the customer side listens for Oktsec.

PropertyHow it worksStatus
DirectionOutbound onlyAvailable
Policy deliverySigned bundle, pulled by the nodeAvailable
Evidence deliveryPushed by the node, hash chainedAvailable
Control plane in the execution pathNeverAvailable

Offline verification.

The same verifier as on the Oktsec Control page. Anyone with the public key can check the chain without Oktsec Cloud, on a machine with no network.

  1. 01
    Export the audit database

    Copy the node's audit database out of the environment.

  2. 02
    Take the node's public key

    keys/proxy.pub is the only material you need from Oktsec.

  3. 03
    Run the verifier

    Every hash recomputed, every signature checked.

Terminal
# from any machine, no network needed
oktsec audit verify-chain --db ./oktsec.db --key ./proxy.pub

# machine readable output for auditors
oktsec audit verify-chain --db ./oktsec.db --key ./proxy.pub --json

Data residency and control plane modes.

Regulated teams in Latin America and Europe ask where evidence is stored and who can reach it. This is the real state, not the roadmap dressed as product.

ModeWhere it runsStatus
Hosted control planeOktsec managed, evidence and policy onlyAvailable
Private control planeCustomer VPCPlanned
Isolated control planeNo shared infrastructurePlanned
Offline control planeAir gapped, artifact handoffPlanned
Evidence region selectionChoose the region where evidence is stored. Export it at any timeAvailable

Frameworks.

Deployment choices map to control families in NIST AI RMF, OWASP Agentic Top 10, MITRE ATLAS, CSA AICM, ISO 42001 and ISO 27001.

Review framework mappings

Security disclosure.

Found something in Oktsec? Write to security@oktsec.com. We acknowledge within two business days and publish fixes with credit. Our own research goes through the vendors' programs first, the same way.

Report a finding

Walk your security team through the deployment.

Thirty minutes with the people who built the node. Bring your network diagram and your questions about what leaves.

Book a deployment reviewSee Oktsec Control