ENCLOSURE 1 - JH Variant Requirements.pdf

ENCLOSURE A: JHV Requirements

General Notes:

1. For MEO and GEO, the forward link (FL) direction is from the JHV to the satellite. Forward link L-band interfaces are output interfaces from the JHV perspective.

2. For MEO and GEO, the return link (RL) direction is from the satellite to the JHV. Return link L-band interfaces are input interfaces from the JHV perspective.

The following Joint Hub Variant for MEO and GEO requirements shall be applicable at the JHV segment level and below to include hardware, software, and firmware.

a. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver an upgrade to the GFX PTES JH that provides two commercial satellite configurations: GEO and MEO. The JHV can be in either GEO or MEO configuration at a time and is not required to support both configurations simultaneously.

Section A.1 JHV for GEO requirements

The following Joint Hub Variant for GEO requirements shall be applicable at the JHV segment level and below to include hardware, software, and firmware.

a. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver GEO configuration upgrades to the GFX PTES JH while retaining all pre-upgrade performance and functionality that is not superseded by upgrade-related requirements.

b. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver MEO configuration upgrades to the GFX PTES JH that meet all applicable certification requirements for the O3B mPOWER system and other Commercial SATCOM providers.

c. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver GEO configuration upgrades to the GFX PTES JH that provide two dedicated individually configurable class-of-service port to identified user connections.

d. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a GEO configuration upgrade to the GFX PTES JH that provides an internal M-code GPS receiver.

e. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a GEO configuration upgrade to the GFX PTES JH that supports the maximum aggregate FL bandwidth in any one of the L-band outputs. Only one L-band output is operational at a time.

f. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a GEO configuration upgrade to the GFX PTES JH that supports the maximum aggregate RL bandwidth in any one of the L-band inputs. Only one L-band input is operational at a time.

Section A.2 JHV for MEO requirements

The following Joint Hub Variant for MEO requirements shall be applicable at the JHV segment level and below to include hardware, software, and firmware.

a. General Notes for MEO:

1. MEO JHV-to-satellite slant range is not static but is a function of time.

2. MEO JHV-to-satellite Doppler is not static but is a function of time.

3. The MEO satellite mapped to each L-band input will change over time as the satellites in the

MEO constellation pass the JHV location.

4. Different MEO L-band inputs will be mapped to different satellites at the same time (e.g., L-band input 1 may be mapped to satellite 5 while L-band input 2 is mapped to satellite 6).

5. The MEO satellite mapped to each L-band output will change over time as the satellites in the MEO constellation pass the JHV location.

6. Different MEO L-band outputs will be mapped to different satellites at the same time (e.g., L-band output 1 may be mapped to satellite 5 while L-band output 2 is mapped to satellite 6).

7. A MEO satellite handover stagger occurs when the JHV transitions FL and RL communication resources from the falling satellite L-band input/output to the rising satellite L-band input/output. MMS maps each of the FL and RL communication resources to one of the multiple staggers that occur during a pass between falling satellite and rising satellite.

b. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver MEO configuration upgrades to the GFX PTES JH while retaining all pre-upgrade performance and functionality that is not superseded by upgrade-related requirements.

c. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver MEO configuration upgrades to the GFX PTES JH that meet all applicable certification requirements for the O3B mPOWER system and other Commercial SATCOM providers.

d. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver MEO configuration upgrades to the GFX PTES JH that provide two dedicated individually configurable class-of-service port to identified user connections.

e. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides an internal M-code GPS receiver.

f. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides two simultaneously operational L-band inputs. Note that the GFX PTES JH supports one L-band input at a time.

g. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides two simultaneously operational L-band outputs. Note that the GFX PTES JH supports one L-band output at a time.

h. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides simultaneous utilization of two GFX ECUs, one for the rising satellite PTW waveform times and one for the falling satellite PTW waveform times. Note that the GFX PTES JH supports one ECU.

i. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides bi-directional operation simultaneously on a rising satellite and a falling satellite. Bi-directional operation with each satellite is supported via one L-band input and one L-band output. f

j. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that post-compensates for L-band input timing variations due JHV-to-satellite slant range. L-band input timing is based on the satellite mapped to that L-band input.

k. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that post-compensates for L-band input JHV-to-Satellite Doppler frequency offset. L-band input Doppler is based on the satellite mapped to that L-band input.

l. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides L-band output timing that pre-compensates for JHV-to-satellite slant range. L-band output timing is based on the satellite mapped to that L-band output.

m. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides an L-band output frequency offset that pre-compensates for JHV-to-satellite Doppler. L-band output Doppler is based on the satellite mapped to that L-band output.

n. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that distributes the aggregate RL bandwidth across two L-band inputs. Each of the two simultaneously operational L-band inputs may be assigned from zero to the maximum aggregate RL communications bandwidth of the JHV, under the constraint that the sum of the bandwidths across both L-band inputs does not exceed the maximum aggregate RL communications bandwidth of the JHV.

o. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that distributes the aggregate FL bandwidth across two L-band outputs. Each of the two simultaneously operational L-band outputs may be assigned from zero to the maximum aggregate FL communications bandwidth of the JHV, under the constraint that the sum of the bandwidths across both L-band outputs does not exceed the maximum aggregate FL communications bandwidth of the JHV.

p. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that meets all performance requirements when operating with Doppler shift, rate of change and acceleration values resulting from operation with satellites in MEO orbit, including the O3B mPower system and other Commercial SATCOM providers.

q. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that transitions FL and RL communication resources from the falling satellite L-band input/output to the rising satellite L-band input/output at MMS-defined stagger times. Each FL and RL communication resource element can be mapped to any stagger by MMS.

r. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that has a defined maximum outage period duration when communication resources are transitioned from the falling satellite L-band input/output to the rising satellite L-band input/output. A seamless transition is not required. Only communication resources being transitioned experience an outage, while other communication resources are not impacted.

s. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that has four simultaneous and independently adjusted PTW waveform times:

1. Falling FL transmit time, based on slant range and slant range time derivatives to the falling satellite.

2. Falling RL receive time, based on slant range and slant range time derivatives to the falling satellite.

3. Rising FL transmit time, based on slant range and slant range time derivatives to the rising satellite.

4. Rising RL receive time, based on slant range and slant range time derivatives to the rising satellite.

t. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides simultaneous operation of four L-band interfaces (two L-band inputs and two L-band outputs), one for each of the four PTW waveform times defined in the prior requirement.

u. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that executes staggers according to a schedule provided by MMS configurations.

v. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that accepts and executes MMS configurations with at least 3 staggers during each pass between falling satellite and rising satellite. This requirement does not prohibit configurations with 1 or 2 staggers.

w. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that provides logical beams with FL communication resources simultaneously spanning two L-band outputs and RL communication resources simultaneously spanning two L-band inputs. This requirement does not prohibit all FL communication resources on one L-band output and does not prohibit all RL communication resources on one L-band input.

x. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that distributes the maximum number of beams supported by the JHV across the rising satellite and falling satellite L-band input/outputs. Each satellite may be assigned from zero to the JHV maximum number of logical beams, under the constraint that the sum of logical beams across the rising and falling satellites does not exceed the JHV maximum number of logical beams.

y. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that, after all logical beams have transitioned from the falling satellite to the rising satellite during a pass, is capable of communicating via the next rising satellite in less than a defined maximum time. This time period is not an outage because it occurs during a window when all logical beams in the JHV are handled by a single satellite. This activity is in preparation for the pending arrival of the next rising satellite. Preparation includes, but is not limited to, transitioning the following items from falling satellite to the next rising satellite: satellite ephemeris, FL and RL waveform timing, and GFX ECU timing.

z. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a MEO configuration upgrade to the GFX PTES JH that supports MEO constellations with at least 13 satellites. This includes, but is not limited to, receiving, storing and processing of satellite-specific ephemeris data. The JHV supports one MEO constellation at a time.

Section A.3 PTWoC Mission Management System (MMS) Upgrade for MEO and GEO

The following MMS Upgrade requirements shall be applicable at the MMS segment level and below.

a. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS with adherence to the CJCSI 6250.01x DEPARTMENT OF DEFENSE SATELLITE COMMUNICATIONS and SPI 3250.01x SATELLITE COMMUNICATIONS (SATCOM).

