Security · Trust
Every public release ships signed, attested, and with a software bill of materials — you verify provenance and integrity with public tooling instead of trusting us. The artifacts of each published release are the evidence.
Supply chain
The release pipeline generates these artifacts automatically, and every one of them is on each tagged release: download the artifacts and verify them with public tooling.
Release binaries are built by GitHub Actions with SLSA provenance attestation via slsa-github-generator. The attestation proves a binary was built from the committed source, in a hardened build environment, without manual intervention.
How verification worksThe checksums manifest and the container image are signed with Sigstore cosign (keyless mode via Fulcio + Rekor); the release carries an SPDX SBOM and an OpenVEX document, and the set carries SLSA provenance — each verified through its own path. You can verify without us distributing a public key — the transparency log is the root of trust.
Verification guideEach release includes an SBOM in SPDX format, listing every dependency with version and license. Machine-readable, auditable.
How to verify the SBOMKnown vulnerabilities and their applicability to each release are published as OpenVEX documents. VEX statements distinguish "affected", "not affected", and "under investigation".
How advisories are verifiedA machine-readable vulnerability disclosure policy at /.well-known/security.txt, following RFC 9116. Includes contact, policy link, and expiry.
View security.txtArchitecture
Unknown state is denied, not permitted. Every policy decision defaults to deny — an engine that cannot reach its policy store refuses all requests rather than failing open.
The audit ledger is append-only with cryptographic chaining. Events cannot be silently modified or deleted — tampering breaks the chain and is detectable.
The engine runs entirely in your environment. License verification is offline (Ed25519 signature check). No telemetry, no mandatory network calls, no activation server.
Cedar-based RBAC and ABAC with scoped grants. Custom roles, delegation ceilings, and break-glass with dual-control. The default permission set is empty. Custom roles, scoped grants and break-glass are Business.
Compliance
We publish what is live and what is not yet started. We do not claim certifications we have not obtained.
RFC 9116 security.txt
Machine-readable vulnerability disclosure policy, live at /.well-known/security.txt.
SLSA Build Level 3
Provenance attestation via slsa-github-generator — built and exercised in CI; publishes with every tagged release.
SBOM (SPDX)
Software bill of materials generated for every release build.
Cosign keyless signatures
Sigstore-based artifact signing via Fulcio + Rekor.
OpenVEX advisories
Vulnerability applicability statements per release.
SOC 2 Type II
Planned.
ISO 27001
Planned. Timeline not committed.
Independent penetration test
Planned. Will be published when completed.
Framework readiness
Business maps capabilities to 26 compliance framework catalogs. Below is the readiness posture for the frameworks most requested by enterprise buyers. Each item is a readiness mapping — not a certification.
Annex A control mapping with evidence pointers. Not certified.
AIMS readiness mapping — the product generates the evidence an AIMS requires. Not certified.
Trust Services Criteria (Security / Common Criteria) mapping. Not attested.
Annex IV technical documentation template. The product is governance tooling, not itself an Annex III system.
CAIQ v4 and AI-CAIQ (AICM v1.0) self-assessments prepared. Not submitted to the STAR Registry.
RTBF runbook with crypto-shred, residency attestation, retention and legal hold. Self-hosted: customer is controller and processor.
Subcategory mapping including the Generative AI Profile (AI 600-1).
ICT-risk view export; the Register-of-Information generator is included in the Business Compliance Packs family.
Obligation mapping with ICT supply-chain posture and incident-reporting evidence.
Trust package
The trust package is downloadable from this Trust Center and ships in the public source repository. Enterprise buyers can request the full package — including pre-filled questionnaires and the evaluation guide — via enterprise@olivares.ai.
Available files are public Markdown snapshots. Each one starts with a header line that gives its snapshot date and the SHA-256 digest of everything after that line and the blank line below it. Items without a shareable source remain available on request.
CSA Cloud Controls Matrix v4 — 17 domains with evidence pointers.
Download (Markdown)CSA AI Controls Matrix v1.0 — 18 domains including Model Security.
Download (Markdown)33 pre-verified answers aligned to SIG 2026, CSA AI-CAIQ, and common buyer questionnaires.
Download (Markdown)Buyer-facing architecture: three trust zones, deployment topologies, HA/DR, sizing.
Download (Markdown)Proof-of-value in 10 business days — pass/fail criteria against the real binary.
Download (Markdown)Business includes the commercial license, signed release channel and four capability families: Regulated Operations, AI Runtime Security, Compliance Packs, Identity & Scale. Nothing is sold separately.
Download (Markdown)Threat model verification with file:line evidence — pentest-ready.
Available on requestVoluntary Product Accessibility Template for the admin console.
Download (Markdown)Data processing
Olivares AI is self-hosted software. Olivares governance data — inventory, access map, policy state and audit evidence — stays in infrastructure you control by default, and there are no sub-processors of customer data. Requests to hosted model providers, and any output or telemetry destinations you configure, go to the vendors you choose — your vendors, not ours; the product catalogs them in the inventory for your third-party risk management. Olivares itself has no mandatory calls home.
Our own website, licensing and communications run on:
Website hosting, DNS and anti-bot protection.
Transactional email delivery.
Merchant of record for commercial licenses.
Source hosting and community.
We use no client-side analytics provider and run no client-side analytics.
Verify yourself
Obtain scripts/verify-release.sh from a trusted source checkout of the release tag; it is not a release asset. Run it from the directory containing the downloaded files. Keyless verification needs Sigstore trust-root material and network access.
/path/to/olivares/scripts/verify-release.sh --source-tag <version>--source-tag <version> pins only SLSA provenance and requires slsa-verifier. SHA-256 checksum comparison needs no network; authenticating the manifest still requires the signing checks. --offline skips Rekor lookup, not every network dependency. Keyless signatures and SBOM/OpenVEX attestations need Sigstore trusted-root material unless cached; SLSA has no offline switch here. Skipped checks are unverified. See the guide for prerequisites.
Deploy the demo estate in five minutes, then run the full proof-of-value in 10 business days. The evaluation guide includes pass/fail criteria against the real binary — no slides, no sandbox, no demo environment that differs from production.
Not yet. Readiness mappings exist for both — SOC 2 (Trust Services Criteria) and ISO 27001 (Annex A controls) — with evidence pointers to the codebase. We publish posture, not claims.
Not yet. The program is committed with scope, cadence, and budget documented. The first independent test is planned for post-launch; results will be published.
Obtain scripts/verify-release.sh from a trusted source checkout of the release tag; it is not a release asset. Keyless verification needs Sigstore trust-root material and network access. --source-tag <version> pins the SLSA provenance check to tag <version>; it requires slsa-verifier and is skipped if that tool or provenance is missing. The default checks for signatures and SBOM/OpenVEX attestations accept any release tag from the project’s signing workflow, not only <version>. Skipped checks are unverified. See the guide for prerequisites and container-image verification.
With self-hosting, Olivares governance data (inventory, access map, policy state and audit evidence) stays by default in infrastructure you control. Requests to the hosted model providers you choose, and data sent to output or telemetry destinations you configure, go to those external services. The services we use for the website, licensing and communications are listed separately on this page.
Yes — a GDPR Art. 28 DPA is available on request via enterprise@olivares.ai for enterprise procurement, even self-hosted, where you remain the controller and processor of your own data.
Business maps 26 framework catalogs including EU AI Act, NIST AI RMF, ISO 42001, SOC 2, ISO 27001, GDPR, NIS 2, DORA, OWASP Agentic, CSA AICM, and US state AI laws. Each framework is data with per-control evidence — not a certification claim.
Install a signed release or build from source, boot the demo estate in five minutes, and follow the 10-day evaluation guide. Every criterion is pass/fail against the real binary. Contact enterprise@olivares.ai for an enterprise evaluation license for the POV.
Community is the complete, free AGPL-3.0 platform with unlimited users and one active identity provider. Business includes the commercial license, signed release channel and four paid capability families. Enterprise adds negotiated contract terms. For more legal entities, deployments or identity providers, air-gap, custom LTS, OEM/MSP or support objectives, contact us about Enterprise.
Every public release ships signed, attested, and documented — verify the integrity yourself.