Trust & Security

Production-grade by inheritance, not by badge.

Hosted agent vendors ask you to trust their certifications. Vocion takes the other path: it runs inside your AWS account, on AWS's production agent infrastructure, under the IAM, VPC, KMS, and CloudTrail controls your security team already audited. There is no vendor control plane to trust, because your traffic never leaves your account.

Your AWS account · your VPC · your data never leaves

Vocion — the workforce layer

MPL-2.0 · yours

Roles & agentsContext & learningsReview & inboxEvalsRegistryBudgets & policy

standing on

AWS — the production floor

Bedrock AgentCore

runs the agent loop

Bedrock Guardrails

screens input + output

CloudWatch (OTEL)

traces in your stack

IAM + KMS + CloudTrail

your existing controls

terraform apply — the whole stack, one commandAWS Marketplace listingair-gapped reference topology

Vocion inherits the controls your security team already audited — IAM, VPC, KMS, CloudTrail — because it runs inside them, in your account.

Guarded run · support_reply #4812agent id: sr-7f2 · signed

Screen
passed
Prompt-injection check on everything the agent reads
Policy
allowed
Access, budget, and autonomy checked before any action
Validate
2 fields masked
PII masked and content filtered before anything leaves
Review
approved
A person approves anything customer-facing

Audit record: agent sr-7f2 + Morgan (CX Lead) · both identities on the signature · exportable to your compliance stack

Every run travels the same guarded path — screened in, checked against policy, masked on the way out, reviewed by a person, and signed into the audit record.

The posture, question by question

Where it runs

Your AWS account and VPC. One `terraform apply` stands up the full topology; an air-gapped reference exists for regulated environments.

Who runs the loop

Amazon Bedrock AgentCore — AWS's managed agent harness. Vocion defines the role, the context, and the review; AWS executes the loop in isolated sessions.

What screens the traffic

Bedrock Guardrails on every input and output: prompt-injection checks in, PII masking and content filtering out. The control your security team has already approved.

Where the traces go

OpenTelemetry-native. Runs land in CloudWatch, Datadog, or whatever your team already watches — with cost, context version, and approval on every trace.

Who did what

Dual identity on every side-effect: the agent's own principal plus the approving person. Revocable, least-privilege, on the CloudTrail record.

What is it allowed to do

Policy as code (Cedar — the same language AWS uses), with budgets, autonomy levels per agent, and a kill switch any operations lead can pull.

On certifications, plainly

SOC 2 and ISO 27001 certify an operator of a hosted service. Vocion is software you host, so the certification that governs your deployment is your own cloud posture — which is exactly where your auditors want it. When AWS operates the loop (AgentCore), the traffic runs on infrastructure covered by AWS's compliance programs. What Vocion adds on top is the evidence trail an audit actually asks for:

— Every run traced to its inputs, context version, tools called, and cost
— Every customer-facing output linked to a named human approval
— Every agent change scored against evals before promotion, with the history kept
— Every side-effect signed by both the agent identity and the approver