====== MO-007 — Connected, Disconnected, and Air-Gapped Operation ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]]

===== Original Requirement =====

> //[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL support testing operations in [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]], [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]], and [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]].//

===== Assessment of Original Requirement =====

The Original Requirement preserves the approved intent that DIDO-TE conduct testing operations in three types of environment, but it combines three independently testable normative obligations.

The following Specification Discipline and Authoring findings apply:

  * **Support** is a weak verb that does not identify an observable DIDO-TE behavior
  * **Testing operations** does not identify the operations DIDO-TE performs within each environment type
  * The requirement combines operation in Connected Environments, Disconnected Environments, and Air-Gapped Environments
  * The requirement does not identify the distinct connectivity, isolation, transfer, execution, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] obligations associated with each environment type
  * A single verification result could obscure failure to operate in one or more required environment types

The Original Requirement identifies:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]]

The decomposition treats operation in each environment type as a separate obligation so that DIDO-TE behavior can be specified and verified independently.

The three environment types impose different constraints upon:

  * Access to external networks and services
  * Introduction of testing artifacts and dependencies
  * Transfer of [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundles]]
  * Configuration and execution of tests
  * Collection and removal of Test Results
  * Collection and preservation of logs and Evidence
  * Integrity, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
  * Application of security and authorization controls

The Original Requirement does not identify which testing operations apply to all three environment types or which environment-specific operations require separate treatment.

The Original Requirement therefore requires:

  * Replacement of **support** with observable DIDO-TE behaviors
  * Identification of the testing operations required within each environment type
  * Separation of the three independently testable environment obligations
  * Identification of the transfer controls applicable to Disconnected and Air-Gapped Environments
  * Identification of the connectivity and external-service dependencies permitted within each environment type
  * Confirmation that the derived requirements collectively preserve the complete intent of MO-007

The decomposition preserves ''MO-007'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

===== Proposed Statements =====

The Original Requirement is decomposed into the following proposed replacement requirements:

{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007#1|js navbar nocookie maxjs#1 id#dido_te_mo_007_requirements_nav}}

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

<todo>Review and approve the decomposition of MO-007 into separate Connected Environment, Disconnected Environment, and Air-Gapped Environment requirements.</todo>

<todo>Determine whether MO-007a through MO-007c collectively supersede MO-007.</todo>

<todo>If MO-007a through MO-007c are accepted as the complete replacement for MO-007, mark MO-007 as superseded and preserve this page as the parent Traceability record.</todo>

----

===== Issues =====

The following unresolved issues affect the decomposition of MO-007:

<todo>Confirm the controlling source statement and citation for MO-007.</todo>

<todo>Confirm the titles and scope of MO-007a, MO-007b, and MO-007c.</todo>

<todo>Identify the testing operations DIDO-TE performs in each environment type.</todo>

<todo>Determine which testing operations apply uniformly across Connected, Disconnected, and Air-Gapped Environments.</todo>

<todo>Determine whether transfer operations require separate derived requirements beneath MO-007b and MO-007c.</todo>

<todo>Determine whether MO-007a through MO-007c provide complete coverage of the approved intent of MO-007.</todo>

----

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

This page should retain the stable parent requirement identifier ''MO-007''.

This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace.

The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces.

This page preserves:

  * The Original Requirement
  * The assessment of the Original Requirement
  * The reason for decomposition
  * Traceability to the proposed replacement requirements
  * The unresolved cross-cutting issues affecting the decomposition
  * The supersession decision

The proposed child requirements are:

  * ''MO-007a — Connected Environment Operation''
  * ''MO-007b — Disconnected Environment Operation''
  * ''MO-007c — Air-Gapped Environment Operation''

The Original Requirement should not be marked as superseded until the requirement owner:

  * Approves the three child requirements
  * Confirms that the child requirements collectively preserve the complete approved intent of MO-007
  * Confirms that each required testing operation has been allocated to one or more child requirements
  * Confirms that no additional child requirements are required

After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.

Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.

The non-leaf page namespace is:

<code>
dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:start
</code>

----

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