A19 75D30126Q78912 SOLICITATION.doc

PAGE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

1. REQUISITION NUMBER

PAGE 1 OF

2. CONTRACT NO.

3. AWARD/EFFECTIVE

DATE

04/08/2026

4. ORDER NUMBER

5. SOLICITATION NUMBER

75D301-26-Q-78912

6. SOLICITATION

ISSUE DATE

04/01/2026

Peter Loree

b. TELEPHONE NUMBER (No collect calls)

(770) 488-5490

8. OFFER DUE DATE/

LOCAL TIME

04/07/2026 08

12. DISCOUNT TERMS

FORMTEXT

OFR - Office of Acquisition Services

Chamblee Campus Building 108

4770 Buford Highway

Atlanta, GA 30341-

X UNRESTRICTED

SIC: 334111

SIZE STANDARD:

X SEE SCHEDULE

UNDER DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

CDC (NCEZID)

1600 CLIFTON ROAD

BLDG 23, 4TH FLOOR

ATLANTA, GA 30329-4018

STERLING COMPUTERS CORPORATION

303 CENTENNIAL DR

NORTH SIOUX CITY, SD 57049-

Centers for Disease Control and Prevention (FMO)

PO Box 15580 404-718-8100

Atlanta, GA 30333-0080

TELEPHONE NO.

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

“See Continuation Page”

(Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA

939014P 257R 2026 75-26-0949 5614D11101

26. TOTAL AWARD AMOUNT (For Govt. Use Only)

$134,732.00

28.

CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

29.

AWARD OF CONTRACT: REFERENCE

DATED

30b. NAME AND TITLE OF SIGNER (Type or print)

30c. DATE SIGNED

31b. NAME OF CONTRACTING OFFICER (Type or print)

Howard D Bish 31c. DATE SIGNED

FORMTEXT

RECEIVED

32b. SIGNATURE OF AUTHORIZED GOV’T REPRESENTATIVE 32c. DATE

41a. I CERTIFY THIS AMOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

38. S/R ACCOUNT NUMBER

39. S/R VOUCHER NUMBER

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC’D 42d. TOTAL CONTAINERS

40. PAID BY

AUTHORIZED FOR LOCAL REPRODUCTION

SEE REVERSE FOR OMB CONTROL NUMBER AND PAPERWORK BURDEN STATEMENT STANDARD FORM 1449 (10-95)

TABLE OF CONTENTS

SECTION B - CONTINUATION CONTINUATION OF SF1449tc \l2 "CONTINUATION OF SF 1449

Base, Year 1 Items:

R540 ND+PS+KK

R640 Pioneer ND+PS+KK

R640 Pioneer OEMXL (Northlake) ND+PS+KK

R740 NC+PS+KK

R750 ND+PS+KK

R440 ND+PSS+KK

R730 ND+PSS+KK

Firm Fixed Price

Severable Service Item

Period of Performance

4/08/2026 - 4/07/2027 1 Each

Option 1 Year 2 Items:

R540 ND+PS+KK

R640 Pioneer ND+PS+KK

R640 Pioneer OEMXL (Northlake) ND+PS+KK

R740 NC+PS+KK

R750 ND+PS+KK

R440 ND+PSS+KK

Firm Fixed Price

Severable Service Item

Period of Performance

4/08/2027-4/07/2028

1 Each

Option 2 Year 3 Items:

R540 ND+PS+KK

R640 Pioneer ND+PS+KK

R640 Pioneer OEMXL (Northlake) ND+PS+KK

R740 NC+PS+KK

R750 ND+PS+KK

R440 ND+PSS+KK

Firm Fixed Price

Severable Service Item

Period of Performance

4/08/2028-4/07/2029 1 Each

SECTION C - CONTRACT CLAUSES

SECTION D - CONTRACT DOCUMENTS, EXHIBITS OR ATTACHMENTS

SECTION C STATEMENT OF WORK

SECTION 1 – BACKGROUND

High throughput sequencing and other data-intensive laboratory technologies represent the cutting edge of public health laboratory science. The Centers for Disease Control's Office of Advanced Molecular Detection manages the agency's High Performance Computing Center of Excellence, which includes extensive computing, network and storage resources to support CDC's scientific and public health mission. These high-performance computing resources are used by the majority of CDC's infectious disease programs for pathogen surveillance, outbreak investigations and applied public health research.

The core infrastructure for this environment includes a High-Performance Computing (HPC) cluster consisting of Dell PowerEdge equipment listed below.

SECTION 2 – PURPOSE/OBJECTIVE

The purpose of this procurement is to extend warranty for qualified Dell computers with authorized support from the vendor.

SECTION 3 – SCOPE OF WORK

The contractor will provide level of extended warranty support listed for the following hardware: Base Period

POWEREDGE R440 – ND+PSS+ KK

POWEREDGE R730 – ND+PSS+KK POWEREDGE R540 – ND+PS+ KK POWEREDGE R640 – ND+PS+KK POWEREDGE R740 – ND+PS+KK POWEREDGE R750 – ND+PS+KK

Option 1, Year 2

POWEREDGE R540 – ND+PS+ KK POWEREDGE R640 – ND+PS+KK POWEREDGE R740 – ND+PS+KK POWEREDGE R750 – ND+PS+KK

Option 2, Year 3

POWEREDGE R540 – ND+PS+ KK POWEREDGE R640 – ND+PS+KK POWEREDGE R740 – ND+PS+KK POWEREDGE R750 – ND+PS+KK

SECTION 4 – TASKS TO BE PERFORMED

The contractor shall provide Dell hardware extended warranty as indicated in the scope of work above.

SECTION 5 – GOVERNMENT FURNISHED PROPERTY

No Government Furnished Materials

Contract Descriptions

SECTION 6 – PLACE OF PERFORMANCE AND CONTRACT SUPPORT HOURS SUBSECTION A – PLACE OF PERFORMANCE

Support will be provided remotely or on-site as needed.

SUBSECTION B – CONTRACT SUPPORT HOURS

Technical support will be provided as needed.

SECTION 7 – TRAVEL

No travel involved in this acquisition. Vendor will provide next business day onsite support as needed for hardware.

SECTION 8 – DELIVERABLES/REPORTING SCHEDULE

each option year)

