75D30124Q78121_SOW.pdf

Statement of Work Period of Performance: 09-30-2024 – 09/29/2025

Title: Environmental Sampling within the United States for Burkholderia pseudomallei and Leptospira spp. for the Division of High-Consequence Pathogens and Pathology (DHCPP), Bacterial Special Pathogens Branch (BSPB)

SECTION 1 – BACKGROUND

The Bacterial Special Pathogens Branch (BSPB) in the Division of High-Consequence Pathogens and Pathology (DHCPP) is responsible for the prevention and control of human illnesses due to a varied group of zoonotic and environmental bacterial pathogens, many of which are also classified as Tier 1 Select Agents, because of the possibility for these pathogens to be used maliciously against the United States. The mission of BSPB is to prevent illness, disability, or death caused by bacterial zoonotic diseases or unusual bacterial pathogens in the United States and around the world. BSPB accomplishes this mission by conducting surveillance, epidemic investigations, epidemiologic and laboratory research, training, and public education to develop, evaluate, and promote prevention and control strategies.

Melioidosis is caused by the Tier 1 bacterium Burkholderia pseudomallei which occurs in soil and water in areas endemic for the disease. Historically, melioidosis in the continental United States has been associated with travelers returning from international regions endemic for B.

pseudomallei, specifically Southeast Asia. Recently however, BSPB determined that B.

pseudomallei is locally endemic. Soil and water in the coastal area of Mississippi collected during investigations into two cases of melioidosis, from patients who lived within 20 miles of each other, were positive for B. pseudomallei.

Leptospirosis, caused by over 35 different species of pathogenic and intermediate Leptospira species, is one the most common zoonotic/environmental diseases in the world. Leptospira spp.

are shed in animal urine and are capable of surviving in soil and water. Globally it is estimated that there are up to 500,000 severe cases of leptospirosis annually, although this is likely a severe underestimate due to non-specific clinical presentations, poor availability of reliable tests, and lack of surveillance systems. Cases of leptospirosis increase after flooding events and tends to affect rural and economically disadvantaged areas disproportionately. Due to climate change and the associated extreme weather events, it is expected that cases of leptospirosis will continue to increase at a high rate.

Environmental sampling in the Gulf Coast bordering counties of Mississippi presents a unique opportunity to combine environmental surveillance efforts on two major pathogens within the continental United States. This information will allow the US Government to direct resources and conduct educational campaigns in the appropriate areas to help prevent illness due to B.

pseudomallei and Leptospira spp. BSPB is limited in personnel, so a contract has been identified as the best option to pursue this project.

SUBSECTION A – DEFINITIONS

BSPB-Bacterial Special Pathogens Branch DHCPP-Division of High Consequence Pathogens and Pathology NCEZID-National Center for Emerging and Zoonotic Infectious Diseases

SECTION 2 – PURPOSE

The purpose of the contract is to perform comprehensive environmental sampling of soil and water followed by laboratory testing of these specimens to identify the prevalence and genetic variations of members of the Burkholderia pseudomallei complex and Leptospira spp. endemic to the Gulf Coast of Mississippi.

SECTION 3 – SCOPE OF WORK

This contract will provide environmental sampling of soil and water from defined areas within Mississippi followed by laboratory testing of these specimens to identify the prevalence and genetic variations of members of the Burkholderia pseudomallei complex and Leptospira species endemic to the Gulf Coast of Mississippi.

Activities include:

1. Collect ≥275 soil samples and ≥25 water samples from coastal counties of Mississippi.

Sample collection sites will be selected in collaboration with CDC.

2. Georeference all sampling sites and collect any necessary data on environmental conditions associated with each collected specimen.

3. Culture the environmental samples in conditions optimal for the recovery of members of the B. pseudomallei complex and Leptospira spp. Identify recovered isolates by genetic analysis such as multilocus sequence typing (MLST) or other comparable methods. All laboratory procedures must follow proper biosafety requirements (Select Agent requirements and BSL3 laboratory requirements for working with suspected isolates of B. pseudomallei.)

4. Transfer to CDC all isolates and DNA from relevant isolates recovered during this study following standard shipment practices and with appropriate permits.

SECTION 4 – TASKS TO BE PERFORMED

Tasks include but are not limited to the following:

