Attachment 4- ITAR_Terms-Conditions_FC Life Cylce_2.pdf

As of 7/30/2025

FREEDOM CENTER LIFE CYCLE

PR257668E18 / PR257668E189 / PR257668E18 / PR257668E190

Terms & Conditions

08/14/2025

1.0 Terms and Conditions

1.1 Cybersecurity Policy for TSA Government Acquisitions (June 2025)

A. General Security Requirements:

A.1. Special notice for program sponsors:

The following Cybersecurity policy requirements supersedes any inadvertent or deliberate contradiction in previous sections of this document. Program sponsors must ensure this section is thoroughly reviewed prior to initiating the Appendix G approval process.

A.2. All authorized, cleared and vetted personnel (i.e., federal employees; and primary, subcontractor, and/or 3rd party vendors or contractors) supporting or doing business per agreement with TSA (either directly or indirectly) shall comply with applicable cybersecurity or information assurance (IA) policies as stated in the DHS Policy Directive 4300A, Information Technology System Security Program, Sensitive Systems, version 13.3, Feb 23, 2023 (hereinafter known as DHS 4300A) and Attachments; DHS National Security Systems Policy Directive 4300B Version 10.1, November 21, 2018 for classified systems (hereinafter known as DHS 4300B); TSA MD 1400.28 Information System Security Program (ISSP); TSA Information System Security Program (ISSP) Policy Directive (PD) and TSA Organizational Defined Parameter (ODP) spreadsheet; supplemental Technical Standards (TSs) and Standard Operating Procedures (SOPs); TSA Cloud Computing Security Handbook (CCSH); the DOD Cloud Computing Security Requirements Guide (CC SRG); and the NIST SP 800-53, “Security and Privacy Controls for Information Systems and Organizations”, Rev 5 standards. This Cybersecurity Policy document serves as a subset to the TSA PD. Additional DHS directives and security related guides for contractors can be found on DHS’ security policy site:

www.dhs.gov/publication/security-training-contract-policy.

A.3. The Contractor shall comply with Federal, Department of Homeland Security (DHS) and Transportation Security Administration (TSA) security, sensitive information handling, and privacy guidelines in effect at the time of the award of the contract, as well as those requirements that may be added during the contract.

A.4. The Contractor shall perform periodic reviews to ensure compliance with cybersecurity, information security and privacy requirements.

A.5. The Contractor shall comply with proper DHS and TSA security controls to ensure that the Government's security requirements are met. These controls are described in DHS 4300A, TSA MD 1400.28 ISSP, the TSA ISSP PD and TSA ODP security policy documents and is mainly based on the current National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 Rev 5 standards.

A.6. The Contractor shall include this guidance in all subcontracts at any tier where the subcontractor is performing the work defined in the Statement of Work (SOW), Performance Work Statement (PWS), Statement of Objective (SOO).

http://www.dhs.gov/publication/security-training-contract-policy

A.7. The Contractor shall ensure all its staff members have the required level of approved security clearance commensurate with the sensitivity of the information being accessed, stored, processed, transmitted, or otherwise handled by the system or required to perform the work stipulated by the contract. At a minimum, all Contractor staff shall be subjected to a Public Trust background check and be granted a Public Trust clearance before access to any system or other TSA resources as granted.

A.8. The Contractor shall sign a DHS Form 11000-6 Non-Disclosure Agreement (NDA) within thirty (30) calendar days of the contract start date.

A.9. The Contractor shall not release, publish, or disclose agency information to unauthorized personnel, and shall protect such information in accordance with the provisions of pertinent laws, regulations, and policies governing the confidentiality of sensitive information.

A.10. The Contractor shall ensure its staff follow all policies and procedures governing cybersecurity, physical, environmental, and information security described in the various TSA regulations pertaining thereto, and the specifications, directives, and manuals for conducting work to generate the products as required by the contract. Personnel shall be responsible for the physical security of their work area and government furnished equipment (GFE) issued to the contractor under the terms of the contract.

A.11. The Contractor shall make all system information and documentation produced (in support of the contract) available to TSA upon request.

B. Risk Management Framework (RMF):

B.1. The Security Authorization (SA) and Ongoing Authorization (OA) processes, in accordance with recent NIST SP 800-37 Rev 2 (Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy) and SP 800-137 (Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations) are required for all TSA IT systems, including General Support Systems (e.g., standard TSA desktop, general network infrastructure, electronic mail), Major Applications and development systems (if connected to the operational network or processing, storing, or transmitting government data). These processes are documented in the NIST Risk Management Framework (RMF), and the Ongoing Authorization is part of Step 6 “Monitoring” of the RMF.

All NIST guidance is publicly available; TSA and DHS security policy is disclosed upon contract award with some exceptions, which are public facing (i.e., DHS Security and Training Requirements for Contractors).

B.2. Data Privacy and Protection: See SAFEGUARDING OF CONTROLLED UNCLASSIFIED INFORMATION (JULY 2023) and INFORMATION TECHNOLOGY SECURITY AWARENESS TRAINING (JULY 2023) for additional clauses.

