NOD-003f — Record Node Configuration

Go to NOD-003 — Configure a Node

The DIDO-TE SHALL record the actual Node Configuration of each configured Node.

• NOD-003 — Configure a Node
• NOD-003a — Select the Node Configuration
• NOD-003b — Resolve Node Configuration Values
• NOD-003c — Apply the Node Configuration
• NOD-003d — Establish Node Bindings
• [DTE5] DIDO-TE Requirements Register, source requirement identifier and obligation to be assigned
• [DTE6] Structured Information Processing Reference Architecture (SIP-RA)
• [DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

A Node Configuration record identifies the configuration actually applied to a Node rather than only the configuration selected or intended for application.

The record captures the Node Configuration identity and version, resolved Configuration Values, established Node Bindings, configuration operations, responsible authority, time, resulting state, findings, and approved exceptions.

The record distinguishes an intended Node Configuration from the actual state of the configured Node. This distinction supports comparison, validation, reproduction, diagnosis, audit, and evaluation of subsequent Test Results.

Sensitive Configuration Values require protected recording. The record identifies their existence, source, use, and integrity without unnecessarily disclosing the values.

An incomplete, inaccurate, mutable, or untraceable Node Configuration record prevents the DIDO-TE from demonstrating which configuration governed a Test Execution.

• DIDO-TE
• Node
• Node Definition
• Node Implementation
• Node Configuration
• Configuration Value
• Node Binding
• Configuration Application
• Test Environment
• Test Execution
• Evidence
• Traceability

Verification confirms that:

• Each Node Configuration record has a unique identity.
• Each Node Configuration record identifies the applicable Node instance.
• Each Node Configuration record identifies the applicable Node Definition and Node Implementation.
• Each Node Configuration record identifies the selected Node Configuration and its version.
• Each Node Configuration record distinguishes the intended Node Configuration from the actual Node Configuration.
• Each Node Configuration record identifies the Configuration Procedure used to apply the Node Configuration.
• Each Node Configuration record identifies each resolved Configuration Value or an authorized protected reference to it.
• Each Node Configuration record identifies each established Node Binding.
• Each Node Configuration record identifies the responsible authority and the time of Configuration Application.
• Each Node Configuration record identifies the resulting configuration state.
• Each Node Configuration record identifies any difference between the intended and actual Node Configuration.
• Each Node Configuration record identifies applicable findings, warnings, errors, exceptions, and recovery actions.
• Each approved exception identifies its authority, rationale, scope, duration, and expected effect.
• The DIDO-TE protects Sensitive Configuration Values from unauthorized disclosure.
• The DIDO-TE preserves sufficient information to verify the integrity and authorized use of a Sensitive Configuration Value without recording the exposed value.
• The DIDO-TE detects an incomplete, inconsistent, altered, ambiguous, duplicate, or unauthorized Node Configuration record.
• A material Node Configuration change produces a distinguishable Node Configuration record and revision.
• The DIDO-TE preserves the applicable Node Configuration record for the retention period governing the Test Execution and its Evidence.
• The DIDO-TE associates the applicable Node Configuration record with each Test Execution performed by the configured Node.
• The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, selected Node Configuration, resolved Configuration Values, Node Bindings, Configuration Application, actual Node Configuration, Test Environment, Test Execution, findings, exceptions, and resulting Evidence.
• A missing, incomplete, inaccurate, unauthorized, altered, ambiguous, or untraceable Node Configuration record constitutes nonconformance with this requirement.

Verification includes:

• Inspection of the Node Configuration record and its unique identity
• Comparison of the selected Node Configuration with the actual Node Configuration
• Inspection of recorded Configuration Values and protected references
• Inspection of recorded Node Bindings
• Inspection of the responsible authority, Configuration Procedure, operations, and timing
• Inspection of findings, exceptions, differences, and resulting configuration state
• Confirmation of controls protecting Sensitive Configuration Values
• Confirmation that a material configuration change produces a distinguishable revision
• Confirmation that each applicable Test Execution references the governing Node Configuration record
• A negative assessment involving an incomplete Node Configuration record
• A negative assessment involving an altered or unauthorized Node Configuration record
• Inspection of retention, Evidence, and Traceability records

• Add links to the architecture sections governing Node Configuration, Configuration Application, Node Bindings, configuration records, Sensitive Configuration Values, Evidence, and Traceability.

Assign the applicable delivery phase.

Draft

Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-003-configure-a-node:nod-003f-record-node-configuration#Statement&noheader&nofooter&noeditbtn}}