(1) Collection of environmental samples (soil and water) ;

a) At sites selected in consultation with and approval from CDC-BSPB.

Specimens will be collected from a minimum of 30 distinct sites during what is believed to be the high-risk seasons (i.e. Sept-Nov and May-July).

b) Collect ≥275 soil samples and ≥25water samples

c) Use safe, stable, and secure collection methods and storage to maintain viability of environmental samples and all subsequent biological material (i.e.

isolates, DNA)

d) Provide quarterly reports to CDC-BSPB on field collection planning and environmental sampling progress.

e) Ship samples from field to contractor’s laboratory with required permits

f) Receipt of samples at contractor’s laboratory for laboratory testing and store under appropriate conditions until testing begins.

(2) Laboratory testing of environmental samples to identify B. pseudomallei and other related members of the B. pseudomallei complex in a laboratory following Select Agent requirements and BSL3 laboratory guidelines for safe handling of cultures.

a) Conduct preliminary testing on samples to determine which are most likely to contain B. pseudomallei.

b) Culture samples to produce isolates for identification of B. pseudomallei and other related members of the B. pseudomallei complex

c) DNA extraction, sequencing, and identification of recovered isolates as members of the B. pseudomallei complex via analysis by a genetic based method such as multilocus sequence typing (MLST) or other comparable method.

d) Quarterly reports to CDC-BSPB on culture and isolation results

e) Transfer of all isolates and DNA of B. pseudomallei and other related members of the Burkholderia pseudomallei complex to CDC-BSPB with proper communication, permits, documentation, and permissions.

(3) Laboratory testing of environmental samples to identify Leptospira spp.

a) conduct preliminary testing on samples to determine which are most likely to contain Leptospira spp.

b) When possible, culture samples to produce isolates for identification of Leptospira spp.

c) When culture is not possible, conduct amplicon-based sequencing and/or selective enrichment to determine species.

d) when possible, conduct whole genome sequencing and perform identification based on MLST or other comparable method.

e) Quarterly reports to CDC-BSPB on culture and isolation results

f) Transfer isolates of all Leptospira spp. to CDC-BSPB with proper communication, permits, documentation, and permissions.

SECTION 5 – GOVERNMENT FURNISHED MATERIALS

The Government will not provide any government furnished materials to the Contractor.

SECTION 6 – PERIOD OF PERFORMANCE

The period of performance for this contract is from 09/30/2024 through 09/29/2025

SECTION 7 – DELIVERABLES/REPORTING SCHEDULE

Items Descriptions Quantity or No.

Delivery Date Deliver

To Initial Progress Report with Invoice

Contractor provides a report itemizing progress made in planning for sampling and any identified problems. Report will include SOP for sampling and processing of samples. Vendor will obtain any permits as needed.

1 2 months after the start date

PM and

COR

Proposed Sampling Sites

Contractor will provide a description of proposed sampling sites based on input from CDC

1 2 months after the start date

PM and

COR

Map depicting visual locations of sites sampled for members of the B.

pseudomallei complex;

positive and negative locations identified.

Contractor will provide a detailed colored map with georeferenced localities of completed sampling areas with positive and negative samples labeled.

Invoice will be include

5 Quarterly PM and

COR

Midyear Progress Report

Contractor provides a report summarizing sampling trips and identifying the number of samples collected.

1 9 months after the start date

PM and

COR

Laboratory findings report

Contractor provides a report identifying initial laboratory results, including DNA sequence analysis results such as from MLST of members of the B. pseudomallei complex if available and any identified problems.

5 Quarterly PM and

COR

DNA and isolates

Contractor will provide list of biological materials to ship and will be responsible for shipping DNA and isolates from members of the B. pseudomallei complex to CDC if DNA and isolates are available.

3 Semiannually PM and

COR

Final Report Report summarizing field sample collections, laboratory findings, pathogens of interest detected, and

1 At the end of the period of performance

PM and

COR

any identified problems with resolutions.

SECTION 8 – REFERENCE MATERIAL

