**Latest CCR Affecting this Ticket:** (for database administrator use
only)\
**Latest CCR DATE Affecting this Ticket:** (for database administrator
use only)

Ticket: SD_A8_01 (With L4 Mappings)

Secure Distribution of Subscriptions

+-------------------------------+----+---------------------------------+
| **Launch Criticality:** 6A.08 |    | **Ticket CCR Number^\*^:** (for |
|                               |    | database administrator use      |
| **Review:** N/A               |    | only**)**                       |
|                               |    |                                 |
| **Priority:** N/A             |    | **Ticket CCR Date^\*^:** (for   |
|                               |    | database administrator use      |
| **Number of Tracked Ticket    |    | only)                           |
| Changes:** (for database      |    |                                 |
| administrator use only)       |    | \* Represents changes to        |
|                               |    | information from Ticket table   |
|                               |    | only. Does not include          |
|                               |    | information linked in from      |
|                               |    | other tables.                   |
+-------------------------------+----+---------------------------------+

  -----------------------------------------------------------------------
  NOTE: The number of tracked changes (above) represents the number of
  changes to this particular Ticket. Whenever the data appearing in this
  Ticket changes this number is incremented by 1.

  -----------------------------------------------------------------------

**External Interface Dependency:**

**Subsystem Dependency:**

NBSRV, DDIST, STMGT, DMS, DBDM, CSS, OMS,

**Preconditions:**

Configure the PVC and the VATC to simulate distribution between GSFC and
an external user at the OMI Dutch Processing System. The secure copy
media type should be incorporated into the GSFC regression test and
verified as part of this delivery. Thereafter, the GSFC regression test
and the EOC GSFC 24-hour workload test should include secure copy
subscriptions.

