About this file

This document is Enclosure A to a Request for Information (RFI) detailing Joint Hub Variant (JHV) Requirements for the Protected Tactical SATCOM-Global (PTS-G) program. The requirements specify technical upgrades for a Government Furnished X (GFX) Protected Tactical Enterprise Service (PTES) Joint Hub at commercial Geosynchronous Earth Orbit (GEO) gateways, focusing on developing and delivering configuration upgrades that include: two dedicated individually configurable class-of-service ports, an internal M-code GPS receiver, support for maximum Forward Link and Return Link bandwidth in L-band interfaces, and Mission Management System (MMS) upgrades adhering to specific Department of Defense satellite communications standards.

The document extensively details cybersecurity and information assurance requirements, mandating that the contractor implement security controls, develop a Cybersecurity Implementation Plan, create a Cybersecurity Test & Verification Plan, maintain security controls throughout the system's operational life, perform quarterly security patches, ensure workforce certification, comply with multiple national security and cybersecurity policies, and support a Cybersecurity Review Board. Key compliance documents include DODI 8510.01, NIST SP 800-53, CNSSI No. 1253, and DFARS 252.204-7012, with the ultimate goal of obtaining Risk Management Framework (RMF) authorization approval from the Space Operations Command.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ENCLOSURE A: Joint Hub Variant (JHV) Requirements

General Notes:

1. For Protected Tactical SATCOM- Global (PTS-G), 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 PTS-G, 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 JHV for PTS-G requirements shall be applicable at the JHV segment level and below to include hardware, software, and firmware.

a. The Protected Tactical Waveform (PTW) over PTS-G JHV and Mission Management System (MMS) Upgrade Contractor shall develop and deliver an upgrade to the Government Furnished X (GFX) Protected Tactical Enterprise Service (PTES) Joint Hub that is hardened to be able to operate with Keying Material (KEYMAT) at commercial Geosynchronous Earth Orbit (GEO) gateways.

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 PTW over PTS-G JHV and Mission Management System (MMS) Upgrade Contractor shall develop and deliver PTS-G configuration upgrades to the GFX PTES Joint Hub while retaining all pre-upgrade performance and functionality that is not superseded by upgrade-related requirements.

b. The PTW over PTS-G 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.

c. The PTW over PTS-G JHV and MMS Upgrade Contractor shall develop and deliver a GEO configuration upgrade to the GFX PTES JH that provides an internal M-code Global Positioning System (GPS) receiver.

d. The PTW over PTS-G 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.

e. The PTW over PTS-G 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.3 PTW over PTS-G Mission Management System (MMS) Upgrade for GEO

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

a. The PTW over PTS-G 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 PTW over PTS-G MMS Upgrade for GEO

a. The PTW over PTS-G JHV and MMS Upgrade Contractor shall evaluate the baseline PTES MMS implementation to determine any upgrades needed to manage missions over PTS-G satellites.

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

Section A.4 Cybersecurity/Information Assurance (IA) requirements