Cossaboom, C. M., Marinova-Petkova, A., Strysko, J., Rodriguez, G., Maness, T., Ocampo, J., Gee, J. E., Elrod, M. G., Gulvik, C. A., Liu, L., Bower, W. A., Hoffmaster, A. R., Blaney, D. D., Salzer, J. S., Yoder, J. S., Mattioli, M. C., Sidwa, T. J., Ringsdorf, L., Morrow, G., Ledezma, E., … Kieffer, A. (2020). Melioidosis in a Resident of Texas with No Recent Travel History, United States. Emerging infectious diseases, 26(6), 1295–1299. https://doi.org/10.3201/eid2606.190975 Gee JE, Gulvik CA, Elrod MG, Batra D, Rowe LA, Sheth M, Hoffmaster AR (2017) Phylogeography of Burkholderia pseudomallei Isolates, Western Hemisphere. Emerg Infect Dis.

2017 Jul;23(7):1133-1138

CDC Health Alert Netowrk. Melioidosis Locally Endemic in Areas of the Mississippi Gulf Coast after Burkholderia pseudomallei Isolated in Soil and Water and Linked to Two Cases – Mississippi, 2020 and 2022. CDCHAN-00470.

Limmathurotsakul D1, Dance DA, Wuthiekanun V, Kaestli M, Mayo M, Warner J, Wagner DM, Tuanyok A, Wertheim H, Yoke Cheng T, Mukhopadhyay C, Puthucheary S, Day NP, Steinmetz I, Currie BJ, Peacock SJ (2013) Systematic review and consensus guidelines for environmental sampling of Burkholderia pseudomallei PLoS Negl Trop Dis. 20(3):e2105. doi:

10.1371/journal.pntd.0002105.

Sanchez-Villamil JI, Torres AG.(2018) Melioidosis in Mexico, Central America, and the Caribbean.Trop Med Infect Dis. Mar;3(1). pii: 24.

SECTION 9 – POINT OF CONTACT INFORMATION

The Point of Contact (POC) for this procurement is:

TBD

SECTION 10 – PAYMENT TERMS

Reports must be submitted as outlined in the Deliverables. Invoices will be submitted to the government with the reports for payment in arrears. The government will withhold payment on new Invoices until reports are received, per the schedule.

SECTION 11 – Information Security Compliance Standard-1: Procurements Requiring Information Security and/or Physical Access

Security

1. Baseline Security Requirements https://doi.org/10.3201/eid2606.190975 https://emergency.cdc.gov/han/2022/han00470.asp https://emergency.cdc.gov/han/2022/han00470.asp https://emergency.cdc.gov/han/2022/han00470.asp

a. Applicability. The requirements herein apply whether the entire contract or modification (hereafter "contract"), or portion thereof, includes either or all of the followings. No contractor will be permitted to access or operate CDC infrastructure or systems overseas unless prior approval is received from CDC CISO.

i. Access (Physical or Logical) to Government Information: A Contractor (and/or any subcontractor) will have or will be given the ability to have, routine physical (entry) or logical (electronic) access to government information.

ii. Operate a Federal System Containing Information: A Contractor (and/or any subcontractor) will operate a federal system and information technology containing data that supports the CDC mission. In addition to the Federal Acquisition Regulation (FAR) Subpart 2.1 definition of "information technology" (IT), the term as used in this section includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), and related resources.

b. Safeguarding Information and Information Systems. All government information and information systems must be protected in accordance with HHS/CDC policies and level of risk. At a minimum, the Contractor (and/or any subcontractor) must:

i. Protect the:

Confidentiality, which means preserving authorized restrictions on access and disclosure, based on the security terms found in this contract, including means for protecting personal privacy and proprietary information;

Integrity, which means guarding against improper information modification or destruction, and ensuring information non-repudiation and authenticity; and

Availability, which means ensuring timely and reliable access to and use of information.

ii. Categorize all information owned and/or collected/managed on behalf of CDC and information systems that store, process, and/or transmit HHS information in accordance with FIPS 199 and National Institute of Standards and Technology (NIST) Special Publication (SP) 800-60, Volume II: Appendices to Guide for Mapping Types of Information and Information Systems to Security Categories.

Based on information provided by the ISSO, CISO, CDC CPO, or other representative, the impact level for each Security Objective (Confidentiality, Integrity, and Availability) and the Overall Impact Level, which is the highest watermark of the three factors of the information or information system are the following:

Table 1: Information Types and Risk Ratings http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf

Information Type Title Confidentiality Impact Level

