====== MO-001e — Compliance Baseline Conformance ====== [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:start|Go to MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments]] ===== Statement ===== [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL create an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] that conforms to the selected [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline|Compliance Baseline]]. ===== Derived From ===== This requirement derives from: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:start|MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments]] The Original Requirement states: > //Crucible SHALL enable rapid creation of repeatable, compliant, and secure infrastructure environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] MO-001e preserves the portion of the Original Requirement that characterizes Infrastructure Environments as **compliant** by requiring each created Infrastructure Environment to conform to the selected Compliance Baseline. The separate requirements derived from MO-001 address: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:mo-001a|MO-001a — Infrastructure Environment Creation]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:mo-001b|MO-001b — Deployment Duration]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:mo-001c|MO-001c — Reproducibility]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:mo-001d|MO-001d — Security Baseline Conformance]] ===== Rationale ===== The word **compliant** does not establish an objective compliance obligation unless a controlling Compliance Baseline identifies the requirements and conformance criteria used for evaluation. The selected [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline|Compliance Baseline]] provides the controlled compliance requirements against which the created Infrastructure Environment is evaluated. Compliance Baseline conformance supports: * Consistent application of compliance requirements * Objective evaluation of the created Infrastructure Environment * Identification of unmet or incorrectly implemented requirements * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] generation * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] * Independent review of compliance outcomes Separating Compliance Baseline conformance from Infrastructure Environment creation permits Crucible to create an Infrastructure Environment while independently passing or failing the compliance requirement. This requirement does not establish a deployment-duration threshold, reproducibility criterion, or [[dido:99_annexes:annex-b-terms-and-definitions:s:security_baseline|Security Baseline]]. The other requirements derived from MO-001 address those outcomes. ===== Applies To ===== This requirement applies to: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline|Compliance Baselines]] * Compliance requirements * Compliance evaluation * Compliance findings * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configurations]] * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] ===== Verification ===== Verification confirms that: - The selected [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline|Compliance Baseline]] is identified - The Compliance Baseline identifies the compliance requirements and conformance criteria used for evaluation - The created [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] is evaluated against the selected Compliance Baseline - Each required compliance requirement is evaluated - The created Infrastructure Environment satisfies the conformance criteria defined by the selected Compliance Baseline - Any compliance finding is identified and associated with the affected compliance requirement - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the selected Compliance Baseline, the evaluated compliance requirements, the created Infrastructure Environment, and the evaluation result ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:02-crusible}} ===== Delivery Phase ===== Implemented and Verified ===== Implementation Status ===== Assess whether the current Crucible implementation creates Infrastructure Environments that conform to the selected Compliance Baseline. ===== Requirement Status ===== Review and accept MO-001e as a proposed derived requirement created from the evaluation and decomposition of MO-001 in the Crucible System Requirements Specification, Version 1.1 Draft. ---- ===== Issues ===== The following unresolved issues affect this requirement: Identify the controlling source that selects the Compliance Baseline for each Infrastructure Environment. Identify the compliance requirements and conformance criteria that determine Compliance Baseline conformance. Define how exceptions, deviations, waivers, and compensating measures affect Compliance Baseline conformance. Define whether an Infrastructure Environment with unresolved compliance findings can satisfy this requirement. ---- ===== Notes for Editors ===== This requirement page should retain the stable requirement identifier ''MO-001e''. This page is a leaf requirement page and omits a trailing '':start'' from its namespace. The parent MO-001 page is a non-leaf page and retains a trailing '':start'' in its namespace. Changes to the Statement should preserve: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor * Creation of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the required outcome * The selected [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline|Compliance Baseline]] as the controlling compliance source * Conformance to the selected Compliance Baseline as the required compliance outcome The unresolved Compliance Baseline selection and conformance criteria should remain recorded in the Issues section until a controlling source resolves them. Material changes should receive review and should update the verification criteria, source records, and Issues section. To reference this requirement Statement from another wiki page, insert: {{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:mo-001e#Statement&noheader&nofooter&noeditbtn}} Do not rename this page after an external citation unless a redirect or move plan is in place. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.