public:99_annexes:annex-b-terms-and-definitions:i:image_verification

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:i:image_verification [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:i:image_verification [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Image Verification ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Image Verification is the process of determining whether a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] satisfies specified identity, integrity, authenticity, provenance, compatibility, or approval criteria.
 +
 +The process may compare cryptographic digests, validate digital signatures, inspect an [[public:99_annexes:annex-b-terms-and-definitions:i:image_record|Image Record]], confirm source revisions, evaluate provenance, check provider registration, or compare image characteristics with declared requirements.
 +
 +Image Verification may occur after a build, before upload, after provider conversion, before promotion, before deployment, or after transfer across an [[public:99_annexes:annex-b-terms-and-definitions:a:air_gap|Air Gap]].
 +
 +Within Crucible, Image Verification supports controlled image lifecycle management and helps ensure that a deployment uses the intended image artifact.
 +
 +===== Definition =====
 +
 +//process of determining whether a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] satisfies specified identity, integrity, authenticity, provenance, compatibility, or approval criteria//
 +
 +===== Source =====
 +
 +Generalized from artifact verification, digital-signature validation, configuration management, software supply-chain security, and machine-image governance usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Image Verification evaluates specified criteria. It does not imply that every possible security, compliance, operational, or functional property has been evaluated.
 +
 +Verification of a signature establishes only the properties supported by the applicable signature, certificate, key, and trust policy.
 +
 +===== Example =====
 +
 +Before deploying a [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 Capability Image, Crucible verifies its digest, validates its signature, confirms its recorded source revisions, and checks that its Image Record satisfies the deployment’s Image Requirements.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>