D1- 75D301-25-F-20585 v2 CO signed 29 Jul 2025.pdf

ORDER FOR SUPPLIES OR SERVICES

PAGE OF PAGES

1 46

IMPORTANT: Mark all packages and papers with contract and/or order numbers.

1. DATE OF ORDER 2. CONTRACT NO. (If any) 6. SHIP TO:

07/29/2025 47QTCA22A0008 a. NAME OF CONSIGNEE

3. ORDER NO. 4. REQUISITION/REFERENCE NO. CDC DISTRIBUTION CENTER (Warehouse)

75D30125F20585 0HCAJRJK-2025-94607 b. STREET ADDRESS

5. ISSUING OFFICE (Address correspondence to)

Centers for Disease Control and Prevention Chamblee Campus Building 102, MS S102-4 4770 Buford Hwy Atlanta, GA 30341-3717

3719 NORTH PEACHTREE RD.

c. CITY

CHAMBLEE

d. STATE

GA

e. ZIP CODE

30341-2221

f. SHIP VIA

a. NAME OF CONTRACTOR

CARAHSOFT TECHNOLOGY CORP

UEI: DT8KJHZXVJH5 8. TYPE OF ORDER

b. COMPANY NAME

a. PURCHASE X b. DELIVERY

REFERENCE YOUR:

c. STREET ADDRESS

11493 SUNSET HILLS RD

d. CITY

RESTON

e. STATE

VA

f. ZIP CODE

20190-

9. ACCOUNTING AND APPROPRIATION DATA

See Section B

10. REQUISITIONING OFFICE

HCAJRJK

11. BUSINESS CLASSIFICATION (Check appropriate box(es))

a. SMALL X b. OTHER THAN SMALL c. DISADVANTAGED d. WOMEN-OWNED

12. F.O.B. POINT

Destination

13. PLACE OF

a. INSPECTION b. ACCEPTANCE

14. GOVERNMENT B/L NO.

15. DELIVER TO F.O.B. POINT

ON OR BEFORE (Date)

07/28/2026

16. DISCOUNT TERMS

Net 30 Days

17. SCHEDULE (See reverse for Rejections)

ITEM NO.

(a)

SUPPLIES OR SERVICES

(b)

QUANTITY

ORDERED

(c)

UNI

T

(d)

UNIT

PRICE

(e)

AMOUNT

(f)

QUANTITY

ACCEPTED

(g)

This will be a Firm Fixed-Price Order. To ensure payment, the invoice must reference the order number, DUNS/UEI, and Tax

ID Numbers. Information regarding IPP, including IPP

Customer Support contract information, is available at www.ipp.gov.

Contractor: Timothy VanLandeghem Phone: 571-662-4218

Email: Timothy.VanLandeghem@carahsoft.com

CDC COR: Andrew Gonzales

Phone: 770-488-1584

Email: slx1@cdc.gov

CDC Contracting Specialist: Kenyadah Gamble

Phone: 770-488-5244 Email: xvw0@cdc.gov

18. SHIPPING POINT

19. GROSS SHIPPING WEIGHT

20. INVOICE NO.

21. MAIL INVOICE TO: $5,098,972.44

a. NAME

Centers for Disease Control and Prevention (FMO)

b. STREET ADDRESS (or P.O. Box)

PO Box 15580 404-718-8100

c. CITY

Atlanta

d. STATE

GA

e. ZIP CODE

303330080

$5,098,972.44

22. UNITED STATES

OF AMERICA (Signature)

23. NAME (Typed)

Sheena Delaine

TITLE: CONTRACTING/ORDERING OFFICER

NSN 7540-01-152-8083

PREVIOUS EDITION NOT USABLE

OPTIONAL FORM 347 (REV. 6/95)

Prescribed by GSA/FAR 48 CFR 53.213(e)

Except for billing instructions on the reverse, this delivery order is subject to instructions contained on this side only of this form and is issued subject to the terms and conditions of the above-numbered contract.

Please furnish the following on the terms and conditions specified on both sides of this order and on the attached sheet, if any, including delivery as indicated.

17(h) TOT.

(Cont.

pages) SEE BILLING

INSTRUCTIONS

ON

REVERSE

17(i)

GRAND

TOTAL

7. TO:

http://www.ipp.gov/ mailto:Timothy.VanLandeghem@carahsoft.com mailto:slx1@cdc.gov mailto:xvw0@cdc.gov

SUPPLEMENTAL INVOICING INFORMATION

