Security & compliance
Built for regulated industries from the ground up.
Governance, redaction, isolation and audit aren’t add-ons; QOR was designed around them. It’s built to the requirements of NIST SP 800-171 / CMMC 2.0 Level 2, ITAR technical-data handling, FIPS 140-3 cryptography, HIPAA and SOC 2, and exceeds them in places. We test QOR internally against those controls.
QOR has not been externally audited or certified; certification is your step with your assessor, and QOR produces signed evidence bundles to support it.
- NIST SP 800-171
- CMMC 2.0 Level 2
- ITAR technical data
- DFARS 252.204-7012
- FIPS 140-3 cryptography
- HIPAA
- SOC 2
Controls
No external security service required
QOR is designed for organizations without an enterprise security stack to lean on. The controls reinforce one another: a misbehaving agent is limited by the authority delegated to it, by the governance gate, by row-level security in the database and by the sandbox around its tools, and its decisions are recorded in the ledger.
Identity
Built-in accounts support MFA and hardware-key (WebAuthn) sign-in, with no external identity provider required. Single sign-on through your OpenID Connect provider is optional.
Authorization
Every delegation narrows authority, and the governance gate refuses what it cannot decide. Authority is checked throughout execution and can be revoked mid-task.
Per-user isolation
Each user has their own agent team, and the database itself enforces data isolation through row-level security, not only application code.
Network
Internal services and nodes authenticate each other with mutual TLS. Nothing inside the network is trusted by default. Remote nodes join over an encrypted WireGuard fabric.
Governed egress
Outbound traffic leaves only through governed paths: named integrations and model providers by allowlist, and web research through a read-only, audited gateway with a per-organization blocklist.
Secrets
Secrets live in Vault, never in images or environment files, and stay highly available even on one- and two-node installations.
Encryption
Data is encrypted at rest, and in transit with TLS for browsers and mutual TLS between services and nodes.
Sandboxed tools
Custom tools run in an isolated container sandbox with no network access.
Audit
A hash-chained audit trail covers agent actions, data access and configuration changes, and every governance decision is written to an append-only ledger. Refusals are recorded, never silent.
Evidence for your assessor
Signed evidence bundles, verifiable offline
When you prepare for an assessment, QOR produces the evidence. Each bundle carries a manifest of per-file SHA-256 digests, and the manifest is signed with a key held in Vault. Your assessor verifies it offline against the matching public key, without relying on the system that produced it, and the export itself is recorded in the audit trail.
A live control mapping connects QOR’s controls to the frameworks it is built to support. The compliance dashboard shows control status and generates the matching bundle from the same screen.
- SSP fragments
- POA&M
- Access-control export
- Audit extract
- Model lineage
QOR provides the controls and produces evidence for them; it does not replace the assessment. Certification by an accredited third-party assessor is a separate engagement.
Air-gapped operation
What an air gap gives up, and what stays
An air-gapped installation has no outside connection, so four capabilities that need one are unavailable. Each has a local counterpart.