Differences

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

--- public:99_annexes:annex-b-terms-and-definitions:i:image_baseline [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1
+++ public:99_annexes:annex-b-terms-and-definitions:i:image_baseline [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Image Baseline ======
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+An Image Baseline is a [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] that identifies the controlled inputs, definitions, dependencies, configuration, hardening, compliance settings, and build processes used to produce a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]].
+The Image Baseline may identify installation media, operating-system version, processor architecture, partitioning, filesystems, packages, provisioning roles, security settings, compliance profiles, source revisions, and build-tool versions.
+An Image Baseline defines how an image is reproduced. The resulting Machine Image is an artifact produced from that Baseline rather than the Baseline itself.
+Within Crucible, an Image Baseline may serve as a source layer in a [[public:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] and may support multiple provider-specific image realizations.
+===== Definition =====
+//[[public:99_annexes:annex-b-terms-and-definitions:b:baseline|baseline]] that identifies the controlled inputs, definitions, dependencies, configuration, hardening, compliance settings, and build processes used to produce a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]]//
+===== Source =====
+Generalized from machine-image engineering, configuration management, infrastructure automation, and reproducible-build usage and specialized for the Crucible architecture and operational model.
+===== Note =====
+An Image Baseline differs from a Machine Image. The Image Baseline defines the controlled configuration and process, while the Machine Image is a realized build artifact.
+Changes to operating-system media, packages, provisioning logic, hardening settings, or compliance settings may require a new Image Baseline.
+===== Example =====
+An Image Baseline identifies the [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 installation medium, required packages, Packer configuration, Ansible roles, STIG profile, remediation setting, processor architecture, and pinned source revisions used to produce a hardened guest image.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>