Runtime authorization boundary
BobSentry sits immediately before execution—after an agent proposes an action, before tools, APIs, or infrastructure are mutated. It returns ALLOW, REQUIRE_APPROVAL, or BLOCK.
Security
Designed as an independent runtime authorization boundary
BobSentry evaluates normalized action metadata with deterministic policy decisions. Sensitive payloads stay in your environment. Every decision produces signed decision evidence.
Data-flow diagram
Customer environment
- AI agent
- Sensitive payload
- Local classification / redaction
Normalized action metadata
BobSentry
- Deterministic policy evaluation
- Human authorization
- Signed decision evidence
Deterministic policy evaluation
Policies evaluate action metadata, target, context, and risk to produce a deterministic decision. High-risk actions can require human authorization without stopping every autonomous workflow.
Metadata-first architecture
BobSentry receives normalized action metadata—not raw source code, PHI, financial records, credentials, or full prompts. Local classification can redact or summarize sensitive fields before the evaluate call.
Sensitive payload handling
Customer-controlled agents and services retain sensitive payloads. Only the metadata required for policy evaluation crosses the boundary.
Transport security
Runtime API traffic uses HTTPS. API keys authenticate callers; keys should be stored and rotated according to your secret-management practices.
Signed decision evidence
Each decision can be exported as signed JSON (and PDF where enabled). Evidence captures the requested action, policy evaluation, decision outcome, authorization state, and cryptographic integrity—audit-ready records of authorization decisions, not a compliance guarantee.
Action hashing
Action hashes bind approvals and evidence to the proposed action so an authorized decision cannot silently apply to a different payload.
Tenant isolation
Evaluation, policies, approvals, and evidence are scoped per tenant. Cross-tenant access is not part of the product model.
API-key handling
Sandbox and production keys authenticate Runtime API callers. Do not embed production keys in public clients. Rotate compromised keys immediately.
Failure-mode configuration
Integrations should define fail-closed or fail-open behavior for unreachable evaluate calls based on risk tolerance. Prefer fail-closed for consequential production actions.
Certifications and compliance posture
BobSentry is designed to support regulated workflows. We do not claim completed SOC 2, HIPAA, GDPR, ISO 27001, or other certifications on this site unless evidence is published. Contact us for current status.
Responsible disclosure
Report security issues to hello@bobsentry.com with enough detail to reproduce. Do not include real customer data in reports. Contact hello@bobsentry.com.