NOD-006 — Isolate a Node [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.
====== NOD-006 — Isolate a Node ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:start|Go to Node Requirements]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL isolate a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] when a condition specified by the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] requires isolation.

===== Derived From =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-006|[DTE6] Structured Information Processing Reference Architecture (SIP-RA)]]
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-007|[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)]]

===== Rationale =====

Node isolation prevents an identified Node from exchanging data, control, services, or resources through interactions prohibited by the applicable Test Definition.

The Test Definition identifies the conditions that require isolation, the required isolation scope, the interactions permitted during isolation, the responsible authority, and the conditions required for release. The applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_procedure|Test Procedure]] identifies the actions used to isolate and release the Node.

Conditions requiring isolation include an invalid lifecycle state, unsuccessful validation, loss of readiness, unauthorized interaction, unexpected behavior, compromised security, incorrect [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]], invalid [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Binding]], resource misuse, or an unresolved [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exception]].

Isolation restricts or terminates selected Node Bindings, interfaces, services, processes, data flows, control paths, credentials, or access to [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resources]]. The isolation scope protects affected Test Executions without unnecessarily affecting unrelated Nodes, Test Resources, or Test Environments.

Isolation differs from stopping a Node. A stopped Node occupies a defined non-operating state. An isolated Node remains available for authorized observation, diagnosis, evidence collection, remediation, recovery, or controlled stopping while prohibited interactions remain restricted.

Controlled isolation preserves the Node state and information required to determine the cause, scope, and effect of the triggering condition. It also prevents the condition from affecting other Nodes, Test Resources, Test Results, or Test Environments.

===== Applies To =====

  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Binding]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependency]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_procedure|Test Procedure]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution_exception|Test Execution Exception]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:authorizing_authority|Authorizing Authority]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Verification =====

Verification confirms that:

  - The applicable Test Definition identifies each condition that requires Node isolation.
  - Each identified condition specifies the required isolation scope, permitted interactions, responsible authority, and release conditions.
  - The applicable Test Procedure identifies the actions required to isolate and release the Node.
  - The DIDO-TE detects when a Node satisfies an identified condition requiring isolation.
  - The DIDO-TE uniquely identifies the Node subject to isolation.
  - The DIDO-TE identifies the affected Test Environment and Test Executions.
  - The DIDO-TE identifies the lifecycle and execution states of the Node before isolation.
  - The DIDO-TE verifies the identity of the target Node before applying isolation controls.
  - The DIDO-TE determines which Node Bindings, interfaces, services, processes, data flows, control paths, credentials, Dependencies, and Test Resources require restriction.
  - The DIDO-TE applies the isolation actions specified by the applicable Test Procedure.
  - The DIDO-TE prevents the isolated Node from initiating or receiving prohibited interactions.
  - The DIDO-TE preserves interactions authorized for observation, diagnosis, evidence collection, remediation, recovery, or controlled stopping.
  - The DIDO-TE prevents isolation controls from unnecessarily affecting unrelated Nodes, Test Resources, Test Environments, or Test Executions.
  - The DIDO-TE verifies the completion and effectiveness of each material isolation action.
  - The DIDO-TE detects an incomplete, unsuccessful, interrupted, bypassed, incorrectly scoped, or unauthorized isolation action.
  - The DIDO-TE detects a prohibited interaction attempted by or directed to the isolated Node.
  - The DIDO-TE identifies interactions that occurred between detection of the isolation condition and effective isolation.
  - The DIDO-TE determines the effect of isolation on affected Test Inputs, observations, outputs, Test Resources, Test Executions, and Test Results.
  - The DIDO-TE preserves the Node state, configuration, logs, observations, and other information required for diagnosis and Evidence.
  - The DIDO-TE assigns a distinguishable isolation status to the Node.
  - The DIDO-TE prevents an isolated Node from resuming prohibited interactions before satisfaction of the applicable release conditions.
  - The DIDO-TE verifies the Node Configuration, Node Bindings, lifecycle state, validation status, and readiness status before releasing the Node.
  - The DIDO-TE obtains approval from the applicable Authorizing Authority when the Test Definition or Test Procedure requires approval before release.
  - An unsuccessful isolation leaves the Node in a known state or identifies the actual resulting state and required corrective or escalation action.
  - The DIDO-TE records the Node identity, triggering condition, responsible authority, Test Procedure, source state, isolation scope, restrictions, actions, timing, resulting state, findings, exceptions, affected Test Executions, and release status.
  - The DIDO-TE maintains Traceability among the triggering condition, Node Definition, Node Implementation, Node Configuration, Node Bindings, Test Definition, Test Procedure, isolation actions, Test Environment, affected Test Executions, Test Results, release decision, and resulting Evidence.
  - A missing, delayed, incomplete, ineffective, bypassed, incorrectly scoped, unauthorized, prematurely released, or untraceable Node isolation constitutes nonconformance with this requirement.

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:03-dido-te}}

===== Delivery Phase =====

<todo>Assign the applicable delivery phase.</todo>

===== Implementation Status =====

<todo>Assign the implementation status.</todo>

===== Requirement Status =====

<todo>The proposed derived requirement requires review and acceptance.</todo>

----

===== Issues =====

<todo>Assign the source requirement identifier and obligation from the DIDO-TE Requirements Register.</todo>

----

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

Use the following DokuWiki section-transclusion syntax to reference this requirement’s Statement section:

<code dokuwiki>
{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-006-isolate-a-node#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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