a) The contractor shall satisfy requirements to work with and safeguard Controlled Unclassified Information (CUI), which includes Sensitive Security Information (SSI), Personally Identifiable Information (PII), Sensitive Personally Identifiable Information (SPII), and others (See Appendix G for other examples). All support personnel shall https://www.dhs.gov/dhs-security-and-training-requirements-contractors https://www.dhs.gov/dhs-security-and-training-requirements-contractors https://ustsa.sharepoint.com/:w:/r/sites/IntranetTS/Offices/OIT/ITAR2/3052.204-72SafeguardingControlledUnclassifiedInformation.docx?d=w0b68ceaa9c6442d49621ed086203c4ba&csf=1&web=1&e=eJfmU0 https://ustsa.sharepoint.com/:w:/r/sites/IntranetTS/Offices/OIT/ITAR2/3052.204-72SafeguardingControlledUnclassifiedInformation.docx?d=w0b68ceaa9c6442d49621ed086203c4ba&csf=1&web=1&e=eJfmU0 https://ustsa.sharepoint.com/:w:/r/sites/IntranetTS/Offices/OIT/ITAR2/IT_SecurityAwarenessTraining.docx?d=wf8f62664aeb1423f98309cb044d43e44&csf=1&web=1&e=KCUbwF https://ustsa.sharepoint.com/:w:/r/sites/IntranetTS/Offices/OIT/ITAR2/IT_SecurityAwarenessTraining.docx?d=wf8f62664aeb1423f98309cb044d43e44&csf=1&web=1&e=KCUbwF understand and rigorously follow DHS and TSA requirements, SSI Policies and Procedures Handbook, and Privacy policies, and procedures for safeguarding SSI, PII and

SPII.

b) The Contractor shall be responsible for the security of i) all data that is generated by the contractor on behalf of the TSA, ii) TSA data transmitted by the contractor, and iii) TSA data otherwise stored or processed by the contractor regardless of who owns or controls the underlying systems while that data is under the contractor’s control. All TSA data, including but not limited to: CUI, PII, SPII, SSI, NSS, and Critical Infrastructure Information (CII) shall be protected according to DHS and TSA security policies and mandates.

c) TSA shall identify IT systems transmitting any classified/unclassified/SSI information and requiring protection based on a risk assessment. If encryption is required, the following methods are acceptable for encrypting sensitive information:

a. FIPS 197 (Advanced Encryption Standard (AES)) 256 algorithm (or higher) and cryptographic modules that have been validated under FIPS 140-3.

b. National Security Agency (NSA) Type 2 or Type 1 encryption (current version)

c. Public Key Infrastructure (PKI) (see current DHS 4300A), key cards, biometrics, or in the case of multi-factor authentication MFA), some combination therein (See Attachment U) Information Security Sensitive Systems Program Directive 4300A v 13.3, Feb 2023.

d) The contractor shall maintain data control according to the TSA security level of the data.

Data separation shall include the use of discretionary access control methods, VPN encryption methods, data aggregation controls, data tagging, media marking, backup actions, and data disaster planning and recovery. Contractors handling SPII shall comply with TSA MD 3700.4, Handling Sensitive Personally Identifiable Information (current version).

e) Users of TSA IT assets shall adhere to all system security requirements to ensure the confidentiality, integrity, availability, and non-repudiation of information under their control. All users accessing TSA IT assets are expected to actively apply the practices specified in the TSA ISSP PD, TSA ODP, and applicable Technical Standards and SOPs.

f) The contractor shall comply with SPII disposition requirements stated in the TSA ISSP

PD, applicable Technical Standards, SOPs and TSA MD 3700.4, Handling Sensitive Personally Identifiable Information.

g) The Contractor shall ensure all source code is protected from unauthorized access, alterations, or dissemination (see TSA ISSP PD, Technical Standard).

B.3. A written Authorization to Operate (ATO) granted by the TSA Authorizing Official (AO) is required prior to processing operational data or connecting to any TSA network. Contractor shall provide all necessary system information in support of the Security Authorization (SA) process. The AO shall ensure all TSA information systems undergo security assessment and authorization and obtain an ATO prior to operation and deployment. This includes all systems

(including pilots) that connect to the TSA network or process TSA sensitive data. The AO shall grant a maximum of two Interim Authorizations to Operate (IATOs) for pilot systems and pilot systems shall not be connected to, or deployed as, an operational system until an ATO is issued.

ATOs for Pilot systems shall not exceed ninety (90) days and these systems shall be removed from the operational network unless an extension is approved by the AO.

B.4. TSA shall assign a security category to each IT system compliant with the requirements of Federal Information Processing Standards (FIPS) Pub 199 Standards for Security Categorization of Federal Information and Information Systems impact levels and assign security controls to those systems consistent with FIPS Pub 200 Minimum Security Requirements for Federal Information and Information Systems methodology. Additionally, compliance shall be in accordance with (IAW) NIST 800-60 Volume 2 and Volume 1: Appendices to Guide for Mapping Types of Information and Information Systems to Security Categories.

B.5. Unless the AO specifically states otherwise for an individual system, the duration of any accreditation shall be dependent on the FIPS 199 rating and overall residual risk of the system;

the length can span up to 36 months.