If desired, this order (or a copy thereof) may be used by the Contractor as the Contractor’s invoice, instead of a separate invoice, provided the following statement, (signed and dated) is on (or attached to) the order: “Payment is requested in the amount of $_____. No other invoice will be submitted.”

However, if the Contractor wishes to submit an invoice, the following information must be provided: contract number (if any), order number, item number(s), description of supplies or service, sizes, quantities, unit prices, and extended totals. Prepaid shipping costs will be indicated as a separate item on the invoice. Where shipping costs exceed $10 (except for parcel post), the billing must be supported by a bill of lading or receipt. When several orders are invoiced to an ordering activity during the same billing period, consolidated periodic billings are encouraged.

RECEIVING REPORT

Quantity in the “Quantity Accepted” column on the face of this order has been inspected, accepted, received by me and conforms to contract. Items listed below have been rejected for the reasons indicated.

SHIPMENT PARTIAL DATE RECEIVED SIGNATURE OF AUTHORIZED U.S. GOV’T REP. DATE

NUMBER FINAL

TOTAL CONTAINERS GROSS WEIGHT RECEIVED AT TITLE

REPORT OF REJECTIONS

ITEM NO. SUPPLIES OR SERVICES UNI

T

QUANTITY

REJECTED REASON FOR REJECTION

OPTIONAL FORM 347 (REV. 6/95) BACK

47QTCA22A0008 75D30125F20585

SECTION A – CONTRACT FORM LANGUAGE

1. Order No. 75D301-25-F-20585 is awarded against General Services Administration (GSA) Blanket

Purchase Agreement (BPA) No. 47QTCA22A0008, to CARAHSOFT TECHNOLOGY CORP, for the purchase of commercial ServiceNow Enterprise Software Licenses as detailed in Section B.

2. Performance usage shall commerce on July 29, 2025, and continue as identified for each Contract Line-

Item Number (CLIN) in Section B.

3. The CDC Point of Contacts (POCs) for this order is Andrew Gonzales (COR), slx1@cdc.gov and

Kenyadah Gamble (CS), xvw0@cdc.gov.

4. The total obligated amount and value of this order is $5,098,972.44.

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

mailto:slx1@cdc.gov mailto:xvw0@cdc.gov

ITEM SUPPLIES / SERVICES QTY /

UNIT

UNIT

PRICE

EXTENDED PRICE

0001 Additional Non-Production Instance

PROD00070-2

ServiceNow

Additional Non-Production Instance

Period of License Usage: July 29, 2025 - July

28, 2026

Firm Fixed Price Line Item

24 Each $1,124.36 $26,984.64

Line(s) Of Accounting:

939014P 257P 2025 75-25-0949 5614D11101

$19,247.00

9390GS1 257P 2025 75-25-0955 5613131201

$280.28

939ZRQS 257P 2025 75-25-0950 5610411101

$7,457.36

0002 ServiceNow ITOM Operator Pro v2

PROD14995-2

ITOM AIOps Professional – Subscription

Firm Fixed Price Line Item

24,000 Each $21.59 $518,160.00

Line(s) Of Accounting:

9390J4Y 257P 2025 75-X-4553 5698111101

$518,160.00

0003 ServiceNow Agile Team Module

PROD12492-2

Agile Team – Module

Firm Fixed Price Line Item

12 Each $0.00 $0.00

0004 ServiceNow AI Search Starter

PROD15338-2

AI Search Starter - Documents

Firm Fixed Price Line Item

12 Each $0.00 $0.00

0005 Instance Gov (FedRAMP) Data Ctr

PROD188818

FedRAMP Premium for Production/Non-

Production Instances - GCC Internet POD

Firm Fixed Price Line Item

60 Each $375.08 $22,504.80

Line(s) Of Accounting:

93907PW 257P 2025 75-25-0951 5612311101

$2,690.68

939ZRQS 257P 2025 75-25-0950 5610411101

$7,234.12

939ZXTV 257P 2025 75-X-4553 5698111101

$12,580.00

0006 ServiceNow Business Stakeholder user v4

PROD17800-2

Business Stakeholder User v4

Firm Fixed Price Line Item

5,640 Each $26.10 $147,204.00

Line(s) Of Accounting:

939ZTRJ 257P 2025 75-25-0949 5614B11101

$147,204.00

0007 Database Encryption

PROD08358-2

Database Encryption

Firm Fixed Price Line Item

12 Each $7,486.77 $89,841.24

