Statement of Objective (SOO)

Enterprise Network Management System (ENMS)

1. Objective: The objective of this requirement is to acquire and deploy an Enterprise Network

Management System (ENMS) that delivers comprehensive visibility, monitoring, modeling, analytics, and assurance capabilities across the United States Transportation Command (USTRANSCOM) enterprise network environment, including on-premises, cloud, and hybrid infrastructures, to improve operational awareness, network reliability, security posture, and mission assurance. The solution shall facilitate authoritative topology discovery, performance monitoring, fault detection, path analysis, configuration validation, and reporting while maintaining dual-stack Internet Protocol version 4 (IPv4) and IPv6 operations, including IPv6-exclusive environments, and alignment with Zero Trust principles. This requirement includes both the procurement of enterprise software licenses; professional services necessary to aid initial implementation, configuration, and integration with existing enterprise systems and security platforms, data ingestion and normalization, API integration where required; and structured knowledge transfer to confirm a deliberate transition to sustained government-led operations once full operational capability is achieved. Full operational capability is defined as the NMS being fully functional in the production environment, meeting all performance requirements specified in this SOO, having USTRANSCOM personnel trained for system operation and maintenance

2. Scope: Requirements for the USTRANSCOM ENMS solution shall include comprehensive network monitoring, topology discovery, performance management, fault detection, configuration and state validation, path analysis, reporting, and secure data export across both the Non-classified Internet Protocol Router (NIPR) Network and the Secure Internet Protocol Router (SIPR) Network enclaves. The NIPRNet environment maintains approximately ten thousand end devices and associated network infrastructure components, and the SIPRNet environment maintains approximately five thousand end devices and associated infrastructure. The solution shall be capable of operating across multiple geographically separated facilities and must achieve high availability of 99% uptime for all NMS components, excluding scheduled maintenance; scalability to accommodate a 20% growth in monitored devices over performance of the contract without performance degradation; and enterprise resiliency through automated failover to a secondary server in less than 15 minutes with no more than 5 minutes of data loss.

a) The scope of this project involves the implementation of an ENMS platform across two separate enclaves at Scott Air Force Base (AFB), one assisting with the unclassified enterprise network and one assisting with the classified enterprise network.

USTRANSCOM requires a centralized NMS capability to provide topology discovery, performance monitoring, fault management, configuration validation, and path analysis across core, access, security, and cloud-connected (Azure, AWS) infrastructure.

Engineering resources are required to evaluate the existing architecture, install and configure platform components and collectors, integrate the solution with enterprise identity, logging, and configuration management systems, and validate functionality through a phased deployment. The solution shall comply with applicable Department of

War (DoW) Security Technical Implementation Guides (STIG) and cybersecurity requirements. Professional services shall include knowledge transfer for transition to government-led sustainment, and all classified enclave assistance shall be performed by appropriately cleared personnel.

b) The existing enterprise network environment and integrated systems (NIPRNet/SIPRNet) include:

• On-Premises Infrastructure o Core and distribution routing platforms maintaining enterprise Wide Area Network (WAN) and data center connectivity o Access layer switching infrastructure maintaining approximately 10,000 NIPRNet and 5,000 SIPRNet endpoints o Palo Alto Networks firewalls providing boundary protection and internal segmentation o Cisco Firepower platforms managed through Cisco Firepower Management Center (FMC) o Cisco Software-Defined (SD) WAN infrastructure maintaining transport and edge connectivity o Out-of-band management infrastructure maintaining device administration o Cisco Catalyst Center maintaining network automation and assurance functions o Remedy and ServiceNow platforms maintaining incident, change, and service management workflows o Configuration and asset management systems maintaining inventory synchronization and lifecycle tracking o Cloud-hosted enterprise services operating within hybrid connectivity models o Secure transport connections between on-premises and cloud infrastructure o Dual-stack IPv4 and IPv6 routing environments maintaining enterprise modernization initiatives