Integrity Impact Level

Availability Impact Level

C.2.1.3 Program Monitoring Low Low Low C.3.4.4 Services Acquisition Low Low Low

Table 2: Information/System Categorization and Overall Risk

Information Type Title Confidentiality (Low, Moderate, High)

Integrity (Low, Moderate, High)

Availability (Low, Moderate, High)

Security Objectives Impact Level: (NIST SP 800-60) Moderate Moderate Moderate Security Objectives Impact Level: (If System / Information Owner need to downgraded / upgraded risk)

Overall Impact Level: (Low, Moderate, High)

Moderate Moderate Moderate

iii. Based on the agreed-upon level of impact, implement the necessary safeguards to protect all information systems and information collected and/or managed on behalf of CDC regardless of location or purpose.

iv. Report any discovered or unanticipated threats or hazards by either the agency or contractor, or if existing safeguards have ceased to function immediately after discovery, within one (1) hour or less, to the government representative(s).

v. Adopt and implement all applicable policies, procedures, controls, and standards required by the CDC Information Security Program to ensure the confidentiality, integrity, and availability of government information and government information systems for which the Contractor is responsible under this contract or to which the Contractor may otherwise have access under this contract. Obtain all applicable security and privacy policies by contacting the CO/COR or CDC security and/or privacy officials.

c. Privacy Act. Comply with the Privacy Act requirements (when applicable), and tailor FAR and HHSAR clauses as needed.

d. Privacy Compliance. Comply with the E-Government Act of 2002, NIST SP 800- 53, and applicable CDC privacy policies, and complete all the requirements below:

i. Per the Office of Management and Budget (OMB) Circular A-130, Personally Identifiable Information (PII), is "information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual." Examples of PII include, but are not limited to the following: Social Security number, date and place of birth, mother's maiden name, biometric records, etc.

ii. To ensure that the public's personal information is protected in a manner commensurate with the privacy risks, CDC uses a privacy analysis process to assess the risks associated with CDC's collection and maintenance of PII and to ensure information is handled in accordance with applicable legal, regulatory, and policy requirements. PTAs analyze how information is handled in IT systems and electronic information collections and determines if the IT system or electronic information collection collects, disseminates, maintains, or disposes of PII. PIAs are used to assess the privacy risks of IT systems and electronic information collections that collect, disseminate, maintain, or dispose of PII about members of the public. PIAs also provide transparency into how CDC collects, disseminates, maintains, or disposes of the public's PII.

iii. The Contractor must support the agency with conducting a Privacy Threshold Analysis (PTA) for the information system and/or information handled under this contract to determine whether or not PII is collected, disseminated, maintained, or disposed as part of the contract. The PTA will determine if a full Privacy Impact Assessment (PIA) needs to be completed.

If the results of the PTA show that a full PIA is needed, the Contractor must support the agency with completing a PIA for the system or information within 60 days after completion of the PTA and in accordance with CDC policy and OMB M-03-22, Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002.

The Contractor must support the agency in reviewing the PIA at least every three years throughout the system development lifecycle (SDLC)/information lifecycle, or when determined by the agency that a review is required based on a major change to the system, or when new types of PII are collected that introduces new or increased privacy risks, whichever comes first.

e. Controlled Unclassified Information (CUI). Executive Order 13556 defines CUI as "information that laws, regulations, or Government-wide policies require to have safeguarding or dissemination controls, excluding classified information." The Contractor (and/or any subcontractor) must comply with Executive Order 13556, Controlled Unclassified Information, (implemented at 3 CFR, part 2002) when handling CUI. 32 C.F.R. 2002.4(aa) As implemented the term "handling" refers to "…any use of CUI, including but not limited to marking, safeguarding, transporting, disseminating, re-using, and disposing of the information." 81 Fed. Reg. 63323. The requirements below apply only to nonfederal systems that process, store, or transmit CUI, or that provide security protection for such components. All sensitive information that has been identified as CUI by a regulation or statute, handled by this solicitation/contract, must be:

i. Marked appropriately;

ii. Disclosed to authorized personnel on a Need-To-Know basis;

iii. Protected in accordance with NIST SP 800-53, Security and Privacy Controls for Information Systems and Organizations applicable baseline if handled by a Contractor system operated on behalf of the agency, or NIST SP 800- 171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations if handled by internal Contractor system; and

