C.3.6 Compliance Management [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== C.3.6 Compliance Management ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]]

The Compliance Management [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] define how [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] represents compliance baselines, invokes compliance-scanning tools through an operating-system-independent abstraction, records [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Findings]], produces compliance reports and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], and transfers applicable findings with the [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] they describe.

Together, these requirements establish repeatable [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_assessment|Compliance Assessment]] behavior that contributes to compliance consistency, [[dido:99_annexes:annex-b-terms-and-definitions:a:auditability|Auditability]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].

===== Contents =====

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management#1|js navbar nocookie maxjs#1 id#crucible_compliance_management_requirements_nav}}

===== Notes for Editors =====

The individual requirement pages should retain the stable identifiers ''FR-COMP-001'' through ''FR-COMP-010''.

Individual requirement pages are leaf nodes and should not include a trailing '':start'' in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should identify the applicable compliance criteria, assessed subject, assessment operation, [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Finding]], report, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] result.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should use the wiki Backlinks function rather than a manually maintained list.

To reference a requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
</code>

Replace ''<namespace>'' with the namespace of the requirement leaf page.

The section name following ''#'' SHALL match the section heading verbatim on the requirement page.

Do not rename a requirement page after an external citation unless a redirect or move plan is in place.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>