c) The ENMS shall maintain enterprise-scale operations across both enclaves, including monitoring and analysis of approximately 10,000 NIPRNet endpoints and 5,000 SIPRNet endpoints, in addition to more than 300 network infrastructure devices consisting of core, distribution, access, firewall, SD WAN, and boundary protection platforms. The solution shall also maintain visibility and monitoring of more than 50 enterprise encryption devices maintaining classified and unclassified transport connectivity. The platform shall be built for high availability within each enclave and sized to accommodate projected enterprise growth. Initial implementation shall include phased onboarding of priority infrastructure and encryption devices, validation of monitoring coverage and data integrity, configuration of alerting and escalation workflows aligned with existing operational processes, and establishment of data retention policies consistent with cybersecurity and audit requirements. The system shall operate successfully within dual-stack IPv4 and IPv6 environments without degradation of monitoring performance.

d) On each enclave (NIPRNet and SIPRNet), the provider shall:

• Perform an initial architecture review and deployment planning session to validate sizing, collector placement, high availability design, and integration approach.

• Install and configure required platform components, collectors, and maintaining services within the enterprise environment in accordance with DoD cybersecurity policies and STIGs.

• Configure secure device access, credential management, role-based access controls, and authentication integration with existing identity services.

• Onboard core, distribution, access, firewall, SD WAN, and encryption devices in a phased approach and validate monitoring accuracy, telemetry ingestion, and system performance.

• Integrate the NMS with Cisco Identity Services Engine, Cisco Catalyst Center, Cisco SD WAN, Palo Alto, and Cisco FMC platforms, Assured Compliance Assessment Solutions (ACAS), Tanium, and enterprise service management systems, including Remedy and ServiceNow, through authorized interfaces and application programming interfaces as determined by USTRANSCOM.

• Configure alerting thresholds, escalation workflows, dashboards, and reporting views aligned with enterprise operational processes.

• Conduct functional testing and operational validation in coordination with USTRANSCOM personnel before system acceptance.

• Provide structured knowledge transfer, administrator training, implementation documentation, and standard operating procedures to allow for transition to government-led sustainment.

e) Continuous Network Assurance and Compliance: USTRANSCOM intends to implement a continuous network assurance capability leveraging the ENMS in coordination with existing enterprise security, compliance, and service management platforms across both enclaves. The purpose is to provide continuous visibility into network device health, configuration compliance, segmentation posture, authentication telemetry, encryption transport dependencies, and operational risk indicators across more than 300 network devices and more than 50 encryption devices maintaining both NIPRNet and SIPRNet operations.

• The solution shall utilize a Hybrid Central deployment model in which the primary

NMS platform is hosted on premises within each enclave, with secure, encrypted connectivity established to ingest telemetry and configuration data from cloud-hosted environments and remote network segments.

• The architecture shall consist of two (2) primary NMS instances, one deployed within the NIPRNet enclave and one deployed within the SIPRNet enclave, each configured as one (1) high availability pair located at Scott AFB.

• Each enclave shall include one (1) primary server and one (1) secondary server configured in an active standby or equivalent high availability configuration to verify continuity of monitoring operations.

• Secure VPN, Direct Connect, or approved encrypted transport mechanisms shall be utilized for cloud and remote site telemetry ingestion.

• The provider shall configure and validate integration points necessary to ingest telemetry, configuration state data, and event information from Cisco Identity Services Engine, Cisco Catalyst Center, Cisco SD WAN, Palo Alto, Cisco FMC, ACAS, Tanium, and enterprise service management platforms, including Remedy and ServiceNow.

• The solution shall maintain automated alerting, reporting of configuration deviations, performance degradation, and change impact visibility across both enclaves.

• All components deployed within the classified enclave shall reside on approved infrastructure and be implemented by personnel holding the appropriate security clearance.

3. Place of Performance: Services will be performed at USTRANSCOM, Command, Control, Communications, and Cyber Systems Directorate, Building 1961, 508 Scott Drive, Scott AFB, IL 62225. Anticipated service dates: September 2026 through March 2027.