iv. Returned to HHS/CDC control, destroyed when no longer needed, or held until otherwise directed. Information and/or data must be disposed of in accordance with NIST SP 800-88, Guidelines for Media Sanitization.

f. Protection of Sensitive Information. For security purposes, information is or may be sensitive because it requires security to protect its confidentiality, integrity, and/or availability. The Contractor (and/or any subcontractor) must protect all government information that is or may be sensitive by securing it with a solution that is validated with current FIPS 140 validation certificate from the NIST CMVP.

g. Confidentiality and Nondisclosure of Information. Any information provided to the contractor (and/or any subcontractor) by CDC or collected by the contractor on behalf of CDC must be used only for the purpose of carrying out the provisions of this contract and must not be disclosed or made known in any manner to any persons except as may be necessary in the performance of the contract. The Contractor assumes responsibility for protection of the confidentiality of Government records and must ensure that all work performed by its employees and subcontractors must be under the supervision of the Contractor. Each Contractor employee or any of its subcontractors to whom any CDC records may be made available or disclosed must be notified in writing by the Contractor that information disclosed to such employee or subcontractor can be used only for that purpose and to the extent authorized herein.

The confidentiality, integrity, and availability of such information must be protected in accordance with HHS/CDC policies. Unauthorized disclosure of information will be subject to the HHS/CDC sanction policies and/or governed by the following laws and regulations:

i. 18 U.S.C. 641 (Criminal Code: Public Money, Property or Records);

ii. 18 U.S.C. 1905 (Criminal Code: Disclosure of Confidential Information);

and

iii. 44 U.S.C. Chapter 35, Subchapter I (Paperwork Reduction Act).

h. Internet Protocol Version 6 (IPv6). All procurements using Internet Protocol must comply with OMB Memorandum M-05-22, Transition Planning for Internet Protocol Version 6 (IPv6).

i. Information and Communications Technology (ICT). ICT products and services from prohibited entities/sources must not be used/acquired in compliance with Public Law 115-232, Section 889 Parts A and B, FAR 4.21, FAR 52.204.23, FAR 52.204.24, and FAR 52.204.25. The contractor (and/or any subcontractor) must notify the government if they identify prohibited ICT products and/or services are used during the contract performance.

j. Government Websites. All new and existing public-facing government websites must be securely configured with Hypertext Transfer Protocol Secure (HTTPS) using the most recent version of Transport Layer Security (TLS). In addition, HTTPS must enable HTTP Strict Transport Security (HSTS) to instruct compliant browsers to always assume HTTPS to reduce the number of insecure redirects and protect against attacks that attempt to downgrade connections to plain HTTP. For internal-facing websites, HTTPS is not required, but it is highly recommended. Consult HHS/CDC Policy for Internet and Email Security for additional information.

k. Contract Documentation. The Contractor must use provided templates, policies, forms and other agency documents specify which documents/forms will be provided to contractor] to comply with contract deliverables as appropriate.

l. Standard for Encryption. The Contractor (and/or any subcontractor) must:

i. Comply with the HHS Standard for Encryption of Computing Devices and Information to prevent unauthorized access to government information.

ii. Encrypt all sensitive federal data and information (i.e., PII, protected health information [PHI], proprietary information, etc.) in transit (i.e., email, network connections, etc.) and at rest (i.e., servers, storage devices, mobile devices, backup media, etc.) with encryption solution that is validated with current FIPS 140 validation certificate from the NIST CMVP.

iii. Secure all devices (i.e.: desktops, laptops, mobile devices, etc.) that store and process government information and ensure devices meet and CDC Component-specific encryption standard requirements. Maintain a complete and current inventory of all laptop computers, desktop computers, and other mobile devices and portable media that store or process sensitive government information (including PII).

iv. Verify that the encryption solutions in use have been validated under the Cryptographic Module Validation Program to confirm compliance with current FIPS 140 validation certificate from the NIST CMVP. The Contractor must provide a written copy of the validation documentation to the COR.

v. Use the Key Management system on the CDC personal identification verification (PIV) card or establish and use a key recovery mechanism to ensure the ability for authorized personnel to encrypt/decrypt information and recover encryption keys http://csrc.nist.gov/publications/. Encryption keys must be provided to CSPO.

