The safeguards map / 3.7 Admission and owner settings
CRI-O (signature verification policy)
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
CRI-O reads a signature policy file that decides whether an image it has pulled is trusted, with optional per-pod-namespace policies.
Where it sits
3.7 Admission and owner settings (primary): Applies a signature policy file, system-wide or per pod namespace, to decide whether to trust an image on pull.
Path to the file which decides what sort of policy we use when deciding whether or not to trust an image that we've pulled.
captured
Root path for pod namespace-separated signature policies.
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
None recorded. A mapped entry with no handoff is here for its foundation home.
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.