NGDS2 - Appendix 6.2, Cyber Security Requirements (22 June 2021).docx
DOCX document 24 KB Posted
- Attached to
- Next Generation Delivery Services (NGDS 2) - HTC711-22-R-C003; Request For Information (RFI)
- Solicitation number
- HTC711-22-R-C003
About this file
This document outlines cybersecurity incident handling requirements for the Next Generation Delivery Services 2 (NGDS 2) federal contract opportunity. Key details include mandatory reporting of cybersecurity incidents affecting DoD information systems to the USTRANSCOM Cyber Operations Center within 24 hours of discovery, with an initial notification providing high-level details and a follow-on report within 72 hours including additional mandatory data elements. Contractors must preserve evidence and data related to incidents and allow potential follow-on actions by government entities to further characterize and evaluate suspect activity. The NGDS 2 contract provides small package air and ground shipping for the federal government up to 150 pounds domestically and 300 pounds internationally, and is considered operationally critical support involving DoD information systems.
View the file
Other files
Show all 20
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
HTC711-22-R-C003
PWS Appendix 6.2 1 October 2022
Appendix 6.2 Cybersecurity Incident Handling
1. CYBERSECURITY for NGDS Carriers
1.1. Operationally Critical Support. The services designated under this contract are “operationally critical support” as defined in DFARS 252.204-7012.
1.2. Cybersecurity Incident Reporting
1.2.1. In addition to the DFARS 252.204-7012 reporting requirements for unclassified systems and DoD Manual (DoDM) 5220.22, National Industrial Security Program Operating Manual (NISPOM) for classified systems, reportable cyber-incidents include, but are not limited to, the following:
1.2.1.1. Unauthorized data exfiltration, manipulation or disclosure of any DoD information resident on or transiting the contractor's unclassified or classified information systems or networks.
1.2.1.2. Unauthorized access to the contractor’s unclassified or classified information system(s) or networks(s) on which DoD information is resident or transiting.
1.2.1.3. Cyber-incidents as listed in the MITRE ATT&CK Framework available at https://attack.mitre.org/, incorporated herein by reference, which affect network or information systems where DoD information is resident or transiting.
1.2.1.4. Notifications by a federal, state, or local law enforcement agency or cyber-center (i.e., National Cyber Investigative Joint Task Force (NCIJTF), National Cybersecurity & Communications Integration Center (NCCIC)) of being a victim of a successful or unsuccessful cyber-event, anomaly, incident, insider threat, breach, intrusion, or exfiltration.
1.2.2. If the cyber-incident affects a classified system, vulnerabilities associated with the incident will be classified per the current version of USTRANSCOM Instruction 31-02, Security Classification Guide.
1.3. Cybersecurity Incident Reporting Timelines. In addition to providing the notification required by DFARS 252.204-7012, the contractor is required to notify USTRANSCOM as soon as practicable, but no later than 24 hours after discovering a reportable cyber-incident. The reporting timeline begins when the incident is discovered or reported to the company, its employees, contractors, or cybersecurity firm responsible for providing cybersecurity and response for the company. The contractor shall contact the USTRANSCOM Cyber Operations Center (CyOC) via phone at 618-220-4222. If the contractor does not immediately reach the CyOC via phone, the contractor shall send an email notification to transcom.scott.tcj6.mbx.cyoc@mail.mil.
1.4. Mandatory Reporting Data
1.4.1. The contractor shall work with the USTRANSCOM CyOC through resolution of the incident. Within 24 hours of becoming aware of a reportable cyber-incident, the contractor shall provide an initial notification of the incident, even if some details are not yet available, which includes, but is not limited to, the following information:
(a) Company Name
(b) Who will be the POC with contact information
(c) Contracting Officer POC (name, telephone, email)
(d) Overall Assessment –Description of incident, data at risk, mitigations applied
(e) Indicators of compromise
(f) Vector of attack (if known)
(g) Estimated time of attack (if known)
1.4.2. The contractor shall provide a follow-on cyber-incident report to the USTRANSCOM CyOC within 72 hours of becoming aware of a reportable cyber-incident, which includes, but is not limited to, the following information:
(a) Contractor unique Commercial and Government Entity (CAGE) code
(b) Contract numbers affected
(c) Facility CAGE code where the incident occurred if different than the prime Contractor location
(d) POC if different than the POC recorded in the System for Award Management (name, address, position, telephone, email)
(e) Contracting Officer POC (name, telephone, email)
(f) Contract clearance level
(g) DoD programs, platforms, systems, or information involved
(h) Location(s) of compromise
(i) Date incident discovered
(j) Type of compromise (e.g., unauthorized access, inadvertent release, other)
(k) Description of technical information compromised
(l) Any additional information relevant to the information compromise
1.5. Incident Reporting Coordination
1.5.1. In the event of a cyber-incident, USTRANSCOM may conduct an on-site review of network or information systems where DoD information is resident on or transiting to assist the contractor in evaluating the extent of the incident and to share information in an effort to minimize the impact to both parties. Date and time of on-site visits will be mutually agreed upon by USTRANSCOM and the contractor in advance.
1.5.2. The contractor agrees to allow follow-on actions by the Government (e.g., USTRANSCOM, Federal Bureau of Investigation, Department of Homeland Security, DC3, etc.) to further characterize and evaluate the suspect activity. The contractor acknowledges that damage assessments might be necessary to ascertain an incident methodology and identify systems compromised as a result of the incident. Once an incident is identified, the contractor agrees to take all reasonable and appropriate steps to preserve any and all evidence, information, data, logs, electronic files and similar type information (reference NIST Special Publication 800-61: Computer Security Incident Handling Guide, (current version)) related to the incident for subsequent forensic analysis so that an accurate and complete damage assessment can be accomplished by the Government.
1.5.3. The contractor is not required to maintain an organic forensic capability, but must ensure data is preserved (e.g., remove an affected system, while still powered on, from the network) and all actions documented until forensic analysis can be performed by the Government or, if the Government is unable to conduct the forensic analysis, a mutually agreed upon third party (e.g., Federally Funded Research and Development Center (FFRDC), commercial security contractor, etc.). Any follow-on actions shall be coordinated with the contractor via the Contracting Officer.
1.5.4. The contractor agrees to indemnify and hold the government harmless for following any recommendations to remedy or mitigate the cyber-incident following the actions under 1.5.1. and 1.5.2.
1.6. Confidentiality and Non-Attribution Statement. The Government may use and disclose reported information as authorized by law and will only provide attribution information on a need-to-know basis to authorized persons for cybersecurity and related purposes (e.g., in support of forensic analysis, incident response, compromise or damage assessments, law enforcement, counter intelligence, threat reporting, and trend analysis). The Government may share threat information with other USTRANSCOM industry partners without attributing or identifying the affected contractor.
File details come from the government source that posted it. Updated .