B.6. The Security Authorization (SA) Package contains documentation required for SA and Ongoing Authorization (OA). The package shall contain the following security documentation as required by the DHS OA Methodology:

a) Security Assessment Report (SAR)

b) Security Plan (SP)

c) Contingency Plan

d) Contingency Plan Test Results

e) Federal Information Processing Standards (FIPS) 199 Security Categorization

f) Privacy Threshold Analysis (PTA)

g) E-Authentication

h) Security Assessment Plan (SAP)

i) Authorization to Operate (ATO) Letter

j) Plan of Action and Milestone (POA&M)

k) DHS Ongoing Authorization Artifacts

The SA package shall document the specific procedures, training, and accountability measures in place for systems that process Personally Identifiable Information (PII). All security compliance documents shall be reviewed and approved by the CISO and the IAD and accepted by the Contracting Officer (CO) upon creation and after any subsequent changes, before they go into effect. Note: The CO shall not alter or remove any documentation or language once approved by IAD or authorized members of its staff.

Ongoing Authorization artifacts include monthly TRigger Accountability Log (TRAL), monthly operating system scan results, application scans as directed, updated control allocation table (CAT), and associated memos as directed. All steps in the DHS Mandated tool or System of Record shall be completed correctly, thoroughly and in a timely manner for all steps of the RMF.

B.7. The Contractor shall support the successful remediation of all identified system weaknesses and vulnerabilities that are identified as a result of the aforementioned security review process.

B.8. The Contractor shall submit and analyze monthly operating system vulnerability scans for the DHS Information Security Performance Plan FISMA Scorecard. Vulnerabilities not remediated are generated into Plan of Action and Milestone (POA&Ms) after 30 days.

B.9. Training Requirements:

a) All newly-arrived Contractor employees requiring system access shall receive initial “Organizational Security Fundamentals (OSF)” training within 60 days of assignment to the contract via the Online Learning Center (OLC). The COR shall initiate and facilitate this access. Refresher training shall be completed annually thereafter. Another required OLC cybersecurity training course is the “Cybersecurity for TSA System Users (TSA- CYBRSCRTY-SYSTM-USRS)” training and would be the official TSA-wide course developed in accordance with mandated policy to safeguard TSA’s mission and assets. It is the annual course that all users shall take and the one leveraged against FISMA requirements.

b) The Contractor shall complete any TSA-related Privacy training on an annual basis.

c) Role-Based training is required for contract employees with Significant Security Responsibility (SSR), whose job proficiency is required for overall network security within TSA and shall be in accordance with DHS and TSA policy. The contractor shall be notified if they have a position with Significant Security Responsibilities.

d) Individuals with SSR shall have a documented individual training and education plan, which shall ensure currency with position skill requirements, with the first course to be accomplished within 90 days of employment or change of position. The individual training plan shall be refreshed annually or immediately after a change in the individual’s position description requirements.

e) Cybersecurity and privacy training supplied by the Contractor shall meet standards established by NIST and set forth in DHS and TSA security policy.

f) The Contractor shall maintain an accurate and up-to-date list of all vetted contractor employees who have completed training and shall submit this list to the Contracting Officer Representative (COR) upon request, or during DHS/TSA onsite validation visits performed on a periodic basis.

g) The contractor shall ensure its employees review, understand, and sign the TSA Form 1403 Computer and Wireless Mobile Device Access Agreement (CAA) prior to accessing any IT systems.

B.10. Configuration Management (hardware/software/applications):

https://ustsa.sharepoint.com/sites/Office-OTWE3/myOLC/SitePages/Home.aspx

a) Hardware or software configuration changes shall be in accordance with the current DHS

Information Security Performance Plan, the DHS Continuous Diagnostics and Mitigation (CDM) Program to include dashboard reporting requirements and TSA’s Configuration Management policy. The TSA Chief Information Security Officer (CISO)/Executive Director for Information Assurance and Cybersecurity Division (IAD) shall be informed of and aware of all configuration changes to the TSA IT environment including, but not limited to systems, hardware, software, applications, infrastructure architecture, infrastructure assets, and end user assets. The TSA IAD POC shall approve any Request for Change (RFC) prior to any development activity occurring for that change and shall define the security requirements for the requested change. The COR shall provide access to the DHS Information Security Performance Plan.

b) The Contractor shall ensure all application, software and/or configuration patches and/or

Requests for Change (RFC) have approval by the Technical Discussion Forum (TDF), Change Control Board (CCB) and lab regression testing prior to controlled change release under the security policy document, TSA MD 1400.28 ISSP, TSA PD and TSA ODP, unless immediate risk requires immediate intervention.

c) Approval for immediate intervention (i.e., emergency change) requires approval of the TSA CISO, CCB co-chairs, and the appropriate Operations Manager, at a minimum.

d) The Contractor shall ensure all sites, facilities or operational functions impacted by patching are compliant within 14 days of change approval and release.

e) The acquisition of commercial-off-the-shelf (COTS) Information Assurance (IA) and IA-enabled IT products (to be used on systems entering, processing, storing, displaying, or transmitting “sensitive information”) shall be limited to those authorized products that have been carefully analyzed, reviewed, evaluated, and validated, as appropriate, in accordance with the following:

• The NIST FIPS validation program.

• The National Security Agency (NSA)/NIST, National Information Assurance

Partnership (NIAP) Evaluation and Validation Program.

• The International Common Criteria for Information Security Technology

Evaluation Mutual Recognition Agreement.

f) US Government Department of Defense/Department of Homeland Security, Security Technical Implementation Guides (STIGs):

1. The provider of information technology shall certify all applications are fully functional, safe, secure and operate correctly as intended on systems using the US DoD Security Technical Implementation Guides (STIGs) and in accordance with DHS and TSA guidance.

a. DoD STIGs/SRG: https://public.cyber.mil/stigs/ https://public.cyber.mil/stigs/

b. DHS Sensitive Systems Configuration Guidance:

The standard installation, operation, maintenance, management, updates and/or patching of software shall not alter the configuration settings from the approved United States Government Configuration Baseline | CSRC (nist.gov) (USGCB) configuration. The information technology shall also use the Windows Installer Service for installation to the default “program files” directory and shall be able to discretely install and uninstall.

2. Applications designed for general end users shall run in the general user context without elevated system administration privileges.

g) The Contractor shall establish processes and procedures for continuous monitoring (ConMon) of Contractor systems that contain TSA data/information by ensuring all such devices are monitored by, and report to, the TSA Security Operations Center (SOC). The Contractor shall perform monthly security scans on servers and other required assets that contain TSA data and shall send monthly scan results to the TSA IAD.

B.11. Contingency Planning:

a) The Contractor shall develop and maintain a Contingency Plan (CP), to include a Continuity of Operation Plan (COOP), to address circumstances whereby normal operations may be disrupted and thus requiring activation of the CP and/or COOP. The contractor’s CP/COOP responsibility relates only to the approved system(s) they provide or operate under contract. Additionally, the CP/COOP shall align to a Business Impact Analysis (BIA), which establishes processes for identifying the critical information and services of TSA systems, IT assets, and the resources required to support them.

b) The Contractor shall ensure that contingency plans are consistent with template provided in DHS Mandated System of Record. If access has not been provided initially, the contractor shall use the DHS 4300A, Attachment K IT Contingency Plan Template.

c) The Contractor shall identify and train all TSA personnel involved with COOP efforts in the procedures and logistics of the disaster recovery and business continuity plans.

d) The Contractor shall test their CP annually and retain records of the annual CP testing for review during periodic audits.

e) The Contractor shall record, track, and correct any CP deficiency; any deficiency correction that cannot be accomplished within one month of the annual test shall be elevated to IAD management.

f) The Contractor shall have an up-to-date Emergency Response Plan (ERP), Backup Operations Plan (BOP) and a Post-Disaster Recovery Plan (PDRP).

https://usdhs.sharepoint.com/sites/dhsconnect/search/Pages/default.aspx?k=2%2E%09DHS%20Sensitive%20Systems%20Configuration%20Guidance#k=Configuration%20Guidance https://csrc.nist.gov/Projects/United-States-Government-Configuration-Baseline/FAQs#yJUv https://csrc.nist.gov/Projects/United-States-Government-Configuration-Baseline/FAQs#yJUv

g) The Contractor shall ensure all TSA data (e.g., email servers, data servers, etc.) is incrementally backed up daily.

h) The Contractor shall ensure a full backup of all network data occurs as required by the system’s availability security categorization impact rating per the TSA ISSP PD.

i) The Contractor shall ensure backup of data to facilitate a full operational recovery within one (1) business day at either the prime operational site or the designated alternate/backup site in accordance with local disaster recovery plan.

j) The Contractor shall ensure that data at the secondary location is current as required by the system’s availability security categorization impact rating.

B.12. Program Performance and Audit:

a) The Contractor shall comply with requests to be audited and provide responses within three (3) business days to requests for data, information, and analysis from the TSA IAD and management, as directed by the CO. These audits shall include, but are not limited to, requests for system access for penetration testing, vulnerability scanning, incident response and forensic review.

b) Upon completion of monthly security scans, findings shall be documented and categorized as High, Moderate, or Low based on their potential impact to the System IT security posture.

c) The Contractor shall afford DHS/TSA access to the Contractor’s facilities, installations, operations, documentation, databases, and personnel used in the performance of this contract.

B.13. Data Stored/Processed at Contractor Site:

a) Unless otherwise directed by TSA, any storage of data shall be contained within approved resources allocated by the Contractor (and approved by TSA) to support TSA and may not be on systems that are shared with other commercial or government entities or clients.

b) The AO shall approve the use of any contractor portable storage media on external systems.

c) The SO shall ensure the approved alternate storage site is physically secured to an equivalency of the primary storage site, using access controls.

B.14. Remote Access:

a) Any TSA-approved Contractor remote access connection to TSA networks shall be considered a privileged arrangement for both Contractor and the Government to conduct sanctioned TSA business. Therefore, remote access rights shall be expressly granted, in writing, by the TSA AO.

b) Any unauthorized Contractor employee(s) remote access connection to TSA networks shall be terminated immediately at the sole discretion of TSA.

c) The Contractor shall use his or her federally issued and approved personal identity verification (PIV) credential/identification badge to access TSA resources to include IT applications and physical facility.