Line(s) Of Accounting:

9390BRR 257P 2025 75-25-0950 5610118101

$13,379.52

939ZUVC 257P 2025 75-X-4553 5698111101

$76,461.72

0008 ServiceNow Strategic Portfolio Management

PROD23774-2

Strategic Portfolio Management Professional v2 -

SPM User

Firm Fixed Price Line Item

420 Each $112.43 $47,220.60

Line(s) Of Accounting:

$47,220.60

0009 ServiceNow ITOM Visibility v2

PROD14997-2

IT Operations Management Visibility v2 -

Subscription Unit

Firm Fixed Price Line Item

18,000 Each $10.68 $192,240.00

Line(s) Of Accounting:

9390J4Y 257P 2025 75-X-4553 5698111101

$87,289.48

$104,950.52

0010 Customer Svc Mgmt. Pro Fulfiller User v7

PROD19279

Customer Service Management Professional

Fulfiller User v7

Firm Fixed Price Line Item

14,760 Each $156.19 $2,305,364.40

Line(s) Of Accounting:

9390J4Y 257P 2025 75-X-4553 5698111101

$119,519.52

9390PPJ 257P 2025 75-X-4553 5698211101

$2,182,181.76

939ZRQS 257P 2025 75-25-0950 5610411101

$1,484.52

$2,178.60

0011 Security Operations Enterprise VR

PROD20826-2

Security Operations Enterprise - VR v2 – Devices

Firm Fixed Price Line Item

672,000

Each

$1.53 $1,028,160.00

Line(s) Of Accounting:

9390J4Y 257P 2025 75-X-4553 5698111101

$809,751.00

9390PPJ 257P 2025 75-X-4553 5698211101

$218,409.00

0012 App Engine Fulfiller

PROD19351-2

App Engine Enterprise - Fulfiller User

Firm Fixed Price Line Item

300 Each $134.76 $40,428.00

Line(s) Of Accounting:

$40,428.00

0013 ServiceNow Hardware Asset Management v2

PROD16047-2

Hardware Asset Management Professional -

Subscription Unit v2

Firm Fixed Price Line Item

134,400

Each

$3.52 $473,088.00

Line(s) Of Accounting:

9390J4Y 257P 2025 75-X-4553 5698111101

$473,088.00

0014 Workflow Data Fabric Stord Unattended

Robot

PROD24512-2

Workflow Data Fabric Standard - Unattended

Robot

Firm Fixed Price Line Item

12 Each $14,616.33 $175,395.96

Line(s) Of Accounting:

9390BRR 257P 2025 75-25-0950 5610118101

$30,526.48

939ZTLM 257P 2025 75-25-0956 5623221201

$93,544.00

$51,325.48

0015 ServiceNow Workflow Data Fabric Bdle v2

PROD18251-2

Workflow Data Fabric Bundle v2 - 1 million

Integration Hub Transactions - Transaction Pack

Firm Fixed Price Line Item

12 Each $2,698.40 $32,380.80

Line(s) Of Accounting:

9390GS1 257P 2025 75-25-0955 5613131201

$27,449.72

$4,931.08

SECTION C – STATEMENT OF WORK

Centers for Disease Control and Prevention

Office of the Chief Information Officer (OCIO) Office of Business Operations (OBO)

Title: ServiceNow Enterprise Software License

1. Background and Need:

The CDC has previously procured brand name ServiceNow software licensing under task orders in support of

OCIO to provide a cloud and web portal for customer engagement from 2019 to 2025. This requirement is to purchase licensing for 12-months from time of award, as estimating the number of licenses continuously needed beyond a year is difficult due to the unknown number of users, and constant change in product and ski numbers.

It is in the best interest of the government to procure these licenses on an annual basis by the most efficient means necessary.

2. Project Objective:

The purpose of this procurement brand name ServiceNow software licensing to provide the Government with automated workflows for operational support for CIO cloud and a web page “Portal” for customer cloud engagement.

3. Scope of Work:

This is a Firm Fixed-Price (FFP) commercial-off-the-shelf (COT) Supplies procurement for ServiceNow software licensing with no specific scope of work.

4. Deliverables: The Contractor shall provide ServiceNow licenses no later than 3 days after award.

5. Period of Performance: Licensing usage shall be provided for twelve (12) months from time of award.

6. Technical Requirements:

6.1. Product suite must support multiple critical service lines, policies, processes, and supporting procedures.