Section A.3.1 PTWoC Mission Management System (MMS) Upgrade for GEO

a. The PTWoC JHV and MMS Upgrade Contractor shall evaluate the baseline PTES MMS implementation to determine any upgrades needed to manage missions over Commercial SATCOM GEO satellites.

b. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to determine if missions can be satisfied over Commercial SATCOM GEO satellites, to include modeling of the GEO payloads and conducting supportability analysis.

Section A.3.2 PTWoC Mission Management System (MMS) Upgrade for MEO

a. The PTWoC JHV and MMS Upgrade Contractor shall evaluate the baseline PTES MMS implementation to determine any upgrades needed to manage missions over Commercial SATCOM MEO satellites.

b. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to determine if missions can be satisfied over Commercial SATCOM MEO satellites, to include modeling of the MEO payloads and conducting supportability analysis.

c. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to manage and track all stagger times available for handovers for all descending to ascending satellites, at every MEO Joint Hub variant location.

d. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to manage and track MEO JHV interfaces with the gateway equipment.

e. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to determine the MEO JHV to support all terminals within a mission.

f. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to determine if missions can be supported over Commercial SATCOM MEO O3B mPower constellation.

g. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to interface, machine to machine, with the O3B mPower system and other Commercial SATCOM providers.

h. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to manage and process the Link Configuration Plan, which contains the approved resources, stagger times, received from the O3B mPower system.

i. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to manage and process the gateway tracking plan, which contains the times and MEO satellites tracked by the antennas interfaced to the JHVs.

j. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to determine the stagger times, from mission start to mission end, for all locations, each terminal in a mission will need to perform handover from a falling MEO satellite to a rising MEO satellite within the same MEO constellation.

k. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to produce the details of service orders to be submitted to O3B mPower system to request services for missions.

l. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to determine the parameters in the handover configuration files and sets of configuration files for the MEO JHVs and user Terminals (TM LRUs), for stationary and mobile terminals.

m. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to generate and disseminate handover configuration files for the MEO JHVs and TM LRUs, together with the PTES baseline configuration files and key packages.

n. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to display MEO constellation coverages, JHV locations, and terminals’ locations.

o. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to store and display performance metrics received from Commercial SATCOM providers.

p. The PTWoC JHV and MMS Upgrade Contractor shall upgrade the baseline PTES MMS to replan mobile terminals with new stagger time(s), new Return Link Channel Groups (RLCG) and Forward Link Channel (FLC) assignments, create new service order(s), and generate and disseminate configuration files, as mobile terminals report terminal locations periodically.

Section A.4 Cybersecurity/IA requirements

a. PTWoC Joint Hub Variant and MMS Upgrade contractors will be required to meet Risk Management Framework (RMF) requirements for PTWoC Joint Hub Variant and MMS Upgrade.

b. Please comment on and provide potential impacts for the following Cybersecurity Requirements (see Development).

Please note that these tasks are currently in work and subject to change.

c. Documents included in this RFI that are applicable:

i. DODI 8510.01 (Enclosure 4.c.i)

ii. NIST SP 800-53 rev 5 (Enclosure 4.c.ii)

iii. CNSSI No 1253 (Enclosure 4.c.iii)

iv. Space_AO_IATT_Process_Memo 24 Jan 2023 (Enclosure 4.c.iv)

v. Space_AO_Required_Artifacts_Memo_06 Feb 2023 (Enclosure 4.c.v)

vi. NIST 800-171 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations

vii. Space AO ATO required artifacts.

d. Defense Federal Acquisition Regulation Supplement (DFARS), DFARS252.204-7012

Safeguarding Covered Defense Information and Cyber Incident Reporting. Please explain how your company intends to comply with DFARS252.204-7012.

Section A.4.1 Development

The following cybersecurity requirements shall be applicable at the JHV and MMS, segment levels and below to include hardware, software, and firmware.

a. The PTWoC JHV and MMS Upgrade Contractor shall implement security as directed by the Government. The PTWoC Contractor shall demonstrate how the PTWoC JHV and MMS will implement security controls at the Government’s direction and deliver a system capable of obtaining the RMF authorization approval from the SpOC S3/6 office.