4. Deliverables (One (1) each for NIPRNet and SIPRNet): The following deliverables are required for successful project completion.

The USTRANSCOM shall have unlimited rights to all data and deliverables developed, in accordance with FAR 52.227-14. There shall be a set of deliverables for each enclave (NIPRNet/SIPRNet)

• Project Initiation/Project Kick Off

• Pre-Deployment Guide

• Acceptance Testing Procedures (ATP)

• As-Built Documentation

• Low-Level Design

• High-Level Design (HLD)

5. Project Tasks (One (1) each for NIPRNet and SIPRNet):

a) Onsite Project Kickoff

(1) Define roles and responsibilities of government and contractor project team members

(2) Articulate project objectives, priorities, technologies being deployed, and key deliverables.

(3) Identify work required to achieve project goals

(4) Establish a high-level schedule

(5) Identify major project risks and develop strategies for mitigating them

(6) Identify dependencies, and plan project success criteria

(7) Jointly define milestones and due dates

(8) Develop the initial framework and outline for the ATP

1. The ATP must be designed to comprehensively validate all critical system capabilities, including monitoring coverage, integration functionality, high availability failover, and reporting. The duration of the final ATP execution will be mutually agreed upon by the contractor and the government based on the scope defined in the final, approved ATP document.

b) Design

(1) Develop HLD for the NIPRNet Hybrid Central deployment, including high availability architecture, collector placement, integration points, and secure data flows.

(2) Develop HLD for the SIPRNet deployment, including enclave boundary protections, classified infrastructure placement, and secure telemetry ingestion architecture.

(3) Validate STIG compliance alignment and cybersecurity control integration within each enclave design.

c) Solution Engagement

(1) Enterprise Readiness and Integration Assessment: Contractor shall conduct a detailed assessment to validate the readiness of the USTRANSCOM environment for deployment. This assessment must include, at a minimum:

1. Verification that target network devices (over 300) and encryption devices

(over 50) maintain the required monitoring protocols (e.g., Simple Network Management Protocol, Application Programming Interface, Command Line Interface).

2. Confirmation of network connectivity from the NMS collection points to all in-scope devices.

3. Validation of the provided government infrastructure (servers/Virtual Machines) against the NMS vendor’s hardware and software requirements.

4. An inventory of required credentials and verification of access permissions.

5. Identification of technical prerequisites for integration with enterprise systems, including ServiceNow, Remedy, and Infoblox.

(2) A final report detailing the findings, identifying any gaps or risks, and providing a remediation plan. Informal Knowledge Transfer: Provide informal, ongoing knowledge transfer and hands-on training to USTRANSCOM personnel throughout the implementation and integration process.

1. Solution Implementation and Integration: Perform the full implementation and integration of the solution using a phased approach. The scope and timeline of each phase will be mutually agreed upon during the Project Kickoff and documented in the Project Management Plan.

(3)

(4) Conduct comprehensive testing of the deployed solution to validate functionality, performance, and successful integration, as measured against the government-approved ATP.

(5) Cutover - Up to ten (10) cutovers or migration windows through the duration of this project

d) Documentation

(1) Finalized architecture diagrams for each enclave.

(2) Integration mapping documentation and data flow diagrams.

(3) Configuration baselines and operational procedures.

(4) Administrator guides sustainment documentation maintaining transition to government-led operations.

e) Formal NMS Training.

(1) Provide formal administrator-level training for up to twelve (12) government personnel covering system administration, integration management, reporting configuration, troubleshooting, and operational sustainment.

(2) Training shall include practical hands-on exercises aligned to the deployed enterprise architecture within both enclaves.

6. Security (Physical, Personnel, Information, Industrial) and Antiterrorism