6.2. The product must maintain a FedRAMP HIGH Authorization, support multi-cloud operations, and have fully configurable out of the box performance analytics, reporting, and dashboards.

6.2.1. Ability to provide full scope service desk and case management support with self-service capabilities for internal and external users that can enforce SLA; and automate incident, problem, and change management.

6.3. Provide full visibility into how all the incidents and change management requests will affect the IT infrastructure by mapping to different services and the CMDB.

6.3.1. Moreover, include an out of the box portal that includes virtual agents, agent chat, campaign tasks, knowledge base repository, Machine Learning (ML) driven content recommendations, content experiences, content publishing, publishing Enterprise Search, and Enterprise forums.

6.3.2. It must perform cloud and on-prem hardware and software discovery, cloud service mapping, operational intelligence, health management, and cloud resource provisioning and insights.

6.4. The product’s Service Catalog must provide the ability to improve customer and employee service, and accelerate service delivery, allow interaction for external users, and act as a UX Service Portal.

6.5. The product must enforce the hardware and software lifecycle automation; assist with the ability to normalize software and hardware content and state; and manage licenses of complex publishers.

6.6. The product should also help provide software and hardware savings opportunities.

6.7. The product must assess Dynamic Application Security Testing (DAST) results to track against vulnerable items, coordinate fixes, and provide a dashboard summarizing active application vulnerabilities in the organization.

6.7.1. Easily integrate (inbound and outbound) with third party systems with either automatic pre-configured workflows or by using web services tools.

6.8. The product must also have the ability to encrypt data at rest in the database with no impact to functionality.

6.8.1. This should be accomplished by utilizing native capabilities of the database engine to encrypt data as it is written to the database and decrypt as it is read from the database using industry standard AES encryption.

6.9. The product must also provide an agile software development environment using the Scrum framework and offer the flexibility to implement either a pure agile approach over the entire lifecycle of a product, or a hybrid approach using agile methods within a waterfall project structure.

6.10. The product must guide and coach the CDC to see the full investment of the solution with the help of a team and experts.

6.11. Finally, as part of the platform customer support service, ServiceNow advisors must help the organization focus on business outcomes and accelerating adoption of the product, keep the platform in line with best practices, and support operations and escalated issues by managing the system health and coordinating major events. This team must also provide a tailored roadmap, curated content, tailored recommendations, proactive insights, and enhance support.

7. Reporting Schedule: None.

8. Payment Schedule: Contractor shall invoice the Government annually in accordance with the terms and conditions of the contract.

9. Authorized Reseller Instruction: Only authorized ServiceNow resellers shall be considered.

10. Government Furnished Property: Government Furnished Property does not apply to this requirement.

11. Section 508 Compliance and Accessibility Requirements:

Electronic and Information Technology Accessibility Notice:

(a) Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce

Investment Act of 1998 and the Architectural and Transportation Barriers Compliance Board Electronic and Information (EIT) Accessibility Standards (36 CFR part 1194), require that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by

Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

(b) Accordingly, any offeror responding to this solicitation must comply with established HHS EIT accessibility standards. Information about Section 508 is available at http://www.hhs.gov/web/508. The complete text of the Section 508 Final Provisions can be accessed at http://www.access-board.gov/sec508/standards.htm.

(c) The Section 508 accessibility standards applicable to this contract are: 1194.

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 http://www.hhs.gov/web/508 http://www.access-board.gov/sec508/standards.htm http://www.access-board.gov/sec508/standards.htm

To facilitate the Government's determination whether proposed EIT supplies meet applicable Section 508 accessibility standards, offerors must submit an HHS Section 508 Product Assessment Template, in accordance with its completion instructions. The purpose of the template is to assist HHS acquisition and program officials in determining whether proposed EIT supplies conform to applicable Section 508 accessibility standards. The template allows offerors or developers to self-evaluate their supplies and documentation detail - whether they conform to a specific Section 508 accessibility standard, and any underway remediation efforts addressing conformance issues. Instructions for preparing the HHS Section 508

Evaluation Template are available under Section 508 policy on the HHS Web site http://hhs.gov/web/508.

(d) Respondents to this solicitation must identify any exception 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 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.

(e) Electronic content must be accessible to HHS acceptance criteria. Checklist for various formats is available at http://508.hhs.gov/, or from the Section 508 Coordinator listed at https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html. Materials that are final items for delivery should be accompanied by the appropriate checklist, except upon approval of the Contracting Officer or Representative.

12. Information Security and Privacy

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