b. The Contractor shall implement and update identified technical Cybersecurity controls into the component and system engineering processes and deliver a Cybersecurity Implementation Plan (CSIP) that indicates integration of Government PTES Program Office identified Cybersecurity controls from Master Control List (MCL) into the engineering processes, products, system, and segments. The CSIP shall incrementally demonstrate how the contractor will deliver a system that is Cybersecurity control compliant.

c. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver the Cybersecurity Test & Verification Plan (CTVP) that details how the cybersecurity requirements identified from the PTWoC JHV TRD and the tailored security controls will be tested and validated throughout the system lifecycle. The CTVP shall be developed covering all cybersecurity-enabled devices (e.g., router, switch, desktop, server) up through the system level.

d. The PTWoC JHV and MMS Upgrade Contractor shall ensure their overall system cybersecurity test and evaluation process is fully integrated into the overall system test and evaluation processes and plans. The PTWoC JHV and MMS Upgrade Contractor shall demonstrate and maintain traceability between the CSIP, CTVP, allocated and Government approved tailored security controls, and PTWOC JHV TRD. The PTWOC JHV and MMS Upgrade Contractor shall support updates to the Information Technology Categorization and Selection Checklist (ITCSC), CSIP, and Policies.

e. The PTWoC JHV and MMS Upgrade Contractor shall design, develop, and implement an Operating System and Software Patching Plan (OSSPP) that captures and demonstrates how the PTWoC JHV and MMS Upgrade Contractor will maintain the operating system and software patching compliance with published STIGs and vendor OEM standards. The PTWoC JHV and MMS Upgrade Contractor shall collaborate with DISA and integrate the OSSPP into the systems engineering policies, plans and procedures.

f. The PTWoC JHV and MMS Upgrade Contractor shall develop and deliver a Cybersecurity Architecture.

g. The PTWoC JHV and MMS Upgrade Contractor shall develop a Hardware/Software (HW/SW) List and deliver using to the Government provided template.

h. The PTWoC JHV and MMS Upgrade Contractor shall develop the Ports, Protocols and Services (PPS), and deliver according to the Government provided template.

i. The PTWoC JHV and MMS Upgrade Contractor shall deliver products that support RMF authorization approval from SpOC S3/6 for the system with an RMF system categorization impact assessment and all applicable overlays IAW CNSSI 1253, and NIST SP800-53.

(accessible on IDE)

j. The artifacts required for the Interim Authority to Test (IATT) approval are captured in Space_AO_IATT_Process_Memo 24 Jan 2023.

k. The artifacts required for Authorization to Operate (ATO) are captured in Space_AO_Required_Artifacts_Memo_06 Feb 2023.

l. The PTWoC JHV and MMS Upgrade Contractor shall implement DISA Security Technical Implementation Guides (STIG)s, vendor (Original Equipment Manufacturer (OEM)) security guidance, best practices, and applicable vendor product patches at least quarterly to the system under test and operation.

m. The PTWoC JHV and MMS Upgrade Contractor shall demonstrate how the system Solution Architecture is Global (e.g., fail-safe; redundant; able to operate through compromise, degraded operation, or degraded communications).

n. The PTWoC JHV and MMS Upgrade Contractor shall demonstrate how the system will support the continuous monitoring of cybersecurity status with the ability to identify, isolate, eradicate, and recover from an internal and external threat.

o. The PTWoC JHV and MMS Upgrade Contractor shall assess the impact of vulnerabilities and develop and implement custom countermeasures.

p. The PTWoC JHV and MMS Upgrade Contractor shall ensure the PTWoC JHV cybersecurity workforce is certified consistent with DoDD 8140.01 (Cyberspace Workforce Management), IA Training, Certification and Workforce Management within six (6) months of ECD.

q. The PTWoC JHV and MMS Upgrade Contractor shall comply with Committee on National Security Systems Policy (CNSSP) No. 11 (National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology (IT) Products) and CNSSP No. 12 (Cybersecurity Policy for Space Systems Used to Support National Security Missions), and consistent with DoDI 8500.01 (Cybersecurity) for all cybersecurity related to PTWOC JHV, including subsystems, hardware, and software.