Reference document: 'Interface Control Document between the EOSDIS Core
System (ECS and the Science-Investigator-led Processing System (SIPS),
Volume 15, OMI Dutch Processing System (ODPS) , June 2003', ESDIS
document number 423-41-57-15. This SIPS volume documents the intent of
the ODPS to utilize the secure copy transport for its ECS subscriptions
(Table 4-4-1).

It should be noted that the OMI SIPS at GSFC has no plans at this time
to subscribe via secure copy, as documented in 'Interface Control
Document between the EOSDIS Core System (ECS and the
Science-Investigator-led Processing System (SIPS), Volume 13, OMI,
August 2003', ESDIS document number 423-41-57-13" (Figure 3-1).

Regression testing of Synergy III Order Manager capabilities that are
configurable by media type is included in the testing criteria. These
criteria will exercise the following Synergy III OMS capabilities:
suspend and resume requests of a specific media type, validate request
size limits in GB by media type, place on hold requests which exceed the
media capacity limit, configuration of target partition size by media
type. In addition, the bundling of secure copy subscriptions will be
including in the criteria.

**Differences from Previous Releases:**

::: Definition-Term
This ticket adds the secure copy service as a new media type accessible
via subscription. Secure copy will be similar to FTP Push distribution,
but will encrypt the destination hosts authentication information across
the interface.
:::

**Operations Concept:**

::: Definition-Term
The source of this capability is ESD 193, 'Secure Distribution
Capability', and ECS ROM 03-00021. AURA SIPS have requested an
additional distribution service, as an alternative to non-secure FTP
push or pull. The majority of the SIPS currently subscribe using FTP
pull actions. Data-driven processes at the user site typically run cron
scripts which detect the availability of data via Data Notification
email messages from DDIST. The DNs are then used as events to signal the
availability of data for FTP Pull, which subsequently trigger
user-developed scripts to initiate FTP Pull from ECS.
:::

::: Definition-Term
The AURA SIPS have requested that subscriptions provide a secure FTP
Push service, in order to mitigate DN email receipt errors in an
FTP-Pull scenario, and non-secure exchange of authentication information
in an FTP Push scenario. This ticket adds the secure copy service as a
new media type accessible via subscription.
:::

A secure copy service was added to STMGT as part of the secure Ingest
and secure PAN/PDRD capability developed for AURA SIPS and SORCE,
deployed as a patch on 6A.07, and rolled up in 6A.08. (See NCRs 36789
and 36418, both titled 'GDAAC/SMC: Request SCP2 functionality within
INS/STMGT') The service was implemented as scp over ssh, and was made
available only to SIPS interface via Ingest. STMGT developed a new
secure copy server, EcDsStCopyServer , which asynchronously processed
the FTP Pull of data from the SIPS site, and the secure Push of
PANs/PDRDs. It is recommended that the secure copy service be made
available for data distribution requests (see 'Design Directions').

**Operational Impact:**

DAACs will choose between F-secure or freeware ssh for its ssh
implementation, but will only configure one type for all of its secure
distributions. The F-secure scp media type will have an additional
option for distributing data with or without encryption of the data as
well as the authentication information. Operations will see 'scp'
displayed on GUIs for DDIST, OMS and MSS. A new error condition which
can suspend requests will exist when the destination for a secure
distribution request has not been configured correctly with either ssh
or F-secure.

**Transition Approach:**

::: Definition-Term
There are no special transition requirements for orders in process.
Backwards-compatible config patches will be required to add the new
media type to configuration and registry information.
:::

**Comments:**

ECS will certify operation of secure distribution using F-secure 3.2.3.
Users requesting secure distribution of ECS data must have, at a
minimum, F-secure 3.2.3 installed on their destination hosts. This
should be documented in either ICDs or operations agreements with the
SIPS data providers that plan to utilize secure subscriptions.

Note on Requirement S-OMS-01024: Synergy III mode is defined in Ticket
OD_S4_01. S-OMS-01024 augments the list of Synergy III exceptions found
in OD_S4_01. There should be little new coding required since OD_S4_01
specifies that the OMS should handle a configurable list of media types
as exceptions. It is an SY4 design decision whether the configuration is
done via script or OMS GUI.

**Level 3 Requirement(s):**

::: Definition-Term
None
:::

  --------- -------------------------------------- -------------- ------------- -------
  **L3 ID** **L3 Text**                            **Category**   **Release**   **CCR
                                                                                Num**

                                                                                
  --------- -------------------------------------- -------------- ------------- -------

**IRD Requirement(s):**

::: Definition-Term
None
:::

***Level 4 Requirement(s):***

+---------+----------------------------------------+--------+--------+
| **L4    | **L4 Text**                            | **Rel  | **CCR  |
| ID**    |                                        | ease** | Num**  |
+---------+----------------------------------------+--------+--------+
|         |                                        |        |        |
+---------+----------------------------------------+--------+--------+
| S-SS    | The NBSRV CI shall support a secure    | 6A.08  | NEW    |
| S-00311 | copy service for distribution of data. |        |        |
+---------+----------------------------------------+--------+--------+
| S-SS    | The NSBRV CI shall allow the operator  | 6A.08  | NEW    |
| S-00312 | to select secure copy distribution as  |        |        |
|         | a distribution action for a            |        |        |
|         | subscription.                          |        |        |
+---------+----------------------------------------+--------+--------+
| S-SS    | If secure copy distribution is         | 6A.08  | NEW    |
| S-00321 | selected, the NSBRV CI shall require   |        |        |
|         | the operator to enter or select values |        |        |
|         | for the following secure copy          |        |        |
|         | parameters:                            |        |        |
|         |                                        |        |        |
|         | (a) userid                             |        |        |
|         |                                        |        |        |
|         | (b) password                           |        |        |
|         |                                        |        |        |
|         | (c) host name                          |        |        |
|         |                                        |        |        |
|         | (d) destination directory name         |        |        |
+---------+----------------------------------------+--------+--------+
| S-SS    | The NSBRV CI shall allow the operator  | 6A.08  | NEW    |
| S-10126 | to select secure copy as a media type  |        |        |
|         | for a bundling order.                  |        |        |
+---------+----------------------------------------+--------+--------+
|         |                                        |        |        |
+---------+----------------------------------------+--------+--------+
| S-DS    | The SDSRV CI shall accept secure copy  | 6A.08  | NEW    |
| S-01866 | as a valid electronic media type in    |        |        |
|         | its acquire requests.                  |        |        |
+---------+----------------------------------------+--------+--------+
| S-DS    | The SDSRV CI shall direct the DDIST CI | 6A.08  | NEW    |
| S-01868 | to transmit data and metadata          |        |        |
|         | electronically, via secure copy, if    |        |        |
|         | specified by a valid Electronic        |        |        |
|         | Distribution Request.                  |        |        |
+---------+----------------------------------------+--------+--------+
|         |                                        |        |        |
+---------+----------------------------------------+--------+--------+
| S-DS    | The DDIST CI shall support electronic  | 6A.08  | NEW    |
| S-30648 | distribution of data using secure copy |        |        |
|         | in a configurable manner.              |        |        |
+---------+----------------------------------------+--------+--------+
| S-DS    | The DDIST CI shall accept secure copy  | 6A.08  | NEW    |
| S-30649 | as a valid electronic media type in    |        |        |
|         | its distribution requests.             |        |        |
+---------+----------------------------------------+--------+--------+
| S-DS    | The DDIST CI shall direct the transfer | 6A.08  | NEW    |
| S-30650 | of data to external file systems, via  |        |        |
|         | secure copy, as specified by the SDSRV |        |        |
|         | CI.                                    |        |        |
+---------+----------------------------------------+--------+--------+
|         |                                        |        |        |
+---------+----------------------------------------+--------+--------+
| S-OM    | The Order Management Service CI shall  | 6A.08  | NEW    |
| S-01023 | process secure copy distribution       |        |        |
|         | requests.                              |        |        |
+---------+----------------------------------------+--------+--------+
| S-OM    | The Order Management Service CI shall  | SY4    | NEW    |
| S-01024 | process secure copy distribution       |        |        |
|         | requests in Synergy III mode.          |        |        |
+---------+----------------------------------------+--------+--------+
| S-OM    | The Order Management GUI shall not     | 6A.08  | NEW    |
| S-03631 | allow an operator to edit a data       |        |        |
|         | distribution request whose MSS request |        |        |
|         | tracking status is \'Canceled\' or     |        |        |
|         | \'Cancelled\', \'Aborted\' or          |        |        |
|         | \'Abort\', or \'Shipped\' in the       |        |        |
|         | following way:                         |        |        |
|         |                                        |        |        |
|         | a\. Change the media type to secure    |        |        |
|         | copy                                   |        |        |
+---------+----------------------------------------+--------+--------+
|         |                                        |        |        |
+---------+----------------------------------------+--------+--------+
| S-DS    | The STMGT CI shall support secure      | 6A.08  | NEW    |
| S-22122 | electronic distribution of data.       |        |        |
+---------+----------------------------------------+--------+--------+
|         |                                        |        |        |
+---------+----------------------------------------+--------+--------+

L4 to L3 Mappings:

None

  ---------------------------- ---------------------------- --------------
  **L4 ID**                    **L3 ID**                    **CCR Num**

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            
  ---------------------------- ---------------------------- --------------

::: Definition-Term
**L4 to IRD Mappings:**
:::

None

**Design Directive(s):**

During the analysis of the secure SIPS Ingest NCRs, schedule and
resource constraints prohibited the development of a thread-safe sftp
class. Due to the relatively low volume of data to be ingested from the
AURA SIPS, it was feasible to implement secure copy over a secure shell
interface, and spawn the requests asynchronously as the new STMGT secure
copy server receives them.

ESD 193 originally envisioned a secure distribution option for MTMGW and
EDG users, as well for SIPS users. However, similar constraints on
schedule and resources resulted in ECS offering this capability for
subscriptions only. This prioritizes the immediate need for secure
distribution by the AURA SIPS users over the anticipated need from the
EDG and MTMGW. Development should re-use the STMGT EcDsStCopyServer
developed for SIPS Ingest but should also investigate potential
enhancements for improving concurrency, in anticipation of wider use by
the user community at-large. In addition, the rule-based DDIST dynamic
FTP server assignment capability can be utilized to allocate a pool of
secure copy servers between requests destined for the ODPS SIPS and
eventually EDG and MTMGW originators.

This capability will be added to the SSS/NBSRV but not the SBSRV.

***Criteria:***

+--------+--------+------------------------------------+------+-----+
| #      | #      | **Criteria Text**                  | **Ty | **  |
| Criter |  Crite |                                    | pe** | CCR |
| ia Key | ria ID |                                    |      | Nu  |
|        |        |                                    |      | m** |
+--------+--------+------------------------------------+------+-----+
|        | 10     | Establish source and destination   | FC   | NEW |
|        |        | environments that are on opposite  |      |     |
|        |        | sides of a firewall. Set up the    |      |     |
|        |        | secure copy environment for the    |      |     |
|        |        | EcDsStCopyServer for both AES and  |      |     |
|        |        | DES encryption using the F-Secure  |      |     |
|        |        | implementation of SSH. Configure a |      |     |
|        |        | destination to support AES         |      |     |
|        |        | encryption using the F-Secure      |      |     |
|        |        | implementation of SSH. Using the   |      |     |
|        |        | NBSRV GUI, register a subscription |      |     |
|        |        | with secure copy as the            |      |     |
|        |        | distribution media.                |      |     |
|        |        |                                    |      |     |
|        |        | Configure subscribed acquires to   |      |     |
|        |        | route through the SDSRV; set up    |      |     |
|        |        | the destination host/path such     |      |     |
|        |        | that the data will be pushed to a  |      |     |
|        |        | location outside the firewall.     |      |     |
|        |        |                                    |      |     |
|        |        | Trigger the subscription and       |      |     |
|        |        | verify that the event notification |      |     |
|        |        | is received from the NBSRV.        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the data notification  |      |     |
|        |        | email from DDIST displays the      |      |     |
|        |        | secure media type.                 |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the secure media type  |      |     |
|        |        | is visible from the following      |      |     |
|        |        | GUIs.                              |      |     |
|        |        |                                    |      |     |
|        |        | (a) DDIST GUI                      |      |     |
|        |        |                                    |      |     |
|        |        | (b) MSS GUI                        |      |     |
|        |        |                                    |      |     |
|        |        | ::: Definition-Term                |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
|        |        | :::                                |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 15     | Repeat criterion 10 but configure  | FC   | NEW |
|        |        | subscribed acquires to route       |      |     |
|        |        | through the OMS. Set up the        |      |     |
|        |        | destination host/path such that    |      |     |
|        |        | the data will be pushed to a       |      |     |
|        |        | location outside the firewall.     |      |     |
|        |        |                                    |      |     |
|        |        | Trigger the subscription and       |      |     |
|        |        | verify that the event notification |      |     |
|        |        | is received from the NBSRV.        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the data notification  |      |     |
|        |        | email from DDIST displays the      |      |     |
|        |        | secure media type.                 |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the secure media type  |      |     |
|        |        | is visible from the following      |      |     |
|        |        | GUIs.                              |      |     |
|        |        |                                    |      |     |
|        |        | (a) OMS GUI                        |      |     |
|        |        |                                    |      |     |
|        |        | (b) DDIST GUI                      |      |     |
|        |        |                                    |      |     |
|        |        | (c) MSS GUI                        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 18     | \[This criteria tests the OMS      |      | NEW |
|        |        | Synergy III capabilities to        |      |     |
|        |        | validate request size limits in GB |      |     |
|        |        | by media type, and place on hold   |      |     |
|        |        | those requests which exceed the    |      |     |
|        |        | media capacity limit\].            |      |     |
|        |        |                                    |      |     |
|        |        | Repeat Criterion 15 but configure  |      |     |
|        |        | a request size limit for secure    |      |     |
|        |        | copy in OMS. Trigger the           |      |     |
|        |        | subscription using a granule that  |      |     |
|        |        | will exceed the secure copy        |      |     |
|        |        | request limit.                     |      |     |
|        |        |                                    |      |     |
|        |        | (a) Verify that the request limit  |      |     |
|        |        |     is enforced and that the OMS   |      |     |
|        |        |     has placed the request on      |      |     |
|        |        |     hold.                          |      |     |
|        |        |                                    |      |     |
|        |        | (b) Verify that the operator can   |      |     |
|        |        |     resume the request.            |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 19     | \[This criteria tests the OMS and  | FC   | NEW |
|        |        | NBSRV Synergy III capabilities to  |      |     |
|        |        | bundle subscriptions, configure    |      |     |
|        |        | target partition size by media     |      |     |
|        |        | type, and partition a request      |      |     |
|        |        | which has been placed on hold.\]   |      |     |
|        |        |                                    |      |     |
|        |        | Using the NSBRV GUI, enter a       |      |     |
|        |        | bundling order for secure copy     |      |     |
|        |        | distribution, with a minimum       |      |     |
|        |        | bundle granule count that exceeds  |      |     |
|        |        | the configured request granule     |      |     |
|        |        | count limit for non subsetted      |      |     |
|        |        | requests. Observe the warning on   |      |     |
|        |        | the NBSRV GUI, confirm the value   |      |     |
|        |        | and complete the registration of   |      |     |
|        |        | the subscription.                  |      |     |
|        |        |                                    |      |     |
|        |        | Enter another bundling order for   |      |     |
|        |        | secure copy distribution, which    |      |     |
|        |        | does not exceed the granule count  |      |     |
|        |        | limit.                             |      |     |
|        |        |                                    |      |     |
|        |        | From the OMS GUI, configure a      |      |     |
|        |        | target partition size for secure   |      |     |
|        |        | copy requests.                     |      |     |
|        |        |                                    |      |     |
|        |        | Trigger several subscriptions      |      |     |
|        |        | sufficient to fill both bundled    |      |     |
|        |        | orders.                            |      |     |
|        |        |                                    |      |     |
|        |        | (a) Verify that the bundled order  |      |     |
|        |        |     that does not exceed request   |      |     |
|        |        |     limits is successfully         |      |     |
|        |        |     fulfilled.                     |      |     |
|        |        |                                    |      |     |
|        |        | (b) Verify that the bundled order, |      |     |
|        |        |     which exceeded request limits, |      |     |
|        |        |     is placed on hold in the OMS.  |      |     |
|        |        |                                    |      |     |
|        |        | (c) Verify that the operator can   |      |     |
|        |        |     intervene with a request to    |      |     |
|        |        |     partition the secure copy      |      |     |
|        |        |     request.                       |      |     |
|        |        |                                    |      |     |
|        |        | (d) Verify that the partitioned    |      |     |
|        |        |     order is dispatched using the  |      |     |
|        |        |     configured partition size for  |      |     |
|        |        |     secure copy.                   |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 20     | \[SYNERGY IV\] Repeat criterion 15 | FC   | NEW |
|        |        | but use a mode in which the        |      |     |
|        |        | Synergy IV OMS has been installed. |      |     |
|        |        | Configure subscribed acquires to   |      |     |
|        |        | route through the OMS. Configure   |      |     |
|        |        | the media types for OMS Synergy    |      |     |
|        |        | III processing mode to include     |      |     |
|        |        | secure copy. Set up the            |      |     |
|        |        | destination host/path such that    |      |     |
|        |        | the data will be pushed to a       |      |     |
|        |        | location outside the firewall.     |      |     |
|        |        |                                    |      |     |
|        |        | Trigger the subscription and       |      |     |
|        |        | verify that the event notification |      |     |
|        |        | is received from the NBSRV.        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the data notification  |      |     |
|        |        | email from DDIST displays the      |      |     |
|        |        | secure media type.                 |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the secure media type  |      |     |
|        |        | is visible from the following      |      |     |
|        |        | GUIs.                              |      |     |
|        |        |                                    |      |     |
|        |        | (a) OMS GUI. Verify that the       |      |     |
|        |        |     processing mode is Synergy     |      |     |
|        |        |     III.                           |      |     |
|        |        |                                    |      |     |
|        |        | (b) DDIST GUI                      |      |     |
|        |        |                                    |      |     |
|        |        | (c) MSS GUI                        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 30     | Repeat Criterion 10 but configure  | FC   | NEW |
|        |        | the destination to support DES     |      |     |
|        |        | encryption only. Ensure that the   |      |     |
|        |        | secure agent is running.           |      |     |
|        |        |                                    |      |     |
|        |        | (a) Using the NBSRV GUI, register  |      |     |
|        |        |     a subscription with secure     |      |     |
|        |        |     copy as the distribution type. |      |     |
|        |        |                                    |      |     |
|        |        | Configure subscribed acquires to   |      |     |
|        |        | route through the SDSRV; set up    |      |     |
|        |        | the destination host/path such     |      |     |
|        |        | that the data will be pushed to a  |      |     |
|        |        | location outside the firewall.     |      |     |
|        |        |                                    |      |     |
|        |        | Trigger the subscription and       |      |     |
|        |        | verify that the event notification |      |     |
|        |        | is received from the NBSRV.        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the data notification  |      |     |
|        |        | email from DDIST displays the      |      |     |
|        |        | secure media type.                 |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the secure media type  |      |     |
|        |        | is visible from the following      |      |     |
|        |        | GUIs.                              |      |     |
|        |        |                                    |      |     |
|        |        | (a) DDIST GUI                      |      |     |
|        |        |                                    |      |     |
|        |        | (b) MSS GUI                        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 40     | Repeat criterion 15 but configure  | FC   | NEW |
|        |        | the destination to support DES     |      |     |
|        |        | encryption only. Ensure that the   |      |     |
|        |        | secure agent is running.           |      |     |
|        |        |                                    |      |     |
|        |        | Trigger the subscription and       |      |     |
|        |        | verify that the event notification |      |     |
|        |        | is received from the NBSRV.        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the data notification  |      |     |
|        |        | email from DDIST displays the      |      |     |
|        |        | secure media type.                 |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the secure media type  |      |     |
|        |        | is visible from the following      |      |     |
|        |        | GUIs.                              |      |     |
|        |        |                                    |      |     |
|        |        | (a) OMS GUI                        |      |     |
|        |        |                                    |      |     |
|        |        | (b) DDIST GUI                      |      |     |
|        |        |                                    |      |     |
|        |        | (c) MSS GUI                        |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 50     | Force the suspension of a secure   | FC   | NEW |
|        |        | distribution request in DDIST.     |      |     |
|        |        | Verify that the operator can       |      |     |
|        |        | resume the secure copy request     |      |     |
|        |        | from the DDIST GUI.                |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 60     | \[This tests the Synergy III       | FC   | NEW |
|        |        | capability to suspend and resume   |      |     |
|        |        | requests by media type\]           |      |     |
|        |        |                                    |      |     |
|        |        | Submit several subscriptions that  |      |     |
|        |        | will route through to OMS, some    |      |     |
|        |        | with secure copy as the media      |      |     |
|        |        | type. Trigger the secure copy      |      |     |
|        |        | subscriptions. While the requests  |      |     |
|        |        | are in progress, suspend           |      |     |
|        |        | processing of all secure copy      |      |     |
|        |        | requests in OMS. Trigger several   |      |     |
|        |        | more secure copy distribution      |      |     |
|        |        | requests.                          |      |     |
|        |        |                                    |      |     |
|        |        | (a) Verify that all secure copy    |      |     |
|        |        |     orders have been suspended,    |      |     |
|        |        |     both old and new.              |      |     |
|        |        |                                    |      |     |
|        |        | (b) Verify that requests that do   |      |     |
|        |        |     not have secure copy as their  |      |     |
|        |        |     media type are unaffected and  |      |     |
|        |        |     continue to be processed.      |      |     |
|        |        |                                    |      |     |
|        |        | (c) Verify that the operators can  |      |     |
|        |        |     resume secure copy requests    |      |     |
|        |        |     from the OMS GUI.              |      |     |
|        |        |                                    |      |     |
|        |        | ::: Definition-Term                |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
|        |        | :::                                |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 70     | ::: Definition-Term                | FC   | NEW |
|        |        | Repeat the set up in Criterion 60, |      |     |
|        |        | then cancel several subscriptions  |      |     |
|        |        | for secure copy and other media    |      |     |
|        |        | types. Handle the intervention at  |      |     |
|        |        | the OMS GUI as follows:            |      |     |
|        |        | :::                                |      |     |
|        |        |                                    |      |     |
|        |        | (a) Verify that the operator       |      |     |
|        |        |     cannot change a non-secure     |      |     |
|        |        |     copy media type to secure copy |      |     |
|        |        |     from the OMS GUI.              |      |     |
|        |        |                                    |      |     |
|        |        | (b) ::: Definition-Term            |      |     |
|        |        |     Verify that the operator can   |      |     |
|        |        |     change the media type from     |      |     |
|        |        |     secure copy to another media   |      |     |
|        |        |     type from the OMS GUI, and     |      |     |
|        |        |     that the request can be        |      |     |
|        |        |     resumed.                       |      |     |
|        |        |     :::                            |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 80     | ::: Definition-Term                | FC   | NEW |
|        |        | Perform a search and order from    |      |     |
|        |        | the EDG. Verify that the secure    |      |     |
|        |        | copy media type is not accessible  |      |     |
|        |        | from the EDG.                      |      |     |
|        |        | :::                                |      |     |
|        |        |                                    |      |     |
|        |        | \[Note: It is anticipated that     |      |     |
|        |        | this will be satisfied by          |      |     |
|        |        | configuration of the media types   |      |     |
|        |        | in the registry for V0 GWY, which  |      |     |
|        |        | will override the common system    |      |     |
|        |        | media types\]                      |      |     |
+--------+--------+------------------------------------+------+-----+
|        | 90     | ::: Definition-Term                | FC   | NEW |
|        |        | Repeat criterion 10 but specify a  |      |     |
|        |        | destination which is not enabled   |      |     |
|        |        | for ssh.                           |      |     |
|        |        | :::                                |      |     |
|        |        |                                    |      |     |
|        |        | (a) ::: Definition-Term            |      |     |
|        |        |     Verify that the request is     |      |     |
|        |        |     suspended in DDIST after the   |      |     |
|        |        |     total number of retries has    |      |     |
|        |        |     been exhausted.                |      |     |
|        |        |     :::                            |      |     |
|        |        |                                    |      |     |
|        |        | (b) ::: Definition-Term            |      |     |
|        |        |     Verify that the request can be |      |     |
|        |        |     cancelled in DDIST, and that a |      |     |
|        |        |     descriptive error message is   |      |     |
|        |        |     logged.                        |      |     |
|        |        |     :::                            |      |     |
|        |        |                                    |      |     |
|        |        | Verify that the passwords do not   |      |     |
|        |        | appear unencrypted in any of the   |      |     |
|        |        | logs.                              |      |     |
+--------+--------+------------------------------------+------+-----+