The safeguards map / 3.7 Admission and owner settings
Ratify
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
A verification engine that checks artifact signatures and security metadata and admits to Kubernetes only artifacts that meet the owner's policies.
Where it sits
3.7 Admission and owner settings (primary): Verifies the signatures and security metadata attached to an artifact, as a binary or on Kubernetes, and admits for deployment only artifacts that meet the owner's policies.
which enables verification of artifact security metadata and admits for deployment only those that comply with policies you create.
captured
With the Cosign verifier, Ratify can be used to verify signatures generated using
captured
uses a trust store and trust policy to determine if a signed artifact is considered authentic.
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 Provenance and signatures: Cosign signatures and Notation (Notary) signatures
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.