The safeguards map / 3.7 Admission and owner settings
Veraison
Drafted with AI
Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made
Open-source components for an attestation verification service, with owner-written Rego policies that can overwrite the attestation result.
Where it sits
3.7 Admission and owner settings (primary): Verifies attestation evidence from a trusted execution environment before it is trusted, and lets the owner's Rego policy overwrite the attestation result status.
This repository contains attestation services assembled using Veraison components.
captured
You can update the attestation result by defining one or more of the following rules:
captured
This is also the default backend, so if no other backend is specified, `opa` will be used.
captured
Facts
- Concern
- security
- Names the law
- no
- Subject
- software
- Used by
- those who run it
- Runs
- at runtime
- Policy comes from
- owner-entered settings
Handoffs
consumes Policy: Rego policies (OPA)
Collector's note
Placed in 3.7 because attestation verification decides once, before a workload or device is trusted. The Consortium's page names no stage and the services repository has no GitHub releases, only monthly tags. The decision concerns hardware and software trust, not an AI agent's actions. The deployment the README offers is marked as not for production.
Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.