a. PTW over PTS-G Joint Hub Variant (JHV) and MMS Upgrade contractors will be required to meet Risk Management Framework (RMF) requirements for PTW over PTS-G JHV 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 PTW over PTS-G JHV and MMS Upgrade Contractor shall implement security as directed by the Government. The PTW over PTS-G Contractor shall demonstrate how the PTW over PTS-G 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 Space Operations Command (SpOC) S3/6 o ice.

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 O ice 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 PTW over PTS-G JHV and MMS Upgrade Contractor shall develop and deliver the Cybersecurity Test & Verification Plan (CTVP) that details how the cybersecurity requirements identified from the PTW over PTS-G JHV Technical Requirements Document (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 PTW over PTS-G 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 PTW over PTS-G JHV and MMS Upgrade Contractor shall demonstrate and maintain traceability between the CSIP, CTVP, allocated and Government approved tailored security controls, and PTW over PTS-G JHV TRD. The PTW over PTS-G JHV and MMS Upgrade Contractor shall support updates to the Information Technology Categorization and Selection Checklist (ITCSC), CSIP, and Policies.

e. The PTW over PTS-G JHV and MMS Upgrade Contractor shall design, develop, and implement an Operating System and Software Patching Plan (OSSPP) that captures and demonstrates how the PTW over PTS-G JHV and MMS Upgrade Contractor will maintain the operating system and software patching compliance with published Security Technical Implementation Guides (STIGs) and vendor Original Equipment Manufacturer (OEM) standards. The PTW over PTS-G JHV and MMS Upgrade Contractor shall collaborate with the Defense Information Systems Agency (DISA) and integrate the OSSPP into the systems engineering policies, plans and procedures.

f. The PTW over PTS-G JHV and MMS Upgrade Contractor shall develop and deliver a Cybersecurity Architecture.

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

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

i. The PTW over PTS-G 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 PTW over PTS-G JHV and MMS Upgrade Contractor shall implement DISA STIGs, vendor OEM security guidance, best practices, and applicable vendor product patches at least quarterly to the system under test and operation.

m. The PTW over PTS-G 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 PTW over PTS-G 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 PTW over PTS-G JHV and MMS Upgrade Contractor shall assess the impact of vulnerabilities and develop and implement custom countermeasures.

p. The PTW over PTS-G JHV and MMS Upgrade Contractor shall ensure the PTW over PTS-G JHV cybersecurity workforce is certified consistent with DoDD 8140.01 (Cyberspace Workforce Management), IA Training, Certification and Workforce Management within six (6) months of the Estimated Completion Date (ECD).

q. The PTW over PTS-G 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 PTW over PTS-G JHV, including subsystems, hardware, and software.

r. The PTW over PTS-G JHV and MMS Upgrade Contractor shall support the Government PTW over PTS-G JHV Program O ice led Cybersecurity Review Board (CRB) for the development, refinement, and implementation of a cybersecurity strategy. Projected meetings are quarterly.

s. The PTW over PTS-G JHV and MMS Upgrade Contractor shall maintain the Cybersecurity Test & Verification Plan (CTVP) that details how the cybersecurity requirements identified from the PTW over PTS-G 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. PTW over PTS-G JHV system component with a direct network interface to the Defense Information Systems Network (DISN) shall comply with the DISA Approved Product List (APL) (https://aplits.disa.mil/).

Section A.4.2 Sustainment

a. The PTW over PTS-G JHV and MMS Upgrade Contractor shall ensure compliance with Information Assurance, Cybersecurity, and Program Protection requirements.

1. The PTW over PTS-G 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 PTW over PTS-G 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 Integrated Digital Environment (IDE).

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 PTW over PTS-G JHV and MMS Upgrade Contractor shall review their Plan of Action and Milestones (POAM) monthly and provide comments and milestones to the Government Program O ice. (accessible on the IDE)

b. The PTW over PTS-G JHV and MMS Upgrade Contractor shall identify and implement e iciencies and process improvements over the lifecycle, that will reduce the cost to operate and sustain the system.

c. The PTW over PTS-G JHV and MMS Upgrade Contractor shall maintain the security controls implemented for the operational life of the PTW over PTS-G JHV system.

d. The PTW over PTS-G JHV and MMS Upgrade Contractor shall maintain the OSSPP for the operational life of the PTW over PTS-G JHV System.

e. PTW over PTS-G JHV and MMS Upgrade Contractor shall maintain the PTW over PTS-G JHV Cybersecurity Architecture for the operational life of the PTW over PTS-G JHV System.

f. The PTW over PTS-G JHV and MMS Upgrade Contractor shall perform cybersecurity maintenance activities needed to maintain the RMF authorization for the operational life of the PTW OVER PTS-G 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 Authorizing O icial 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 based on technologies and architecture)

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

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

File details come from the government source that posted it. Updated .