Controls buyers can inspect before connecting a repository.

Data boundary

Scanning runs locally by default. Qubrisk does not require source code, private keys, certificate private material, tokens, or secrets in the hosted control plane. Uploaded records may include paths, fingerprints, metadata, redacted evidence selected by the customer, dependency identifiers, ownership hints, policy results, and CBOM records.

Access and tenancy

Sessions and scanner keys are one-way hashed. API keys are shown once and scoped to a workspace. Stateful product queries include an organization boundary, and administrative actions require server-side role checks.

Encryption and operations

The cloned deployment foundation supports encrypted stored objects, SQLite WAL integrity checks, encrypted off-box backups, restore verification, a non-root container, health checks, and resource limits. Production configuration requires explicit secrets.

Integrations and billing

Stripe webhook signatures are verified and replay-protected. Managed OAuth connections store workspace-scoped provider identifiers rather than exposing raw provider credentials to the scanner.

Assurance status

Qubrisk does not claim SOC 2, ISO 27001, FIPS validation, or another independent certification without current evidence. A cryptographic inventory is not a compliance certificate.

Procurement references

Security and accuracy model · Privacy notice · Service terms