m. Contractor Non-Disclosure Agreement (NDA). Each Contractor (and/or any subcontractor) employee having access to non-public government information under this contract must complete the CDC non-disclosure agreement, as applicable.

http://csrc.nist.gov/publications/

Contractors (and/or subcontractors) must submit a copy of each signed and witnessed NDA to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition.

2. Training Requirements

a. Mandatory Training for All Contractor Staff. All Contractor (and/or any subcontractor) employees assigned to work on this contract must complete the applicable CDC Contractor Information Security Awareness, Privacy, and Records Management training (provided upon contract award) before performing any work under this contract. Thereafter, the employees must complete CDC Security Awareness, Privacy, and Records Management training at least annually, during the life of this contract. All provided training must be compliant with CDC training policies.

b. Role-based Training. All Contractor (and/or any subcontractor) employees with significant security responsibilities (as determined by the program manager) must complete role-based training annually commensurate with their role and responsibilities in accordance with HHS/CDC policy and the CDC Role-Based Training (RBT) of Personnel with Significant Security Responsibilities.

c. Training Records. The Contractor (and/or any subcontractor) must maintain training records for all its employees working under this contract in accordance with CDC policy. A copy of the training records must be provided to the CO and/or COR within 30 days after contract award and annually thereafter or upon request.

3. Rules of Behavior

a. The Contractor (and/or any subcontractor) must ensure that all employees performing on the contract comply with CDC Implementation of the HHS Rules of Behavior for Use of HHS Information Technology Resources.

b. All Contractor employees performing on the contract must read and adhere to the Rules of Behavior before accessing agency data or other information, systems, and/or networks that store/process government information, initially at the beginning of the contract and at least annually thereafter, which may be done as part of annual CDC Information Security Awareness Training. If the training is provided by the contractor, the signed ROB must be provided as a separate deliverable to the CO and/or COR per defined timelines above.

4. Incident Response

a. The Contractor (and/or any subcontractor) must respond to all alerts/Indicators of Compromise (IOCs) provided by CDC Computer Security Incident Response Center (CSIRC) IRT teams within 24 hours, whether the response is positive or negative. In accordance with FISMA and OMB M-17-12, Preparing for and Responding to a

Breach of Personally Identifiable Information (PII)1, an incident is "an occurrence that (1) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (2) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies" and a privacy breach is "the loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where (1) a person other than an authorized user accesses or potentially accesses personally identifiable information or (2) an authorized user accesses or potentially accesses personally identifiable information for an other than authorized purpose." For additional information on the CDC breach response process, please see the CDC Standard for Responding to Breaches of Personally Identifiable Information (PII).2"

b. Contracts with entities that collect, maintain, use, or operate Federal information or information systems on behalf of CDC must include in the following requirements:

i. The contractor shall cooperate with and exchange information with CDC officials, as deemed necessary by the CDC Breach Response Team, to report and manage of a suspected or confirmed breach.

ii. All contractors and subcontractors shall properly encrypt PII in accordance with OMB Circular A-130 and other applicable policies, including CDC-specific policies, and comply with HHS-specific policies for protecting PII. To this end, all contractors and subcontractors shall protect all sensitive information, including any PII created, stored, or transmitted in the performance of this contract, with encryption solution that is validated with the current FIPS 140 validation certificate from the NIST CMVP.

iii. All contractors and subcontractors shall participate in regular training on how to identify and report a breach

iv. NOT notify affected individuals unless so instructed by the Contracting Officer or designated representative. If instructed by the Contracting Officer or representative, the Contractor must send [CDC Component] approved notifications to affected individuals [insert CDC Component Specific timeline, process, and format].

v. Report all suspected and confirmed information security and privacy incidents and breaches to the CSPO Incident Response Team (IRT) [CDC Component inserted contact information should be cited here], COR, CO, CDC CPO (or his or her designee), and other stakeholders, including breaches involving PII, in any medium or form, including paper, oral, or electronic, as soon as possible and without unreasonable delay, no later than one (1) hour, and consistent with the applicable CDC Component and CDC policy and procedures, NIST standards and

