MO-007b — Disconnected Environment Operation [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.
====== MO-007b — Disconnected Environment Operation ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:start|Go to MO-007 — Connected, Disconnected, and Air-Gapped Operation]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL perform testing operations in a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] without an active [[dido:99_annexes:annex-b-terms-and-definitions:e:external_network_connection|External Network Connection]].

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

MO-007b derives from [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:start|MO-007 — Connected, Disconnected, and Air-Gapped Operation]].

MO-007b specifies the Disconnected Environment portion of MO-007.

===== Rationale =====

A Disconnected Environment operates without active external network connectivity during testing operations.

Disconnected Environment operation requires DIDO-TE to conduct tests without relying upon an active External Network Connection or an [[dido:99_annexes:annex-b-terms-and-definitions:e:external_service|External Service]]. Required testing artifacts, dependencies, configurations, test data, policies, and other resources must therefore exist within the environment before test execution begins.

Authorized transfer processes introduce required resources into the environment and remove [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]], logs, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] after test execution. Applicable controls preserve the integrity, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] of transferred content.

A Disconnected Environment differs from an [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]]. A Disconnected Environment lacks active external network connectivity during the applicable operation, while an Air-Gapped Environment maintains physical isolation from external networks.

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

MO-007b applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definitions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solutions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test execution]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:external_network_connection|External Network Connections]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:external_service|External Services]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundles]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] [[dido:99_annexes:annex-b-terms-and-definitions:o:operating_procedure|Operating Procedures]]

===== Verification =====

Verification confirms that:

  - DIDO-TE performs testing operations in a Disconnected Environment
  - No active External Network Connection exists during test execution
  - Test execution does not depend upon an External Service
  - The resources required by the Test Definition exist within the Disconnected Environment before test execution begins
  - Authorized transfer processes introduce required testing artifacts and dependencies into the Disconnected Environment
  - Authorized transfer processes remove Test Results, logs, and Evidence from the Disconnected Environment
  - Transfer controls preserve the integrity, provenance, and Traceability of transferred content
  - The Evidence identifies the Disconnected Environment and records the connectivity conditions applicable during test execution

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

The following pages reference this requirement:

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

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

<todo>Assign the delivery phase for MO-007b.</todo>

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

<todo>Record the implementation status of MO-007b after reviewing the implementation plan.</todo>

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

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

----

===== Issues =====

<todo>Confirm the testing operations included within the scope of Disconnected Environment operation.</todo>

<todo>Define how DIDO-TE verifies the absence of active External Network Connections during test execution.</todo>

<todo>Identify the authorized processes for transferring resources into and Test Results, logs, and Evidence out of a Disconnected Environment.</todo>

<todo>Determine whether Transfer Bundle preparation, validation, introduction, and removal require separate derived requirements beneath MO-007b.</todo>

<todo>Determine how DIDO-TE identifies and records dependencies upon External Services before disconnected test execution.</todo>

<todo>Confirm that MO-007b, together with MO-007a and MO-007c, preserves the complete approved intent of MO-007.</todo>

----

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

Use the following code to reference the Statement section from another wiki page:

<code dokuwiki>
{{section>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:mo-007b#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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