a) Security (Industrial, Personnel, Physical, Information, and Antiterrorism/Force

Protection)General Security Requirements Information/Applicability: The majority of daily work associated with this PWS/SOW is at the unclassified level, but contractor personnel may be required to access classified information/systems at the SECRET level, and/or classified areas at the SECRET level, during the performance of this contract/task order. FAR Clause 52.204-2, Security Requirements, applies to the extent of this contract/task order involving access to information, areas, or material classified “CONFIDENTIAL” or “SECRET”. Specific security protocols for contracted companies are outlined in 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), identified in this section of the SOO, and the DD Form 254 (DoD Contractor Security Classification Specification). A completed/signed DD Form 254 will be attached to the contract/task order.

b) Operational Security (OPSEC): OPSEC requirements shall be in effect throughout the life of the procurement from award through the conclusion of services at the end of the period of performance or other procurement termination. In any case where uncertainty or ambiguity regarding OPSEC measures exists, the contractor shall consult the requirements or contracting office’s OPSEC coordinator as soon as possible.

c) Citizenship and Clearance Requirements: All personnel that will have Information

Technology (IT)/Automated Data Processing (ADP) privileged access (i.e. Privileged Users) to US Information Systems (IS), and/or classified information, classified systems, or classified areas, shall be US citizens. Foreign Nationals or Local Nationals employed by the DoD are not authorized to have privileged access to US Information Systems.

Overall, all contractors’, subcontractors’ and/or partner’s personnel shall possess the appropriate personnel security investigation for the position(s) occupied. Contractor personnel shall be required to have a background investigation that corresponds with the sensitivity level of the tasks to be performed. Non-US citizens are not eligible for Common Access Cards (CACs) unless they meet the parameters stated in Department of Defense Manual (DoDM) 1000.13, Volume 1.

d) Information Systems (IS) Roles/Categories and Associated Suitability Requirements

(Federal Investigative Standards): Contractor personnel with IA administrative privileges and/or who will monitor DoD IT systems or software as designated by DoD

Instruction 8500.01 and DoD Manual 5200.02 may be rated at the various levels listed below. The IS roles/categories and the number of personnel assigned to each role is approved by the COR or the CO before the start of the contract/task order. The contractor shall comply with the appropriate provisions of applicable security regulations while assigned to this contract/task order for DOD and USTRANSCOM. The following guidance will be followed when determining background investigation levels for this contract/task order depending on requirements:

IS Role/Category Classified Access Required Investigation General User (Non-Privileged Access) (IT/ADP-III, Non-Sensitive)

NO Tier 1 (T1)

General User (Non-Privileged Access) (IT/ADP-II, Non-Critical Sensitive)

YES Tier 3 (T3)

Privileged User (e.g. System Administrator) (IT/ADP-I, Critical Sensitive)

NO Tier 5 (T5)

Privileged User (IT/ADP-I, Critical Sensitive)

YES Tier 5 (T5)

NOTE: USTRANSCOM Joint Security Office (TCCS-S) will initiate/administer Tier 1 investigations to determine CAC eligibility only, classified access will not be granted based on the Tier 1 investigation. Tier 3 and Tier 5 investigations are the responsibility of the contractor. It is incumbent upon the contractor to have the appropriate investigations completed upon the start of the contract/task order.

e) Security Clearance and Special Access Requirements: All positions on this contract/task order require a minimum of either an interim SECRET granted by the Defense Counterintelligence and Security Agency (DCSA) Adjudication & Vetting Services (AVS), or a completed adjudication of SECRET granted by the DCSA AVS.

f) Facilities Clearance (FCL): The contractor must have a valid FCL at the SECRET level.

FCL procedures and security guidelines for adjudicative requirements are outlined in 32 CFR, Part 117. FCLs must be awarded by the Defense Counterintelligence and Security Agency (DCSA) Entity Vetting Branch.