1 Memorandum is available at: https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2017/m-17-12_0.pdf 2 Standard is available at: https://cdc.sharepoint.com/teams/OCIO-CSPO- PUBDOCS/Standards/CSPO%20Responding%20to%20Breaches%20of%20Personally%20Identifiable%20Informati on.pdf guidelines, as well as US-CERT notification guidelines. The types of information required in an incident report must include at a minimum: company and point of contact information, impact classifications/threat vector, and the type of information compromised. In addition, the Contractor must:

Cooperate and exchange any information, as determined by the Agency, necessary to effectively manage or mitigate a suspected or confirmed breach;

Not include any sensitive information in the subject or body of any reporting e-mail; and

Encrypt sensitive information in attachments to email, media, etc.

vi. Comply with OMB M-17-12, Preparing for and Responding to a Breach of

Personally Identifiable Information, and CDC Component and CSPO privacy breach response policies when handling PII breaches.

vii. Provide full access and cooperate on all activities as determined by the Government to ensure an effective incident response, including providing all requested images, log files, and event information to facilitate rapid resolution of sensitive information incidents. This may involve disconnecting the system processing, storing, or transmitting the sensitive information from the Internet or other networks or applying additional security controls. This may also involve physical access to contractor facilities during a breach/incident investigation [CDC Component insert timeline if required].

viii. All contractors and subcontractors shall be able to determine what Federal information was or could have been accessed and by whom, construct a timeline of user activity, determine methods and techniques used to access Federal information, and identify the initial attack vector.

ix. Cloud service providers shall use guidance provided in the FedRAMP Incident Communications Procedures when deciding when to report directly to US-CERT first or notify CDC first.

x. Acknowledge that CDC will not interpret report of a breach, by itself, as conclusive evidence that the contractor or its subcontractor failed to provide adequate safeguards for PII.

5. Position Sensitivity Designations

All Contractor (and/or any subcontractor) employees must obtain a background investigation commensurate with their position sensitivity designation that complies with Parts 1400 and 731 of Title 5, Code of Federal Regulations (CFR). The following position sensitivity designation levels apply to this solicitation/contract:

Investigation Position Requirement NAC National Agency Check Tier 1 Low-Risk Non-Sensitive, including HSPD-12 Credentialing

Tier 2 Moderate-Risk Public Trust (MRPT) Tier 3 Non-Critical Sensitive, National Security, including Secret and “L” access eligibility Tier 4 High-Risk Public Trust Tier 5 Critical Sensitive and Special Sensitive, National Security, including Top Secret, SCI, and “Q” access eligibility

Not Applicable No Requirement

6. Homeland Security Presidential Directive (HSPD)-12

The Contractor (and/or any subcontractor) and its employees must comply with Homeland Security Presidential Directive (HSPD)-12, Policy for a Common Identification Standard for Federal Employees and Contractors; OMB M-05-24; OMB M-19-17; FIPS 201, Personal Identity Verification (PIV) of Federal Employees and Contractors; CDC HSPD-12 policy; and Executive Order 13467, Part 1 §1.2.

7. Roster

The Contractor (and/or any subcontractor) must submit a roster by name, position, e-mail address, phone number and responsibility, of all staff working under this acquisition where the Contractor will develop, have the ability to access, or host and/or maintain a government information system(s). The roster must be submitted to the COR and/or CO 30 days prior to the effective date of this contract. Any revisions to the roster as a result of staffing changes must be submitted immediately upon the 30 days change. The COR will notify the Contractor of the appropriate level of investigation required for each staff member.

If the employee is filling a new position, the Contractor must provide a position description and the Government will determine the appropriate suitability level.

8. Contract Initiation and Expiration

a. General Security Requirements. The Contractor (and/or any subcontractor) must comply with information security and privacy requirements, Enterprise Performance Life Cycle (EPLC) processes, CDC Enterprise Architecture requirements to ensure information is appropriately protected from initiation to expiration of the contract. All information systems development or enhancement tasks supported by the contractor must follow the CDC EPLC framework and methodology and in accordance with the CDC Office of Financial Resources (OFR) Contract Closeout Guide and HHS Closeout Guide: Contracts and Orders.

b. System Documentation. Contractors (and/or any subcontractors) must follow and adhere to CDC System Development Life Cycle requirements, at a minimum, for system development and provide system documentation at designated intervals (specifically, at the expiration of the contract) within the EPLC that require artifact review and approval.