B.15. Disposition or decommission of Government Resources:

a) At the expiration of the contract, the contractor shall return all TSA information and IT resources provided to the contractor during the contract and provide signed certifications that all assets containing or used to process TSA information have been sanitized in accordance with the TSA MD 1400.28 ISSP, TSA ISSP PD, Technical Standards and SOPs. The contractor shall certify in writing that sanitization or destruction has been performed. Sanitization and destruction methods are outlined in the NIST Special Publication 800-88 Guidelines for Media Sanitization, TSA Technical Standard 046 IT Media Sanitization and Disposition, and SOP 1400-503 IT Media Sanitization. The contractor shall email TSA, PM, CO, and COR a signed certification by the contractor’s designated senior security officer or senior official, signed proof of sanitization. In addition, the contractor shall provide the TSA CO a master asset inventory list that reflects all assets, government furnished equipment (GFE) or authorized non-GFE that were used to process and store TSA information.

B.16. Software Guidance:

The CO shall provide a listing of all TSA approved security software upon contract award. The approved security software listing is maintained by the IAD.

a) In support of the CDM objective to protect high value assets (HVAs) and information, the TSA has acquired security tools to conduct Indicator of Compromise (IOC) scans within the mandated time frame. The Government shall provide the tool license and/or equipment for installation of tool agents on all TSA supported assets.

b) The contractor shall support efforts to allow for the IOC scanning mandate. This may include installation of tool servers and/or agents within each system’s environment and on all TSA supported assets. The Government shall provide the contractor with the tool server(s) that shall not belong to the contractor’s system boundary. The tool server shall be reachable from OneNet/TSANet over the Internet. The tool server(s) shall be properly configured to reach all assets with the tool agent installed on the network. Credentials (service accounts) shall be provided for IOC scans and tool interrogation.

c) The contractor shall support or perform the installation of forensic software servlet agents on supported Operating Systems on all TSA contract supported devices and environments per TSA engineering, security, and configuration standards. The contractor shall test and upgrade the servlet agents as directed by the IAD.

d) The Government shall provide the contractor with a forensic software server that shall not belong to the contractor’s system boundary. The contractor shall support or perform the installation of the server. The server shall be reachable from TSANet over the Internet and shall be primarily used for authentication and proxy functions. The server shall be properly configured to reach all assets with the agent installed on the network.

e) The contractor shall support efforts of incident response and forensic investigation. This includes authorization to connect TSA authorized equipment where the forensic software servlet agents are reachable to perform analysis.

f) The contractor shall install TSA-provided solution patches within two (2) days of issuance, or as directed by TSA CIO, and provide evidence of implementation to the TSA

ISSO.

g) End-of-Life (EOL) / End-of-Service (EOS):

1) The Contractor shall ensure that any hardware, software, or application that is procured develops a full lifecycle plan based on the vendor’s established life and service expectancy of the product and total cost of ownership. Any new or existing product that shall reach end-of-life (EOL)* within three (3) years and is part of a TSA FISMA IT System shall require development of a remediation, upgrade, replacement, and funding plan to remove the EOL item(s) from the TSA environment completely within that time frame. A plan of action and milestone (POA&M) shall be submitted for risk acceptance to the TSA CISO to track remediation milestones appropriately.

*EOL / EOS - Defined as production and/or development, technical support, application updates, spare parts and security patches which are no longer available from the vendor.

B.17. Maintenance:

a) The Contractor shall ensure that the system, once operational, is properly and securely maintained and monitored, to include immediate response to critical security patches, routine maintenance windows to allow for system updates, and compliance with a defined configuration management process. All patches and system updates shall be properly tested and approved in a development environment before being implemented in the production environment.

b) The contractor shall perform customer support twenty-four (24) hours, seven (7) days a week (i.e., 24/7) within the Continental United States (i.e., CONUS) only.

C. Continuous Diagnostics and Mitigation:

C1. The Government, through a Continuous Monitoring as a Service (CMaaS) vendor, shall provide the contractor with GFE appliances and tools to support the implementation and maintenance of the Continuous Diagnostics and Mitigation (CDM) Solution. The tools shall be hosted on the DHS’ Infrastructure as a Service (IaaS) program. The Government, through the CMaaS vendor, shall provide sensor kits, appliances, probes, and agents that shall be deployed on all contractor Information Systems supporting the TSA.

C2. The contractor shall support the installation (including rack and configuration) of sensor kits, appliances, probes, and agents on all TSA contract supported devices and environments per TSA engineering, security, and configuration standards.

C3. The contractor shall configure/tune their existing endpoint security products to coexist with the identified products to ensure smooth and cohesive functionalities. Credentials (service accounts) shall be provided by the TSA CISO, or designee, for vulnerability scans and host interrogation.

C4. The Government, through the CMaaS vendor, shall provide the following support for operations and maintenance of the CDM solution sensor kits:

a) Patching (Controlled through a CMaaS Windows Server Update Service (WSUS))

b) Hardware troubleshooting & Risk Management (RMA)

c) Application maintenance (done from the Government/TSA Management Enclave)

d) Vulnerability scanning