http://hhs.gov/web/508 http://508.hhs.gov/ https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html

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 PII is collected, disseminated, maintained, or disposed as part of the contract. The PTA will determine if a 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 http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf 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) 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:

f) 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/support 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.

g) 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 a current FIPS 140 validation certificate from the NIST CMVP.

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

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

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

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

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

m) 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 a 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 a 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.

n) 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 http://csrc.nist.gov/publications/ 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 a 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 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, can 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 stop 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):

http://intranet.cdc.gov/od/hcrmo/pdfs/hr/Out_Processing_Checklist.pdf

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

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 Act

It has been determined that this contract is subject to the Privacy Act of 1974, because this contract provides for the design, development, or operation of a system of records on individuals.

The System of Records Notices (SORN) that are applicable to this contract are GSA/GOVT-4, “Contracted Travel Services Program (E-Travel)” and 09-90-1402, "HHS Payroll Records ". The design, development, or operation work the Contractor is to perform is outlined above in Section 4, “Tasks to be

Performed”.

The disposition to be made of the Privacy Act records upon completion of contract performance is 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

Records kept for a Federal agency are maintained in accordance with the General Records Retention Schedules issued by the National Archives and Records Administration (NARA), or an Agency and NARA-approved records disposition schedule.

With specific reference to Time and Attendance records: System records are maintained for a minimum of

5 years for hard copy documents and 7 for electronic. The system follows GRS 5.1.

Standard-3 Procurements Involving Government Information Processed on GOCO or COCO

Systems

1) Security Requirements for GOCO and COCO Resources

a) Federal Policies. The Contractor (and/or any subcontractor) must comply with applicable federal laws, directives and CDC policies that include, but are not limited to, HHS Information Security and Privacy

Policy (IS2P), the CDC IT Security Program Implementation Standards, Federal Information Security

Modernization Act (FISMA) of 2014, (44 U.S.C. 101); National Institute of Standards and Technology

(NIST) Special Publication (SP) 800-53, latest revision, Security and Privacy Controls for Information

Systems and Organizations; Office of Management and Budget (OMB) Circular A-130, Managing Information as a Strategic Resource; and other applicable federal laws, regulations, NIST guidance, and agency policies.

b) Security Assessment and Authorization (SA&A). A valid authority to operate (ATO) certifies that the

Contractor's information system meets the contract's requirements to protect the agency data. If the system under this contract does not have a valid ATO, the Contractor (and/or any subcontractor) must work with the agency and supply the deliverables required to complete the ATO prior to any use of the system in a production capacity, i.e., its intended users able to collect, store, process or transmit data to fulfill the system’s function. within the specified timeline(s). The Contractor must conduct the SA&A requirements in accordance with HHS IS2P/CDC IT Security Program implementation standard and

Appendix K: CDC Organizationally Defined Minimum Numbers and Time Periods Derived from NIST SP 800-53 Revision 5, NIST SP 800-37, Guide for Applying the Risk Management Framework to

Information Systems: A Security Life Cycle Approach (latest revision), NIST SP 800-53B, Control

Baselines for Information Systems and Organizations, and the NIST SP 800-53A (latest revision). CDC acceptance of the ATO does not alleviate the Contractor's responsibility to ensure the system security and privacy controls are implemented and operating effectively.

i) SA&A Package Deliverables - The Contractor (and/or any subcontractor) must provide an

SA&A A package timeline, process, and formats proscribed for a Full system authorization in the

CDC Security Assessment and Authorization Standard Operating Procedure (CDC SA&A SOP).

The following SA&A deliverables are required to complete the SA&A package.

• Baseline System Information (BSI) – The Contractor will document a system overview, in accordance with the timeline, process and formats described in the CDC SA&A SOP. The BSI will include information concerning system identification and ownership; system data, information types, impact levels and system categorization; system functional description / general purpose; system authorization boundary and environment; system user descriptions; and system interconnections and dependencies. The Contractor shall update the BSI at least annually thereafter.

• Privacy Threshold Analysis / Privacy Impact Analysis – The Contractor (and/or any subcontractor) shall provide a PTA/PIA (as appropriate), in accordance with the timeline, process and formats described in the CDC SA&A SOP, if applicable. Also see the sections of this contract concerning “Privacy Threshold Analysis (PTA)/Privacy Impact Assessment

(PIA)” and “Requirements for Procurements Involving Privacy Act Records.” NOTE: If social security numbers (SSN) are expected to be…