Security
Decide before the side effect starts.
Security here is not a dashboard of what the model said. It is an independent decision on what the agent is allowed to do, before execution.
Philosophy
How we think about control
Independent gate
The agent proposes the action. Sector8 decides. The runtime that wants the side effect does not approve itself.
Before execution
The decision happens before the tool runs, the file is read, the refund is issued, or the deploy starts. After-the-fact logs are not a control.
Deterministic
Same action, same policy, same decision. If it is not reproducible, it is not a control.
Fail-closed
If the gate is unreachable, times out, or returns an unknown decision, the action does not run — for actions your app sends to Sector8.
Evidence
Every decision carries a reason code, decision trace ID, evidence hash, and policy version. Allows are recorded, not just denials.
Scope
What this is not
- We do not sell LLM observability, dashboards, or prompt telemetry as the product.
- We do not classify toxic output, jailbreaks, or hallucinations as the control.
- We do not judge models with models.
- We do not make you GDPR, HIPAA, or EU AI Act compliant.
- We do not replace content security, SIEM, DLP, or your own governance.
Evaluate path
What we receive
The gate evaluates the proposed action you send: tool, parameters, caller, and policy scope. It returns ALLOW or DENY with an evidence record. That is the product path. It is not a prompt archive and not a SIEM.
How we run Sector8
What you can take to a review
- Tenant-isolated policy enforcement
- EU-hosted deployment
- Encryption in transit and at rest
- Versioned policy sets, bound per tenant
- Auditable decision evidence
Security questionnaires: hello@sector8.ai.