(bun3@cdc.gov)

and Parish Roberts support as

(xrv5@cdc.gov) indicated in the scope above

Contract Descriptions

SECTION 9 – REFERENCE MATERIALS

Contract Descriptions

Software

Legacy Contracts (No longer available)

SECTION 11 – ADDITIONAL REQUIREMENTS

Information Security and Privacy

[ENTER TEXT HERE]

Human Subjects Protections in Research

[ENTER TEXT HERE]

Paperwork Reduction Act (PRA)

[ENTER TEXT HERE]

Section 508 Compliance

Part A – Provision

Reference HHSAR 352.239-73[8] Electronic Information and [Communication] Technology Accessibility Notice.

(Deviation)

(a) Any offeror responding to this solicitation must comply with established HHS Information and Communication Technology (ICT) accessibility standards. Information about Section 508 is available at https://www.hhs.gov/web/section-508/index.html.

(b) The Section 508 accessibility standards applicable to this solicitation are stated in the clause at 352.239-79 Information and Communication Technology Accessibility. In order to facilitate the Government’s determination whether proposed ICT supplies, products, platforms, information, and documentation meet applicable Section 508 accessibility standards, offerors must submit an appropriate HHS Section 508 Accessibility Conformance Checklist (see https://www.hhs.gov/web/section-508/accessibility-checklists/index.html) or an Accessibility Conformance Report (ACR) (based on the Voluntary Product Accessibility Template (VPAT) see https://www.itic.org/policy/accessibility/vpat), in accordance with the completion instructions. The purpose of the checklists and conformance reports are to assist HHS acquisition and program officials in determining whether proposed ICT supplies, products, platforms, information, and documentation conform to applicable Section 508 accessibility standards. Checklists and ACRs evaluate—in detail—whether the ICT conforms to specific Section 508 accessibility standards and identifies remediation efforts needed to address conformance issues.

(c) If an offeror claims its supplies or services meet applicable Section 508 accessibility standards, and it is later determined by the Government, i.e., after award of a contract or order, that supplies, products, platforms, information, documentation, or services support delivered do not conform to the described accessibility standards, remediation of the supplies, products, platforms, information, documentation, or services support to the level of conformance specified in the contract will be the responsibility of the Contractor at its expense.

(d) In order to facilitate the Government's determination whether proposed ICT supplies meet applicable Section 508 accessibility standards, offerors must submit an Accessibility Conformance Report, in accordance with its completion instructions and tailored to the requirements in the solicitation. The purpose of the Report is to assist HHS acquisition and program officials in determining whether proposed ICT supplies conform to applicable Section 508 accessibility standards. The template allows offerors or developers to self-evaluate their supplies and document, in detail, whether they conform to a specific

Section 508 accessibility standard, and any underway remediation efforts addressing conformance issues. Instructions for preparing the Template are available at https://www.section508.gov/.

(e) Additionally, offerors must provide enough information to assist the Government in determining that the ICT services conform to Section 508 accessibility standards, including any underway remediation efforts addressing conformance issues.

(f) Respondents to this solicitation must identify any inability to conform to Section 508 requirements. If an offeror claims its supplies or services meet applicable Section 508 accessibility standards, and it is later determined by the Government, i.e., after award of a contract or order, that supplies or services delivered do not conform to the described accessibility standards, remediation of the supplies or services to the level of conformance specified in the contract will be the responsibility of the Contractor at its expense.

(g) Items delivered as electronic content must be accessible to HHS acceptance criteria. Checklist for various formats are available at http://508.hhs.gov/. Materials, other than items incidental to contract management, that are final items for delivery should be accompanied by the appropriate checklist, except upon approval of the Contracting Officer or Contracting Officer’s Representative.

Part B - Clause

HHSAR 352.239-74[9] Electronic, Information, and Communication Technology Accessibility. (Deviation)

(a) Pursuant to Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998, all information and communication technology (ICT) supplies, products, platforms, information, documentation, and services, or support developed, acquired, maintained or delivered under this contract or order must comply with the Revised 508 Standards, which are located at 36 C.F.R. 1194.1 and Appendices A, B, and C, and are available at https://www.access-board.gov/ict/. Information about Section 508 is available at https://www.hhs.gov/web/section-508/index.html.

(b) Additional Section 508 accessibility standards applicable to this contract or order are identified as follows:

205 WCAG 2.0 Level A & AA Success Criteria 302 Functional Performance Criteria

502 Inoperability with Assistive Technology

503 Applications

504 Authoring Tools

602 Support Documentation

603 Support Services

If it is determined by the Government that ICT supplies, products, platforms, information, documentation, and services support provided by the Contractor do not conform to the described accessibility standards in the contract, remediation of the supplies, products, platforms, information, documentation, or services support to the level of conformance specified in the contract will be the responsibility of the Contractor at its own expense.

(c) In the event of a modification(s) to this contract or order, which adds new ICT supplies or services or revises the type of, or specifications for, supplies, products, platforms, information, documentation, or services support, the Contracting Officer shall require that the Contractor submit a completed HHS Section 508 Accessibility Conformance Checklist (see https://www.hhs.gov/web/section-508/accessibility-checklists/index.html) or an Accessibility Conformance Report (ACR) (based on the Voluntary Product Accessibility Template (VPAT) see https://www.itic.org/policy/accessibility/vpat), and any other additional information necessary to assist the Government in determining that the ICT supplies or services conform to Section 508 accessibility standards. If it is determined by the Government that ICT supplies, products, platforms, information, documentation, and services support provided by the Contractor do not conform to the described accessibility standards in the contract, remediation of the supplies, products, platforms, information, documentation, or services support to the level of conformance specified in the contract will be the responsibility of the Contractor at its own expense.

(d) If this is an Indefinite-Delivery type contract, a Blanket Purchase Agreement or a Basic Ordering Agreement, the task/delivery order requests that include ICT supplies, products, platforms, information, documentation, or services support will define the specifications and accessibility standards for the order. In those cases, the Contractor shall be required to provide a completed HHS Section 508 Accessibility Conformance Checklist (see https://www.hhs.gov/web/section-508/accessibility-checklists/index.html) or an ACR (based on the VPAT see https://www.itic.org/policy/accessibility/vpat), and any other additional information necessary to assist the Government in determining that the ICT supplies, products, platforms, information, documentation, or services support conform to Section 508 accessibility standards. If it is determined by the Government that ICT supplies and services provided by the Contractor do not conform to the described accessibility standards in the provided documentation, remediation of the supplies, products, platforms, information, documentation, or services support to the level of conformance specified in the contract will be the responsibility of the Contractor at its own expense.

(e) The contractor shall identify to the Contracting Officer any perceived exception or exemption to Section 508 requirements for review by the agency Section 508 Program.

Printing

[ENTER TEXT HERE]

[ENTER TITLE OF OTHER CLEARANCE REQUIRED]

[ENTER TEXT HERE]

OTHER CONSIDERATIONS AND ADDITIONAL INFORMATION FOR OFFICE OF ACQUISITION SERVICES

SECTION 1 – PROPOSED CONTRACT TYPE

Firm fixed price

SECTION 2 – OPTIONAL SPECIAL CONSIDERATIONS SUBSECTION A – PAYMENT CLAUSES

[ENTER TEXT FOR PAYMENT CLAUSES NEEDED HERE]

SUBSECTION B – DATA RIGHTS CLAUSES

[ENTER TEXT FOR DATA RIGHTS CLAUSES NEEDED HERE]

SECTION 3 – EVALUATION FACTORS

[ENTER TEXT HERE]

SUBSECTION A – TECHNICAL

Technical Evaluation Criteria:

This solicitation will be awarded to the Offeror whose proposal is considered to be the most advantageous to the Government, price and other factors identified below considered.

[ENTER SECTION HERE]

[ENTER ELEMENTS OF IMPORTANCE HERE] [ENTER ELEMENTS OF IMPORTANCE HERE] [ENTER ELEMENTS OF IMPORTANCE HERE]

[ENTER SECTION HERE]

[ENTER ELEMENTS OF IMPORTANCE HERE] [ENTER ELEMENTS OF IMPORTANCE HERE] [ENTER ELEMENTS OF IMPORTANCE HERE]

[ENTER SECTION HERE]

[ENTER ELEMENTS OF IMPORTANCE HERE] [ENTER ELEMENTS OF IMPORTANCE HERE] [ENTER ELEMENTS OF IMPORTANCE HERE]

SUBSECTION B – PROCUREMENT POINT OF CONTACT (POC) INFORMATION

COR/POC: Olga Stuchlik Telephone Number: 404-639-4453 E-mail Address:hus0@cdc.gov Preferred method of communication: email

Security Compliance Section

Standard-1: Procurements Requiring Information Security and/or Physical Access Security

1. Baseline Security Requirements

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:

Confidentiality: [ x ] Low [ ] Moderate [ ] High

Integrity: [ x ] Low [ ] Moderate [ ] High

Availability: [ x ] Low [ ] Moderate [ ] High

Overall Impact Level: [ x ] Low [ ] Moderate [ ] High

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. 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

1 Memorandum is available at: https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2017/m-17-12_0.pdf 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 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

2 Standard is available at: https://cdc.sharepoint.com/teams/OCIO-CSPO-PUBDOCS/Standards/CSPO%20Responding%20to%20Breaches%20of%20Personally%20Identifiab le%20Information.pdf 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:

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

Certification of Sanitization of Government and Government Activity-

Related Files, Information, and Devices.

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.

Standard-5. Other IT Procurements

1. Hardware Procurements

a. Card Readers. The Contractor (and/or any subcontractor) must include Federal Information Processing Standard (FIPS) 201-compliant smart card readers (referred to as LACS Transparent Readers) with the purchase of servers, printers, desktops, and laptops.

b. Mobile Devices. The contractor must follow NIST 800-124, Rev. 1, Guidelines for Managing the Security of Mobile Devices in the Enterprise and comply with Public Law 115-232 § 889, when purchasing mobile devices that process or store CDC data.

2. Non-Commercial and Open-Source Computer Software Procurements

The Contractor (and/or any subcontractor) must follow secure coding best practice requirements, as directed by the United States Computer Emergency Readiness Team (US-CERT) specified standards and the Open Web Application Security Project (OWASP) that will limit system software vulnerability exploits. The contractor will be liable for malicious or defective code or failure to reduce risk.

3. Information Technology Application Design, Development, or Support

a. The Contractor (and/or any subcontractor) must ensure IT applications designed and developed for end users (including mobile applications and software licenses) run in the standard user context without requiring elevated administrative privileges.

b. The contractor must consult the guidelines from NIST SP 800-160 volume 1, Systems Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems, NIST SP 800-160 volume 2, Systems Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems, and NIST SP 800-53 to implement security during the development of all applications and throughout the life cycle stages of software development.

c. The Contractor (and/or any subcontractor) must follow secure coding best practice requirements, as directed by United States Computer Emergency Readiness Team (US-CERT) specified standards, the Open Web Application Security Project (OWASP), System Admin, Audit, Network and Security (SANS), HHS Policy for Software Development Secure Coding Practices and CDC Secure Software Development Standard that will limit system software vulnerability exploits.

d. The Contractor (and/or any subcontractor) must ensure that computer software developed on behalf of CDC or tailored from an open-source product, is fully functional and operates correctly on systems configured in accordance with government policy and federal configuration standards. The contractor must test applicable products and versions with all relevant and current updates and patches updated prior to installing in the CDC environment. No sensitive data must be used during software testing.

e. The contractor must, at a minimum, segregate physically or logically, all test and development systems from production systems as applicable in accordance with the HHS Standard for Segregation of Dev/Test Environments from Production.

f. The Contractor (and/or any subcontractor) must protect information that is deemed sensitive from unauthorized disclosure to persons, organizations or subcontractors who do not have a need to know the information. Information which, either alone or when compared with other reasonably-available information, is deemed sensitive or proprietary by CDC must be protected as instructed in accordance with the magnitude of the loss or harm that could result from inadvertent or deliberate disclosure, alteration, or destruction of the data. This language also applies to all subcontractors that are performing under this contract.

4. Physical Access to Government Controlled Facilities (NOTE: For procurements involving physical access to government facilities, selected language from Appendix B: Standards may apply. This includes, but not limited to security awareness, incident response, and HSPD-12. Consult with the CDC Component Information Systems Security Officer (ISSO), CDC CPO, and other relevant stakeholders to select applicable language.)

Additionally, due to the COVID-19 Epidemic of 2020 (Effective as of March 30, 2020), The below contract language must be included in all COVID-19 contract actions until such time the CDC Director makes a determination to issue rated contracts related to items used for allowing CDC employees/contractors to physically use and/or operate in CDC facilities and spaces.

"CDC reserves the…