g) Personnel and Facilities Clearance Validation: Upon contract/task order award, the USTRANSCOM contracting team will send TCCS-S the contractor cage code for FCL verification via the National Industrial Security System (NISS). The contractor will submit names of the contractor personnel performing on the contract/task order to the USTRANSCOM contracting team, who will provide TCCS-S for vetting through the DoD personnel security system of record to verify investigative and clearance requirements have been satisfied. This shall be completed before the COR/Mission Partner Affiliation Sponsor (MPAS) accesses the Mission Partner Identity, Credential, and Access Management (MP ICAM) system and creates CAC applications for contractor personnel. If a contractor’s employee does not have the required investigative or security clearance level based on the Government’s determination, the contractor’s employee will be denied the ability to work in assistance of this contract/task order.

h) Common Access Card (CAC) Issuance Procedures:

Facility Security Officer (FSO) will verify, via the DOD personnel security system of record, contractors on the contract/task order have the required background investigation to obtain a CAC and provide those names to the CO/COR. Contractors that require a Tier 3 or Tier 5 investigation are the responsibility of the contractor. Contractors that only require a Tier 1 as determined by the FSO will submit to the TCCS-S Personnel Security Program Manager (through the CO or COR) an OF Form 306 (Declaration for Federal Employment) and a MP ICAM Form 1 with Section 1 completed. TCCS-S will initiate the SF-85 (questionnaire for Non-Sensitive Positions) via the National Background Investigation Services (NBIS) for completion and submission to DCSA, for Tier 1 investigations only.

At the same time, the contractor company will coordinate and obtain electronic fingerprinting for their employee. The third-party company will “electronically” capture the applicant’s fingerprints, using the USTRANSCOM (Submitting Office (SON), Security Office (SOI), and Agency Location Code (ALC)). Hardcopy fingerprint cards are NOT acceptable. These steps shall be completed before the COR/MPAS accesses MP ICAM to create a CAC application.

i) Basic US Citizen Contractor CAC Requirements:

Requires access on a continual basis of 6 months or more.

Contractor personnel require access to a DoD facility or networks, either on-site or from a remote location. Users need access to systems for platforms that require CAC login or user authentication.

j) Basic Non-US Citizen Contractor CAC Requirements:

Meet (as direct/indirect DoD hire personnel), as identified in the DoDM 1000.13, Volume 1, the investigative requirements for DoD employment as recognized through international agreements pursuant to DoDI 1400.25, Civilian Personnel Management, Volume 1231. In addition to these investigative requirements, a fingerprint check against the FBI criminal history database, an FBI investigations files (name check search), and a name check against the Terrorist Screening Database shall be required prior to CAC issuance IAW Office of Personnel Management Memorandum, “Final Credentialing Standards for Issuing Personal Identity Verification Cards under HSPD-12”, July 31, 2008.

Possess (as foreign military, employee, or contract support personnel), a visit status and security assurance that has been confirmed, documented, and processed IAW international agreements pursuant to DoDI 1400.25, Civilian Personnel Management.

k) CAC Applications:

The CAC applications (MP ICAM Form 1 with Section 1 completed) must have an adjudication Tier 1, Tier 3, or Tier 5 background investigation posted in the DoD personnel security system of record, or An interim CAC may be approved when the contractor employee has a favorable fingerprint, name and criminal records check completed and has either a Tier 1, Tier 3, or Tier 5 background check “open” with DCSA.

The MP ICAM MPAS will not approve the CAC applications in MP ICAM until that MPAS has verified, with a member of USTRANSCOM TCCS-S, one of the above requirements.

l) Access to Scott Air Force Base or USTRANSCOM Facilities: Upon receipt of the

CAC, permanently assigned contractor personnel located at USTRANSCOM at Scott AFB (SAFB), IL, may obtain a USTRANSCOM Facility Access Badge if the employee will be assigned physically on SAFB in a USTRANSCOM-owned or managed facility, has a valid Visit Access Request on file, and attends Initial Security Training (IST) on-site. The Government will provide unrestricted access to facilities, consistent with security clearance eligibility and need-to-know, necessary for the on-site personnel to perform their work IAW the contract/task order. Contractor personnel assigned on-site at USTRANSCOM will wear and display the USTRANSCOM Facility Access Badge at all times while in USTRANSCOM facilities. Visits to SAFB by contractor personnel who do not possess the CAC will be facilitated by the COR/CO sponsoring the employee through the online base access system.