c. Sanitization of Government Files and Information. As part of contract closeout and at expiration of the contract, the Contractor (and/or any subcontractor) must provide all required documentation to the CO and/or COR to certify that, at the government's direction, all electronic and paper records are appropriately disposed of and all devices and media are sanitized in accordance with NIST SP 800-88, Guidelines for Media Sanitization.

d. Notification. The Contractor (and/or any subcontractor) must notify the CO and/or COR and system ISSO within 15 days before an employee stops working under this contract.

e. Contractor Responsibilities upon Physical Completion of the Contract. The contractor (and/or any subcontractors) must return all government information and IT resources (i.e., government information in non-government-owned systems, media, and backup systems) acquired during the term of this contract to the CO and/or COR.

Additionally, the Contractor must provide a certification that all government information has been properly sanitized and purged from Contractor-owned systems, including backup systems and media used during contract performance, in accordance with CDC policies.

f. The Contractor (and/or any subcontractor) must perform and document the actions identified in the CDC Out-Processing Checklist (http://intranet.cdc.gov/od/hcrmo/pdfs/hr/Out_Processing_Checklist.pdf) when an employee terminates work under this contract within 15 days of the employee's exit from the contract. All documentation must be available to the CO and/or COR upon request.

9. Records Management and Retention

a. The Contractor (and/or any subcontractor) must maintain all information in accordance with Executive Order 13556 -- Controlled Unclassified Information, National Archives and Records Administration (NARA) records retention policies and schedules and CDC Policy for Records Management and HHS policies and must not dispose of any records unless authorized by CDC Program.

b. If a contractor (and/or any subcontractor) accidentally disposes of or destroys a record without proper authorization, he/she must document and report the incident in accordance with CDC policies.

10. High Value Asset (HVA):

If a system is identified as HVA, the contractor must comply with the HHS Policy for the High Value Asset (HVA) Program and the Department of Homeland Security (DHS) HVA Control Overlay[22] in addition to the above requirements.

11. Deliverables

Deliverable Title/Deliverable Type

Description Due Date

Roster Roster Within 30 days of the effective date of this contract

Contractor Employee Non- Disclosure Agreement

(NDA)

Contractor Employee Non- Disclosure Agreement (NDA)

Prior to performing any work on behalf of HHS http://intranet.cdc.gov/od/hcrmo/pdfs/hr/Out_Processing_Checklist.pdf https://login.max.gov/cas/login?service=https%3A%2F%2Fcommunity.max.gov%2Flogin.action%3Fos_destination%3D%252Fpages%252Fviewpage.action%253FspaceKey%253DHHS%2526title%253DHHS%252BCyberSecurity%252BPolicy%252BCollaboration%252BPage

Privacy Threshold Analysis (PTA)/ Privacy Impact Assessment (PIA)

Assist in the completion of a PTA/PIA form

Within 60-90 days after contract award

Training Records Copy of training records for all mandatory training

In conjunction with contract award and annually thereafter or upon request

Rules of Behavior Signed ROB for all employees

Initiation of contract and at least annually thereafter

Incident Response Incident Report (as incidents or breaches occur)

As soon as possible and without reasonable delay and no later than 1 hour of discovery

Personnel Security Responsibilities

List of Personnel with defined roles and responsibilities

Within 7 days; that is before an employee begins working on this contract.

Personnel Security Responsibilities

Off-boarding documentation, equipment and badge when leaving contract

Within 5 days or less after the Government’s final acceptance of the work under this contract, or in the event of a termination of the contract.

Background Investigation

Onboarding documentation when beginning contract.

Prior to performing any work on behalf of HHS

Certification of Sanitization of Government and Government Activity- Related Files, Information, and Devices.

Form or deliverables required by CDC

At contract expiration.

Contract Initiation and Expiration

If the procurement involves a system or cloud service, additional documentation will be required, such as Disposition/Decommission Plan

At contract expiration.

Standard-2 Requirements for Procurements Involving Privacy

Appropriate security controls and Rules of Behavior should be incorporated to protect the confidentiality of information, proprietary, sensitive, and Personally Identifiable Information (PII) the Contractor may come in contact with during the performance of this contract.

11. Deliverables