C5. The contractor shall install TSA-provided CDM Solution patches within two (2) days of issuance, or as directed by TSA, and provide evidence of implementation to the TSA ISSO.

C6. The TSA CO (as approved and on behalf of the SO and TSA senior leadership) is authorized to provide technical direction to the contractor for the sole purpose of implementing the CDM Solution. If the technical direction results in any cost incurred by the contractor, for which the contractor shall seek reimbursement from the Government, the contractor shall identify the following information in any cost/price proposal to the Government: name of system owner, summary of the technical direction, date of the technical direction, purpose of the technical direction, summary of actions taken by the contractor, any other information the CO may require to further guide the directed change. The contactor shall receive approval from the CO of the directed and approved change prior to incurring costs associated with the technical direction.

C7. Personal Identity Verification (PIV) and Login:

a) The Contractor shall use PIV credential/identification badges as the primary means to access TSA resources to include IT applications and physical facility. TSA network domain user account password expiration function shall be disabled when using PIV Machine Based Enforcement (MBE). PINs for PIV card-enabled users shall not expire and shall have a minimum six-digit PIN when logging into the network using a PIV card.

b) The Contractor shall ensure newly developed information system(s) support PIV card authentication. The information system shall be capable to accept and electronically verify PIV credentials.

c) The Contractor shall employ information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational information systems.

d) The Homeland Security Presidential Directive 12 (HSPD-12) requires the use of the approved PIV credentials as the common means of authentication for access to DHS/TSA facilities, networks, and information systems. PIV credentials shall be used as the primary means of authentication for DHS/TSA sensitive IT systems. The Contractor shall use his or her federal issued PIV credentials to access TSA resources to include IT applications and physical facility.

e) The DHS/TSA Security Office shall be notified of all terminations/resignations within five (5) days of occurrence. The Contractor shall return to the Contracting Officer Representative (COR) all DHS issued PIV credentials/identification cards and building passes that have either expired or have been collected from terminated employees. If a PIV credential/identification card or building pass is not available to be returned, a report shall be submitted to the COR, referencing the PIV credential, pass or card number, name of individual to who it was issued and the last known location and disposition of the PIV credential, pass or any other TSA-issued cards.

f) The contract ISSO shall determine and enforce the appropriate frequency for changing passwords/PINs in accordance with appropriate guidance documentation along with the use of a second factor authentication to follow Executive Order 14028 “Improving the Nation’s Cybersecurity” for Multi-factor Authentication (MFA). In the absence of specific guidance, where applicable, passwords shall not remain in effect longer than ninety (90) days.

D. Federal Risk and Authorization Management Program (FedRAMP):

D1. If a vendor is to host a system with an approved Cloud Service Provider (CSP), the CSP and shall adhere to the following:

a) Comply with Federal Agency cloud requirements per CCSH;

b) Identity and entitlement access management shall be done through Federated Identity;

c) SSI, PII and SPII shall be encrypted in storage and in transit as it is dispersed across the cloud;

d) Sanitization of all TSA data shall be done as necessary at the IaaS, PaaS, or SaaS levels;

e) Cloud bursting shall not occur;

f) TSA data shall be logically separated from other cloud tenants;

g) All system administrators shall be properly cleared and vetted U.S. citizens;

h) TSA data shall not leave the United States; and

i) The cloud internet connection shall route via an approved DHS Trusted Internet Connection (TIC) and intrusion detection system (IDS). These include but are not limited to the analysis of network flow records, detecting, and alerting to known or suspected cyber threats, intrusion prevention capabilities and under the direction of DHS detecting and blocking known or suspected cyber threats using indicators. The IDS capability shall use the Domain Name Server Sinkholing capability and email filtering capability allowing scans to occur destined for .gov networks with malicious attachments, Uniform Resource Locators, and other forms of malware before being delivered to *.gov end-users.

D2. Private Sector System Requirements: TSA shall conduct audits at any time on approved private sector systems, and the system shall be entered into the TSA FISMA Inventory as a system of record (SOR) using the Control Implementation Summary (CIS) provided by the Cloud Service Provider. Security artifacts shall be created and maintained in the DHS Mandated System of Record. The private sector systems are required to go through the Security Authorization Process and the RMF in accordance the Federal Information Systems Management Act (FISMA) and NIST SP 800-37. The cloud internet connection shall be behind a commercial Trusted Internet Connection (TIC) that has an approved IDS deployed. Security event logs and application logs shall be sent to the TSA SOC. Incidents as defined in the TSA MD 1400.28 ISSP, and its Attachment 1 (TSA ISSP PD and TSA ODP) shall be reported to the TSA SPOC 1- 800-253-8571. DHS Information Security Vulnerability Management Alerts and Bulletins shall be patched within the required time frames as dictated by DHS and communicated by the COR or contract security point of contact (POC).

E. Interconnection Security Agreement (where applicable):

If the service being supplied requires a connection to an outside non-DHS/non-TSA Contractor system, or DHS system of different sensitivity, the following shall apply:

E1. Interconnections between DHS/TSA and non-DHS/TSA IT systems (i.e., Contractor Owned Contractor Operated (COCO) systems) shall be established only through authorized contractual agreements and funding, controlled interfaces and via approved service providers. The controlled interfaces shall be accredited at the highest security level of information security on the network. Connections with other Federal agencies shall be documented using an approved Interagency Agreements (IAA); Memoranda of Understanding/Agreement (MOU/MOA), Service Level Agreements (SLA) or Interconnection Service Agreements (ISA).

E2. ISAs shall be reissued every three (3) years or whenever any significant changes have been made to any of the interconnected systems.

E3. ISAs shall be reviewed and updated as needed as a part of the annual FISMA self-assessment.

1.2 ITAR SME Cybersecurity Supply Chain Risk Management (C-SCRM)

Cybersecurity C-SCRM language is applicable for requirements for the use of supplies and services to include the following:

a. Definitions:

i. Component: a unit defined by the supplier that connects to and functions as part of the product. For software products, a component is a unit of software defined by a supplier at the time the component is built, packaged, or delivered. For hardware, a component is one hardware unit designed to connect to and function as part of a larger product.

ii. End-of-Life (EOL): means that an ICT product has reached the final stage of the product life cycle in which that version of the ICT product will no longer be supported nor manufactured (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iii. End-of-Support (EOS): means that an ICT product will no longer be supported (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iv. Information and Communications Technology (ICT): encompasses the capture, storage, retrieval, processing, display, representation, presentation, organization, management, security, transfer, and interchange of data and information; includes all categories of ubiquitous technology used for the gathering, storing, transmitting, retrieving, or processing of information (e.g., microelectronics, printed circuit boards, computing systems, software, signal processors, mobile telephony, satellite communications, and networks).

v. Product: part of the equipment (hardware, software and materials) for which usability is to be specified or evaluated.

b. Original Equipment Manufacturer (OEM) End-use Information and Communications Technology (ICT) Product:

i. The contractor shall provide new equipment unless otherwise formally approved by the Government, in writing. The contractor shall provide only Original Manufacturer (OEM) end-use products to the Government. In the event that a shipped OEM product, or part or component of that product, fails, all replacements must be new (i.e., non-refurbished, not previously used) OEM.

ii. The contractor may provide previously used OEM products only with written Government approval. Such parts shall be procured from their original source and shipped only from the manufacturer's authorized shipment points.

c. Accounting of Components in ICT Products:

i. The contractor shall provide and maintain a list of components for each product used in performance of the contract, including through subcontracts or other arrangements. This list for each product shall provide the component manufacturer's name, address, state, and/or domain of registration, and, where applicable, the Unique Entity Identifier (UEI) number, for all components comprising the ICT products.

ii. The contractor shall notify the Government when a new contractor/subcontractor/service provider is introduced to the ICT provided on this contract, or when suppliers of components or products are changed. If a software component used in the performance of the contract is updated with a new build or release, the contractor must update the list provided in accordance with (i) above to reflect the new version of the software. This includes software builds to integrate an updated component or dependency.

iii. For software products, the contractor shall provide all OEM software updates, and patches to correct defects, for the life of the product [i.e., until the "End of Life" (EoL) or "End of Support" (EoS)]. Software updates and patches shall be made available to the government for all products procured under this Contract and replaced when End of Support (EoS) is reached.

iv. A contractor using team members in performance of the contract (e.g., subcontractors or other service providers) shall ensure that the standards for the accounting of components in this subsection are met by team members.

d. Supply-Chain Transport:

i. The contractor shall use formal, documented, and accountable transit, storage, and delivery procedures (i.e., the possession of the end-use product to be delivered is documented at all times from initial shipping point to final destination, and every transfer of the product from one custodian to another is fully documented and accountable) for all information and communication technology (ICT) shipments to fulfill this contract.

ii. The contractor shall maintain all records pertaining to the transit, storage, and delivery of ICT deliverables under this contract through at least 6 months after acceptance and make available for inspection upon request of the Government.

iii. The contractor shall make use of tamper-proof or tamper-evident packaging for all shipments.

iv. The contractor shall provide a packing slip for each container or package with the information identifying the contract or order number, a description of the hardware/software enclosed (Manufacturer name, model number, serial number), and the customer point of contact.

v. The contractor shall provide a shipping notification to the intended government recipient;

with a copy transmitted to the Contracting Officer, or other designated representative.

This shipping notification shall be provided electronically and identify the contract or order number, a description of the hardware/software being shipped (manufacturer name, model number, serial number), initial shipper, shipping date and identifying (tracking) number.

e. Changes to Ownership and Control:

The Contractor shall immediately notify the Contracting Officer and Contracting Officer's Representative regarding any significant changes to corporate ownership or control from contract award through final delivery or the end of the period of performance. A significant change would be one in which a change occurs in the individuals or entities who, directly or indirectly, either

(1) exercises substantial control over an entity, or (2) owns or controls at least 25 percent of the ownership interests of an entity.

1.3 DHS-TSA Enterprise Architecture Compliance (update as of December 2022)

a) The Contractor shall ensure that all architectural artifacts including but not limited to solutions, business, Data, IT elements for legacy Transportation Security Equipment (TSE), Information Systems Security Agreements (ISSAs), System Design documents (SDDs), deliverables, and services are aligned and compliant with the current DHS and TSA Enterprise Architecture, the Common Approach to Federal Enterprise Architecture, the Technology Business Management (TBM) Taxonomy, and Federal Information Technology Acquisition Reform Act (FITARA).

i. All solutions and services shall meet DHS and TSA Enterprise Architecture policies, standards, and procedures. Specifically:

1. DHS and TSA Enterprise Architecture policies, standards, and procedures.

2. Homeland Security Enterprise Architecture (HLS EA) and TSA EA requirements.

3. TSA and DHS IT Security, Cloud, Infrastructure (including Network), Application/Systems, Information/Data, Performance, and Business Architecture policies, directives, guidelines, standards, segment architectures and reference architectures.

4. TSA functional capabilities

5. TSA operational capabilities

6. TSA lines of business

7. TSA business processes

8. TSA funding sources

9. TBM Taxonomy for IT cost transparency

ii. All software and tools that are used to build, develop, or deploy IT solutions for TSA, shall leverage the TSA NextGen Architecture (NGA) Technology Stack known as “The Kit”. In accordance with TSA CIO Priority 2.1 “Modernize, Simplify, Reduce and Enforce TSA IT and Data Toolkit”, use of “the Kit” will achieve modernization and simplification, with the ultimate goal of reducing the current TSA Technology Footprint.

iii. This includes new Transportation Security Equipment (TSE) and Legacy TSE that utilizes IT software, services, or equipment including embedded IT elements such as network switches, routers, In printers, etc.

iv. All solutions shall implement, and leverage TSA information and data standards as defined and approved per TSA policy.

v. All solution architectures and services (e.g., Application, System, Network, Security, Information/Data, Cloud) shall be reviewed and approved by TSA EA as part of the TSA SELC (System Engineering Life Cycle) review process and in accordance with TSA IT Governance Management Directive 1400.20 with applicable DHS and TSA IT governance policies, directives, and processes. This includes the Solution Engineering Review (SER), Preliminary Design Review (PDR) and Critical Design Review (CDR) stage gates. The required design artifacts include solution approach document, the PDR document, and System Design Document (SDD) as directed by EAD. Successful completion of the PDR/CDR stages results in an approved architecture which is required before proceeding to development. An approved architecture is also a necessary critical step in receiving an Authority to Operate (ATO). All implementations shall follow the approved solution architecture/design without deviation. Any changes, to either the prior approved solution and/or prior approved design that are identified during subsequent SELC phases, including testing, implementation and deployment, shall undergo additional EA review prior to proceeding.

vi. TSA Offices acquiring Enterprise architecture type services at segment or solution levels shall engage and collaborate with the TSA Enterprise Architecture Division (EAD) to ensure strategic alignment of people, process, information, and technology and comply with enterprise level architecture governance, artifacts and standards.

a. The Contractor shall engage domain architect(s) in EAD before SELC Obtain Phase, i.e., during SELC Need or “Analyze and Select” Phase.

b. The Contractors shall collaborate with the EA domain architect(s) to deliver the required design artifacts and desired outcome under the guidance.

c. The Contractor shall provide architecture and system/application data and models in prescribed formats to be stored in TSA's Enterprise Architecture Repository.

b) In accordance with the TSA Cloud Strategy 2.0, April 2019, TSA's approach to cloud computing and governance of migration to the cloud, the contractor shall ensure that the cloud solutions utilize the SaaS (Software as a Service) model as its primary approach to cloud implementation, and also, when necessary, will use Platform as a Service (PaaS) or Infrastructure as a Service (IaaS). The contractor shall adhere to the principles of cloud strategy to systematically retire or replace legacy applications by use of an integrated approach to cloud planning, architecture, hybrid deployment, and operation.