m) Visits by Non-Assigned Contractors to USTRANSCOM/SDDC Buildings: Any visit(s) by contractor personnel not permanently assigned to this contract/task order (i.e., company presidents, company security managers, contractor personnel not permanently assigned at SAFB, etc.) require an electronic visit access request be submitted using the DoD personnel security system of record. The DoD personnel security system of record visits can be forwarded to the Security Management Office (SMO) code: US- TRANSCOM-1. The visit access request shall annotate the contract/task order number in the POC block of the visit access request and the name/phone number of either the functional, COR or CO in the phone number block.

n) Visits by Permanently Assigned Contractors: Permanently assigned contractor employees on SAFB will require a visit access request for the current Period of Performance (PoP) posted in the DoD personnel security system of record to SMO: US- TRANSCOM-1. The visit access request will annotate the contract number in the POC block of the visit access request and the name/phone number of either the functional, COR or CO in the phone number block.

o) Supplemental Notes Regarding Visit Information in the DoD Personnel Security System of Record: Personnel requiring access to Government facilities will properly complete the “Visit Information” block in the DoD personnel security system of record.

Otherwise, contractor employees will be denied access to the facility and classified and/or sensitive information. Also, prime contractors will annotate their contract number and subcontractors will provide the name of their Company, with the prime contract number they are assigned to by the Prime, in the “additional information” block of the Visit table. A valid “Reason for the Visit” must be stated and the “visit access” must not exceed that of the contract.

p) Security and Emergency Operations Training: Contractor personnel physically assigned at USTRANSCOM at SAFB shall attend/complete the following training as prescribed by DoD, USTRANSCOM and Air Force Instructions: Initial Security, Workplace Violence, Annual Security Awareness, OPSEC, DOD Antiterrorism Level I, Active Shooter/Attacker, Emergency Operations, Combating Trafficking in Person (CTIP), Controlled Unclassified Information (CUI), Derivative Classification, and any Security Stand-down Day Training scheduled by the Commander, USTRANSCOM.

Contractor personnel assigned elsewhere shall attend security training established by their respective Government security offices and/or installations.

q) Additional Security Conditions: All contractors assigned to USTRANSCOM on SAFB will complete contractor in-processing before the start of work on this or any contract/task order in USTRANSCOM. Contractors starting work on a new contract/task order will report to the Joint Security Desk, located in Building 1900 first-floor breezeway. In-processing includes the following:

• Verification of personal identification

• Verification of Visit Access Request in the DoD personnel security system of record

• Verification of the contractor’s Security Clearance Eligibility in the DoD personnel security system of record

• Brief and sign the individual SF-312 (Security Agreement)

• Complete North Atlantic Treaty Organization (NATO) Indoctrination

• Review of Facility access requirements

• Issuance of a Temporary USTRANSCOM Facility Access Badge for the facility

• Creation of a personnel security file

r) Derogatory Information: Any member of the contracted company team (Program

Manager, FSO, or other supervisory staff) aware of pending human resource activity of consequence (to include termination or suspension), behaviors or patterns of concern, or misconduct, to include reporting requirements in accordance with Security Executive Agent Directive (SEAD) 3 (for contractors with classified security eligibility), for any contractors working under this contract/task order during the established period of performance, will immediately contact the USTRANSCOM Joint Security Office (TCCS-S) Attn: Industrial Security Program Manager. If the Government notifies the contractor that the employment or the continued employment of any contractor personnel is prejudicial to the interests or endangers the security of the United States of America and/or USTRANSCOM personnel, information, or assets; that employee shall be removed and barred from the worksite. This includes security deviations / incidents and credible derogatory information on contractor personnel as noted in the DoD personnel security system of record. Personnel who have incident reports posted in the DoD personnel security system of record will be denied the ability to work under the contract/task order until the issues have been resolved and the incident has been removed in the DoD personnel security system of record. The contractor shall make any changes necessary in the appointment(s), at no additional cost to the Government. If any incident involves or may involve the mishandling of classified information or a potential Negligent Discharge of Classified Information, the USTRANSCOM Joint Security Office Attn: Industrial Security Program Manager, will be notified within 24 hours during the normal work week and within 72 hours if the incident occurs over the weekend.

