Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:02-crusible:08-compliance-and-authorization-operations:08-01-select-compliance-criteria-and-baselines [2026/08/01 07:22] – removed - external edit (Unknown date) 127.0.0.1 | dido:02-crusible:08-compliance-and-authorization-operations:08-01-select-compliance-criteria-and-baselines [2026/08/01 07:23] (current) – nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== 8.1 Select Compliance Criteria and Baselines ====== | ||
| + | [[dido: | ||
| + | |||
| + | Before performing a [[dido: | ||
| + | |||
| + | Crucible supports defined Compliance Baselines, including: | ||
| + | |||
| + | * DISA STIG Compliance Baselines | ||
| + | * FedRAMP Baseline Definitions | ||
| + | * Custom Compliance Frameworks | ||
| + | * Other Compliance Baselines represented through the supported baseline-definition capability | ||
| + | |||
| + | The selection establishes the criteria for the assessment. It does not independently determine which legal, regulatory, contractual, | ||
| + | |||
| + | ===== Identify the Assessment Subject ===== | ||
| + | |||
| + | The compliance operation identifies the subject to which the selected criteria apply. | ||
| + | |||
| + | An assessment subject can include: | ||
| + | |||
| + | * A Machine Image | ||
| + | * A Container Image | ||
| + | * An Infrastructure Configuration | ||
| + | * An Infrastructure Environment | ||
| + | * A deployed resource | ||
| + | * Another identified artifact supported by the applicable Compliance Baseline | ||
| + | |||
| + | The subject remains identifiable by the information needed to distinguish it from another artifact, resource, environment, | ||
| + | |||
| + | ===== Identify the Applicable Compliance Obligations ===== | ||
| + | |||
| + | The responsible organization determines the compliance obligations applicable to the assessment subject. | ||
| + | |||
| + | Those obligations can derive from: | ||
| + | |||
| + | * Organizational security policy | ||
| + | * A government security program | ||
| + | * A regulatory obligation | ||
| + | * A contractual obligation | ||
| + | * A deployment-environment requirement | ||
| + | * A Security Domain policy | ||
| + | * An approved custom compliance framework | ||
| + | |||
| + | Crucible does not independently decide which obligation governs the subject. | ||
| + | |||
| + | ===== Select a Compliance Baseline ===== | ||
| + | |||
| + | The compliance operation selects a Compliance Baseline that represents the criteria applicable to the identified subject. | ||
| + | |||
| + | The selected Compliance Baseline identifies: | ||
| + | |||
| + | * The Baseline | ||
| + | * The Baseline revision | ||
| + | * The Baseline source | ||
| + | * The included compliance criteria | ||
| + | * The subject or subject type to which the Baseline applies | ||
| + | * Applicable profiles, parameters, or tailoring information | ||
| + | * The compliance framework represented by the Baseline | ||
| + | |||
| + | The assessment uses the identified Baseline revision rather than an unspecified or changing set of criteria. | ||
| + | |||
| + | ===== DISA STIG Compliance Baselines ===== | ||
| + | |||
| + | Crucible supports Compliance Baselines based on Defense Information Systems Agency Security Technical Implementation Guides. | ||
| + | |||
| + | A selected DISA STIG Compliance Baseline identifies the STIG content and revision applicable to the assessment subject. | ||
| + | |||
| + | Support for a DISA STIG Compliance Baseline does not establish that: | ||
| + | |||
| + | * Every STIG applies to the subject | ||
| + | * Every STIG criterion can be evaluated by the selected assessment tool | ||
| + | * The subject satisfies the selected STIG | ||
| + | * An exception or deviation has been approved | ||
| + | * The subject has received operational authorization | ||
| + | |||
| + | The applicable organization determines the selected STIG, tailoring, exceptions, and acceptance process. | ||
| + | |||
| + | ===== FedRAMP Baseline Definitions ===== | ||
| + | |||
| + | Crucible supports definitions representing applicable FedRAMP Baselines. | ||
| + | |||
| + | The selected definition identifies the FedRAMP Baseline and revision used to organize or relate the applicable compliance criteria. | ||
| + | |||
| + | Support for a FedRAMP Baseline Definition does not grant FedRAMP authorization or establish that the complete system satisfies FedRAMP requirements. | ||
| + | |||
| + | ===== Custom Compliance Frameworks ===== | ||
| + | |||
| + | Crucible supports organization-defined or otherwise approved custom compliance frameworks. | ||
| + | |||
| + | A custom compliance framework can represent criteria not completely addressed by a predefined Compliance Baseline. | ||
| + | |||
| + | The custom framework identifies: | ||
| + | |||
| + | * The framework | ||
| + | * The framework revision | ||
| + | * The governing source or organization | ||
| + | * The included compliance criteria | ||
| + | * The subjects to which the framework applies | ||
| + | * Applicable parameters or tailoring information | ||
| + | |||
| + | A custom framework remains a controlled compliance definition rather than an undocumented collection of assessment checks. | ||
| + | |||
| + | ===== Select the Applicable Criteria ===== | ||
| + | |||
| + | The selected Compliance Baseline can contain more criteria than apply to a particular subject or assessment activity. | ||
| + | |||
| + | The responsible organization identifies the applicable criteria and any approved: | ||
| + | |||
| + | * Profiles | ||
| + | * Parameters | ||
| + | * Tailoring decisions | ||
| + | * Exceptions | ||
| + | * Exclusions | ||
| + | * Alternative criteria | ||
| + | |||
| + | Crucible preserves the selected baseline and criteria as inputs to the subsequent Compliance Assessment. | ||
| + | |||
| + | An exclusion from the selected assessment does not by itself establish an approved compliance exception or risk acceptance. | ||
| + | |||
| + | ===== Selection Result ===== | ||
| + | |||
| + | The selection result identifies: | ||
| + | |||
| + | * The assessment subject | ||
| + | * The selected Compliance Baseline | ||
| + | * The Baseline revision | ||
| + | * The represented compliance framework | ||
| + | * The applicable compliance criteria | ||
| + | * Applicable parameters or tailoring information | ||
| + | * The source of the selected Baseline | ||
| + | * Any approved exception or exclusion reference provided as an assessment input | ||
| + | |||
| + | The selected criteria and Compliance Baseline become controlled inputs to [[dido: | ||
| + | |||
| + | ===== Requirements Addressed ===== | ||
| + | |||
| + | ^ Requirement ^ Statement ^ | ||
| + | | [[dido: | ||
| + | | [[dido: | ||
| + | | [[dido: | ||
| + | | [[dido: | ||
| + | |||
| + | The linked leaf requirement pages remain the canonical sources. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||