Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Compliance Baseline ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Compliance Baseline is a [[public: | ||
| + | |||
| + | The Compliance Baseline establishes the controlled reference against which compliance findings and evidence are assessed. | ||
| + | |||
| + | A Compliance Baseline may identify a benchmark version, a selected profile, a control set, tailoring decisions, exceptions, a remediation policy, an assessment method, an evidence format, and an applicable operating context. | ||
| + | |||
| + | Within Crucible, a Compliance Baseline may apply to an image build, infrastructure deployment, [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from compliance management, security engineering, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Compliance Baseline differs from a [[public: | ||
| + | |||
| + | Changing a benchmark version, a selected profile, a tailoring decision, an exception, or a remediation policy may require a new Compliance Baseline. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Compliance Baseline identifies a specific DISA [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||