s) Accessing NATO Information: No contractor employee will access NATO information without first being indoctrinated on NATO and having that access recorded in the DoD personnel security system of record. Any NATO information accessed will be only on SIPRNet. Senders of NATO information will verify the receiving network is accredited and the receiving point is a Sub-Registry or authorized Control Point. No NATO information will be stored with US classified information. Access to NATO information will be based on need-to-know, appropriate access level, and training. NATO information will not be disseminated to unauthorized users. NATO information will not be printed unless authorized by a USTRANSCOM NATO – Sub-Registry person in TCCS-S. All printed NATO classified information must be strictly controlled and tracked in a NATO registry. Contact the USTRANSCOM Sub-Registry for additional control measures. In accordance with 32 CFR, part 117, NATO briefed personnel will be re-briefed on an annual basis. USTRANSCOM will indoctrinate all on-site contractor employees and document in the DoD personnel security system of record. Contractor personnel assigned to USTRANSCOM facilities will be NATO briefed and debriefed by USTRANSCOM, with appropriate annotations to the DoD personnel security system of record. Company FSOs may take responsibility for all NATO refresher briefings per 32 CFR, part 117 and record the date of the annual briefings in the contractor employee’s records.

t) Security Debriefing: Contractor personnel physically working at USTRANSCOM at

SAFB, IL, shall complete out-processing on the last day of the contract/task order or upon termination or reassignment from duties under the current contract/task order. The following close-out tasks will be completed before the contractor departs:

• Review of the contractor’s personnel security folder

• Review and debrief the contractor’s SF-312

• Debrief anyone with NATO Access

• Update and annotate the DoD personnel security system of record reflecting the current status of the contractor at USTRANSCOM

• Surrender CAC (with copy of the revocation notice from the COR or MPAS), for those off-site CACs will be physically mailed to TCCS-S for collection and turned into Scott AFB ID office for DMDC inventory and destruction.

• Surrender the USTRANSCOM Facility Access Badge to the Joint Security Desk

• Contractor personnel shall have surrendered all Government supplies, materials, and equipment to the COR.

u) Antiterrorism/Force Protection: Contractor employees will comply with antiterrorism Force Protection conditions (FPCONs) at the location they are performing work, whether it is CONUS or OCONUS.

v) NOTE TO THE PRIME CONTRACTOR FACILITY SECURITY OFFICER

(FSO): The prime contractor will forward the name, address, email address and telephone number of the Company FSO and backup to the USTRANSCOM Joint Security Office (TCCS-S) at: transcom.scott.tccs.mbx.industrial-security@mail.mil

w) USTRANSCOM Joint Security Office (Industrial Security) POCs:

USTRANSCOM

Attn: TCCS-S (Industrial Security Specialist) 508 Scott Drive Scott AFB, IL 62225 Commercial: 618-817-4078

x) USTRANSCOM Approval:

USTRANSCOM Joint Security Office

y) USTRANSCOM TCCS-S Tracking #: TCCS-S-XXX-YYYY

Governing guidance and directives:

DD Form 254, Contract Security Classification Specification, November 1, 2017 DoD 5200.08-R, “Physical Security Program,” May 27, 2009 DoD 5220-22-M, National Industrial Security Program Operating Manual (NISPOM),” May 18, 2016 DoD Directive 5230.25, “Withholding of Unclassified Technical Data from Public Disclosure,” August 18, 1995 DoD Instruction 2000.12, “DoD Antiterrorism (AT) Program,” May 8, 2017 DoD Instruction O-2000.16, “DoD Antiterrorism (AT) Standards Program Implementation, Volume 1: DoD AT Standards,” May 5, 2017 DoD Instruction O-2000.16, “DoD Antiterrorism (AT) Standards Program Implementation, Volume 2: DoD force Protection condition (FPCON) System, May 8, 2017 DoD Instruction 5200.01, “DoD Information Security Program and Protection of Sensitive Compartmented Information (SCI), April 21, 2016 DoD Instruction 5200.02, “Personnel Security Program,” September 9, 2014 DoD Instruction 8330.01, “Interoperability of Information Technology (IT), Including mailto:transcom.scott.tccs.mbx.industrial-security@mail.mil

National Security Systems (NSS),” December 18, 2017 DoD Instruction 8500.01, “Cybersecurity,” March 14, 2014 DoD Instruction 8510.01, “Risk Management Framework (RMF) for DoD Information Technology (IT),” July 28, 2017 DoD Instruction 8582.01, “Security of Unclassified DoD Information on Non-DoD Information Systems,” October 27, 2017 DoD Manual 1000.13, Volume 1, “DoD Identification (ID) Cards: ID Card Life-Cycle,”

January 23, 2014 DoD Manual 5200.01, Volume 1, “DoD Information Security Program: Overview, Classification, and Declassification”, February 24, 2012 DoD Manual 5200.01 Volume 2, “DoD Information Security Program: Marking of

Classified Information,” March 19, 2013 DoD Manual 5200.01 Volume 3, “DoD Information Security Program: Protection of

Classified Information,” March 19, 2013 DoD Manual 5200.01 Volume 4, “DoD Information Security Program: Controlled

Unclassified Information (CUI),” February 24, 2012 DoD Manual 5200.02, “Procedures for the DoD Personnel Security Program (PSP),”

April 3, 2017 DoD Manual 5220.22, Volume 3, “National Industrial Security Program: Procedures for

Government Activities Relating to Foreign Ownership, Control, or Influence (FOCI),” April 17, 2014

FD Form 258, Fingerprint Card USTRANSCOM Instruction 31-02, “Security Classification Guide,” 6 April 2018 USTRANSCOM Instruction 31-12, “Operations Security,” February 19, 2015 Scott Air Force Base: AF Instruction 31-101_AMC, January 4, 2014

Scott AFB Supplement is a restricted publication: Send only to .mil domains when forwarding - Not for public distribution

Federal Information Processing Standards (FIPS) and National Institute of Standards and Technology (NIST): https://csrc.nist.gov/publications

FIPS 199, “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

FIPS 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

NIST SP 800-18 Revision 1, “Guide for Developing Security Plans for Federal Information Systems” February 2006

NIST SP 800-30 Revision 1, “Guide for Conducting Risk Assessments,” September 2012 NIST SP 800-37 Revision 1, “Guide for Applying the Risk Management Framework to

Federal Information Systems: a Security life Cycle Approach,” June 5, 2014 NIST SP 800-53, Revision 4, “Security and Privacy Controls for Federal Information

Systems and Organizations,” January 22, 2015 NIST SP 800-53A Revision 4, “Assessing Security and Privacy Controls in Federal

Information Systems and Organizations: Building Effective Assessment Plans,” December 18, 2014

NIST SP 800-60 Volume 1, Revision 1, “Guide for Mapping Types of Information and Information Systems to Security Categories,” August 2008

NIST SP 800-61 Revision 2, “Computer Security Incident Handling Guide,” August 2012 https://csrc.nist.gov/publications

NIST Special Publication 800-171 Revision 1 “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, “ December 2016

Committee on National Security Systems (CNSS):

https://www.cnss.gov/CNSS/issuances/Instructions.cfm

CNSS Instruction 1253, “Security Categorization and Control Selection for National Security Systems,” March 27, 2014 https://www.cnss.gov/CNSS/issuances/Instructions.cfm