c) Applicability of Internet Protocol Version 6 (IPv6) to DHS-related components (networks, infrastructure, and applications) specific to individual acquisitions shall be in accordance with the DHS Enterprise Architecture (per OMB Memorandum M-21-07, November 2020) regardless of whether the acquisition is for modification, upgrade, or replacement. All EA related component acquisitions shall be IPv6 compliant as defined in the U.S. Government Version 6 (USGv6) Profile (National Institute of Standards and Technology (NIST) Special Publication 500-267) and the corresponding declarations of conformance defined in the USGv6 Test Program.

Information and Data Governance and Management https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf

d) The Contractor shall develop, use, and dispose of TSA information and data assets following the TSA governance processes established by the Enterprise Information/Data Governance Board (EIDGB), in compliance with the DHS Enterprise Data Governance and Management MD (Management Directive) 103-01.

i. TSA information and data assets include but are not limited to the TSA Data Catalog, TSA information and data standards, TSA Data Management Plan, TSA data sets (including open data sets for public consumption), TSA information and data stored in TSA repositories, TSA information and data in systems and applications (internal and external), and TSA information exchanges.

ii. All TSA information and data, and all solutions that capture, store, use and provide TSA information and data shall comply with the Geospatial Data Act (GDA) of 2018 (P.L.

115-254) that requires agencies to foster efficient management of geospatial data/information, technologies, and infrastructure through enhanced coordination among Federal, state, local, and tribal governments, along with…