dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-008:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-008:start [2026/07/30 07:34] – removed - external edit (Unknown date) 127.0.0.1dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-008:start [2026/07/30 13:32] (current) – nick_dido
Line 1: Line 1:
 +====== FR-COMP-008 — Operating-System-Independent Compliance Scanning ======
  
 +[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:start|Go to Crucible Compliance Management Requirements]]
 +
 +===== Original Requirement =====
 +
 +> //The system shall provide an operating-system-agnostic compliance scanning abstraction. Compliance scanning shall not be limited to a single operating system (the current OpenSCAP/RHEL-9 integration is one concrete provider behind this abstraction).//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
 +
 +===== Assessment of Original Requirement =====
 +
 +The Original Requirement contains two distinct normative obligations:
 +
 +  - Provision of a compliance scanning abstraction
 +  - Compliance scanning across more than one operating system
 +
 +These obligations require separate verification and therefore should be represented by separate leaf requirements.
 +
 +The parenthetical reference to the current OpenSCAP and RHEL 9 integration identifies an implementation example. It does not establish an additional normative obligation and should not appear in a child requirement Statement.
 +
 +The phrase **operating-system-agnostic** is replaced with **operating-system-independent** to align the requirement title and avoid implying complete absence of operating-system-specific implementation components.
 +
 +===== Contents =====
 +
 +{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:fr-comp-008#1|js navbar nocookie maxjs#1 id#fr_comp_008_nav}}
 +
 +===== Requirement Status =====
 +
 +<todo>Review and approve the decomposition of FR-COMP-008.</todo>
 +
 +<todo>Create and approve FR-COMP-008a.</todo>
 +
 +<todo>Create and approve FR-COMP-008b.</todo>
 +
 +----
 +===== Issues =====
 +
 +<todo>Determine whether Compliance Scanning Abstraction requires a controlled definition in the shared Terms and Definitions corpus.</todo>
 +
 +<todo>Determine whether Operating System requires a controlled definition in the shared Terms and Definitions corpus.</todo>
 +
 +<todo>Determine whether the minimum of two operating systems accurately expresses the intended portability threshold.</todo>
 +
 +----
 +===== Notes for Editors =====
 +
 +This page is a non-leaf requirement page and therefore retains a trailing '':start'' in its namespace.
 +
 +The child requirements are leaf pages and omit a trailing '':start'' from their namespaces.
 +
 +The OpenSCAP and RHEL 9 reference describes one implementation of the abstraction and does not create a requirement to use either technology.
 +
 +Do not add requirements for dynamic provider loading, plugin discovery, provider registration, common result formats, or automatic operating-system detection unless the controlling source adds those obligations.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>