r. The PTWoC JHV and MMS Upgrade Contractor shall support the Government PTWoC JHV Program Office led Cybersecurity Review Board (CRB) for the development, refinement, and implementation of a cybersecurity strategy. Projected meetings are quarterly.

s. The PTWoC JHV and MMS Upgrade Contractor shall maintain the Cybersecurity Test & Verification Plan (CTVP) that details how the cybersecurity requirements identified from the PTWoC JHV TRD and the tailored security controls. The controls will be tested throughout the system lifecycle. The CTVP shall be developed covering all cybersecurity-enabled device (e.g., Router, switch, desktop, server) up through the system level.

t. PTWoC JHV system component with a direct network interface to the DISN shall comply with the DISA Approved Product List (APL) (https://aplits.disa.mil/).

Section A.4.2 Sustainment

a. The PTWoC JHV and MMS Upgrade Contractor shall ensure compliance with Information Assurance, Cybersecurity, and Program Protection requirements.

1. The PTWOC JHV and MMS Upgrade Contractor shall conduct STIG compliance scans and deliver a quarterly status of STIG and OEM test status along with system and segment patch status.

i. The PTWoC JHV and MMS Upgrade Contractor shall deliver both raw and summary STIG results, as well as the version and date of the STIGs used, along with the monthly status updates into the IDE.

https://aplits.disa.mil/

ii. The summary STIG results shall include validation statements proving that the vendor has reviewed and addressed each finding within the STIG compliance scans.

iii. The PTWOC JHV and MMS Upgrade Contractor shall review their POAM monthly and provide comments and milestones to the Government Program Office. (accessible on the IDE)

b. The PTWoC JHV and MMS Upgrade Contractor shall identify and implement efficiencies and process improvements over the lifecycle, that will reduce the cost to operate and sustain the system.

c. The PTWoC JHV and MMS Upgrade Contractor shall maintain the security controls implemented for the operational life of the PTWOC JHV system.

d. The PTWoC JHV and MMS Upgrade Contractor shall maintain the Operating System and Software Patching Plan (OSSPP) for the operational life of the PTWoC JHV System.

e. PTWoC JHV and MMS Upgrade Contractor shall maintain the PTWoC JHV Cybersecurity Architecture for the operational life of the PTWoC JHV System.

f. The PTWoC JHV and MMS Upgrade Contractor shall perform cybersecurity maintenance activities needed to maintain the RMF authorization for the operational life of the PTWOC JHV system and annual review of the system security policies or the RMF authorization extension. The review will be held in conjunction with the Cybersecurity Review Board.

The below table is for assessment with government known documents. Can you please inform the Government what your company calls the above documents? Additionally, if there are documents listed on this table that are not applicable to your company, can you please identify that document for the government?

Section Document Name Corresponding Requirements 2a Information Technology Categorization and

Selection Checklist (ITCSC) Same

2b AO Designated Representative (AODR) Signed eMASS Registration and Security Plan

Same

2c Topology/Authorization Boundary Same 2d Hardware List Hardware List, Parts, Materials, and Processes Selection List (Approved suppliers), As-Built Configuration

2d Software List Software List, Software Version Description (SVD)

2e Boundary Network Device Configuration Files (as requested)

N/A

2f Cybersecurity Strategy Same 2g Signed and dated Access Control, Audit and

Accountability, Configuration Management and Incident Response plans and policies

Same, also include the Orbital Operator Handbook

2h Security Technical Implementation Guide (STIG) applicability list (i.e., a listing of all STIGs applicable to the information system

Interface Control Document (ICDs) / Test Cases. Software Test Description based on technologies and architecture) 2i STIG compliance and vulnerability scans for all assets (analyzed and dated within 60 days of submission)

ASD STIG, Functional Test Results/Documents, (i.e., Software Test Report (STR), Software Integration Test (SWIT), Software Item Qualification Test (SIQT), Static Code Analysis, System Performance Test (SPT)) Flight Software (FSW) scans

2j Ports, Protocols, and Services (PPS) Matrix and PPS registration / tracking number

Interface Control Document (ICDs) / Test Cases. Software Test Description

2k Information System Continuous Monitoring Strategy

Same