PWS - OCIO Data and IT Modernization Support Services - Nov 1 2021.docx

UNCLASSIFIED

GENERAL SERVICES ADMINISTRATION

FEDERAL ACQUISITION SERVICE

ASSISTED ACQUISITION SERVICES DIVISION

SOUTHEAST SUNBELT REGION

Project Name: OCIO Data and IT Modernization Support Services

PERFORMANCE WORK STATEMENT (PWS)

CENTERS FOR DISEASE CONTROL AND PREVENTION (CDC)

OFFICE OF THE CHIEF INFORMATION OFFICER (OCIO)

OFFICE OF BUSINESS OPERATIONS (OBO)

TASK ORDER NUMBER: ID0421XXXX

ACQUISITION ID: 47QFSA21K0116

AWARD PIID: 47QFSA21FXXXX

DATE: 1 NOV 2021

1.0 Introduction: Work is to be accomplished for United States Centers for Disease Control and Prevention, Office of Business Operations (OBO), Office of the Chief Information Officer (OCIO), Office of the Chief Operating Officer (OCOO), herein referred to as Client.

1.1 Points of Contact:

Phone: (404) 224-2203 E-mail: Jacqueline.Milton@gsa.gov

2.0 Purpose:

The purpose of this contract is to provide cross-cutting support to the Office of the Chief Information Officer (OCIO) in two focus areas:

a. Enterprise-wide product and service delivery assurance in support of agency modernization activities

b. OCIO internal operational activities

2.1 Background:

The CDC’s OCIO is responsible for building and maintaining the agency’s scientific infrastructure, as well as providing enterprise data and information technology (IT) products and services that support of all aspects of the agency’s mission. In this role, the Chief Information Officer and staff work at the intersections of IT, public health, and health IT to advance system and enterprise-wide scientific infrastructure, data and IT products and services, and related priorities and strategies.

The OCIO has the responsibility to ensure the effective planning, coordination and implementation of scientific infrastructure and data and IT products and services in support of agency modernization priorities. As part of this responsibility OCIO must coordinate the process for identifying, assessing, and reporting on implementation progress that tie directly and indirectly to program outputs and outcomes.

2.2 Scope of Work: This Performance Work Statement (PWS) establishes the requirements for Contractor-provided solutions in support of OCIO. The contractor shall provide all personnel, supervision, and other services necessary to perform the work as defined in this PWS in support of the CDC’s Office of the Chief Information Officer (OCIO) for this purpose of Program Management and Operational Support, Modernization Planning and Implementation Support, Communication and Engagement, Surge Support Service, Data Science, Analytics, and Consulting to support the Enterprise Data Office, and Program Analysis and Project Management.

2.3 Task Order Type: The resulting task order will be Firm Fixed Price (FFP) contract type with FFP Labor.

2.4 Period of Performance:

The availability to extend the task order for six months is also included utilizing FAR 52.217-8 Option to Extend Services clause.

3.0 Functional Requirements

3.1 Task 1: Program Management and Operational Support

The Contractor shall provide operations support to the Office of the Chief Information Officer Office of the Director (OCIO OD) to assist with coordination of OCIO-supported agency modernization activities.

For this task, the following activities shall be conducted:

3.1.1 Subtask 1.1: Provide advisory services including data, IT, financial and strategic recommendations. Develop guidance documents and other materials (e.g. data quality reports, qualitative data collection tools and templates) to facilitate the implementation of monitoring and evaluation of core activities, rapid program assessment projects, and demonstration projects

3.1.2 Subtask 1.2: Provide broad program and project management support ensure project is executed on time, in scope, and within budget.

3.1.3 Subtask 1.3: Manage, triage, and report financial, budget and programmatic OCIO modernization activities. Utilize best practices in graphical designs for development of tables and figures, slide presentations, and other methods to report M&E qualitative and quantitative data.

3.1.4 Subtask 1.4: Collaborate with Deputy Director for Public Health Science and Surveillance (DDPHSS) to ensure implementation plans across CDC’s Centers, Institutes, and Offices (CIOs) are aligned with enterprise-wide scientific infrastructure and data and IT products and services being delivered by OCIO. Recognize, advise, and inform OCIO senior management of situations that may result in duplication of efforts. Task is in direct support of the OCIO role as lead for enterprise scientific infrastructure and data and IT products and services across CDC.

3.1.5 Subtask 1.5: Create Standard Operating Procedures (SOPs) and guidance documents.

3.1.6 Subtask 1.6: Support OCIO senior leaders with administrative support in organizing meetings, providing logistical support, meeting minutes, and managing electronic filing and document version control and management.

3.1.7 Subtask 1.7: Support OCIO senior leaders with gathering, documenting and validating technical requirements for software, hardware and services in support of OCIO operations.

3.2 Task 2: Modernization Planning and Implementation Support

Activities shall be aligned to the Data Modernization Initiative (DMI) strategic framework and ongoing priority tracking activities. Working with OCIO senior leadership, provide modernization planning and implementation support.

The subtasks for Task 2 include:

3.2.1 Subtask 2.1: Working with OCIO senior leadership, plan and develop implementation roadmaps with supporting documentation to address how scientific infrastructure and data and IT products and services align to, extend and enable Centers, Institutes and Offices (CIO) projects aligned to agency modernization (may or may not be funded as part of DMI) as well as how they benefit the agency, public health partners and support U.S. Department of Health & Human Services (HHS) and national-level objectives in the use of this funding.

3.2.2 Subtask 2.2: Integrate Coronavirus Aid, Relief, and Economic Security (CARES) Act strategies with existing OCIO strategic planning to include the American Rescue Plan (ARP), DMI, and current CARES Act requirements and funding, and potential future Congressional funding appropriations initiatives to CDC.

3.2.3 Subtask 2.3: Assist the Office of the Chief Information Officer (OCIO) Office of the Director (OD) team in preparing draft products for spokespeople who provide information in a high-level, public settings.

3.3 Task 3: Communication and Engagement

Effective communications and engagement in support of OCIO’s implementation of enterprise scientific infrastructure and data and IT products and services require both communications and public health expertise. The contractor assists OCIO with leading-edge and operational support for communications and engagement with stakeholders and partners. The contractor shall bring expertise in communication and marketing, partner strategy and engagement, and stakeholder management to ensure OCIO is effectively engaging critical audiences to achieve the modernization objectives. This task includes the development of plans, tools, and materials to facilitate communication needs related to OCIO’s modernization of the agency’s scientific infrastructure.

For this task, the following subtasks include:

3.3.1 Subtask 3.1: Develop an effective engagement plan to support OCIO modernization objectives to include creating relevant materials and resources which generate appropriate awareness of relevant OCIO activities that support, enable and extend CDC and DMI priorities.

3.3.2 Subtask 3.2: Develop a communications plan that defines the various target audiences, how key content shall be delivered, communication channels, frequency and timeframes, and success metrics to track the efficacy of each communication effort. This document shall be “living document” and shall be updated continuously as partners and stakeholders are identified and as other entities request information.

3.2.3 Subtask 3.3: Develop and disseminate internal and external communication materials/documents, as needed, to support agency and OCIO priorities and ensure situational awareness and updates are reaching critical audiences.

3.3.4 Subtask 3.4: Support external communications with key audiences as needed.

3.3.5 Subtask 3.5: Support requirements-gathering and development of knowledge management mechanisms and tools to share information, resources and materials among CIOs within CDC and with external partners (including states) to meet CDC's requirements.

3.3.6 Subtask 3.6: Conduct stakeholder assessments and analyze program requirements.

3.3.7 Subtask 3.7: Provide operational support for this task.

3.4 Task 4 (Optional): Surge Support Service

In response to the COVID-19 Pandemic, Congressional action is occurring very quickly. The purpose of this task is to allow the CDC to ‘ramp up’ efforts to respond to Congressional action quickly and effectively. The Government can anticipate there may be additional appropriations in support of this effort, but specifics are not known at this time. Therefore, there may be times that surge support shall be required. The CDC anticipates a requirement for surge support to Tasks 1, 2, and Task 3. The scope of such surge support falls within the parameters of this PWS, Tasks 1, 2 and 3. Surge support may include additional labor resources and/or an increased level of effort to address the specific needs should they arise. For planning purposes, the CDC expects this level of effort to include a 50% increase in labor support for Tasks 1, 2 and 3. Task 4 would include a 50% increase in labor support for Task 3. The CDC shall provide one (1) office/cube space for support services provided by contractor personnel supporting optional Task 4.

3.5 Task 5 (Optional): Data Science, Analytics, and Consulting to support the Enterprise Data Office.

The agency’s Chief Data Officer, also the Director of the Enterprise Data Office is responsible for developing, promoting, implementing, and evaluating data science and analytic approaches across the agency, as well as developing solutions with internal and external partners to strengthen data and IT systems. This Data Science, Analytics, and Consulting support is in response to increased requirements with OCIO and shall require coordination with the efforts of the contractor in Tasks 1, 2 & 3.

3.5.1 Subtask 5.1: Gather and analyze user requirements for data systems and related scientific infrastructure.

3.5.2 Subtask 5.2: Identify, evaluate and recommend state-of-art computational infrastructures, security processes, and information technology tools to enhance agency capabilities in data and knowledge management and analysis.

3.5.3 Subtask 5.3: Apply analytical, machine learning, natural language processing, graph/network, visualization, and reporting tools to data sets to further scientific understanding and derive knowledge from data

3.5.4 Subtask 5.4: Provide expert advice and inform researchers and staff on the use of data science methods and tools.

3.5.5 Subtask 5.5: Participates with senior data scientist to aid researchers and staff in translating new data science methods and data resources into practice.

3.5.6 Subtask 5.6: Working within CDC IT and Data Governance (ITDG) and other governing bodies at the agency as well as within Health and Human Services and across the federal government, implement data and metadata standards and best practices and participate in the development of metadata policies.

3.5.7 Subtask 5.7: Assess current data management practices within the organization, assist researchers with developing data management plans, and serve as an advocate for research data stewardship.

3.5.8 Subtask 5.8: Provide data science consulting and Subject Matter Expert (SME) support and provide data analytics support to emerging projects and teams and establish collaboration opportunities across the agency and with other institutions.

3.5.9 Subtask 5.9: Provide SME support and data analytics to leadership and committees which provide scientific/technical guidance in planning and conducting data science in the following areas: Management, integration, and analysis of large datasets; architectures for large-scale data management (e.g., grids, clouds); cyberinfrastructures: architectures, operation and evolution; distributed and collaborative information environments; data mining and extraction of structure from networked information; scientific data curation; metadata for scientific data, data provenance; data and knowledge management in virtual organizations; and information visualization.

3.5.10 Subtask 5.10: Provide SMEs for design and implementation of scientific infrastructure-based solutions, including tools, techniques, and practices, that broaden the use of public health and healthcare data sets and ensure access to data throughout its lifecycle.

3.5.11 Subtask 5.11: Provide statistical and computational tools for the agency in support of modernization activities.

3.5.12 Subtask 5.12: Provide SMEs and senior consultancy to Enterprise Data Office (EDO) leadership in the creation of strategies for the development of web-based interfaces that are user-friendly and will promote usage of organizational analytical tools and databases by experts in other data domains and the lay public.

3.5.13 Subtask 5.13: Provide SMEs and senior consultancy to EDO leadership in support of data modernization efforts in the development of roadmaps to shape long-term strategic goals for enterprise data architectures, infrastructures and systems.

3.5.14 Subtask 5.14: Provide technical advice in area of expertise and evaluate technical problems as they arise and initiate appropriate action to resolve problems.

3.5.15 Subtask 5.15: Provide technical advice and expertise in public health and administrative data and health equity.

3.6 Task 6 (Optional): Program Analysis and Project Management

This task is for support of OCIO product delivery and assurance. This requirement shall provide program analyst and project management support to OCIO in coordination with federal employees and other contract personnel.

The following activities are included:

3.6.1 Subtask 6.1: Provide broad program and project management support related to data strategy, data science, and public health.

3.6.2 Subtask 6.2: Support the coordination, triaging, consolidation and reporting requirements related to CDC CARES and DMI activities.

3.6.3 Subtask 6.3: Assist in coordination of implementation plans across CDC’s Centers, Institutes, and Offices (CIOs) to ensure that agency leaders are aware of challenges and that plans are fully aligned with and complementary to other DMI activities across the agency.

3.6.4 Subtask 6.4: Support requirements-gathering and development of mechanisms and tools to share information, resources and materials among CIOs within CDC and with external partners (including states) to meet CDC's requirements. Establish regular procedures and methods to recognize, advise, and inform parties in cases of potential redundancy and raise awareness to prevent situations that may result in duplication of efforts.

3.6.5 Subtask 6.5: Assist in the development and maintenance of Standard Operating Procedures (SOPs), guidance documents, activity tracking/reporting, as well as the development of summary materials, and talking points or presenting briefing materials as needed.

3.6.6 Subtask 6.6: Support environmental scans, reviews and analysis of policies/regulations related to data strategy and data modernization.

3.6.7 Subtask 6.7: Support OCIO leaders with administrative support in organizing meetings, providing logistical support, meeting minutes, and managing electronic filing and document version control and management.

4.0 Deliverables: Delivery schedules, reports, and exhibits will be constructed in Microsoft Word, Excel, Access, Project and delivered to the COR in soft copy on an electronic medium meeting CDC system requirements. All reports are to be emailed to the COR. Any meetings will be held via Teams.

Frequency Delivery Method

3.1 3.2 4.2

3.1.2 3.1.3

MS Word or Excel.

3.1.3 3.1.4

MS Word or Excel.

1 electronic copy via MS Word or Excel.

1 electronic copy via MS Word or Excel.

Upon receipt of each deliverable, the Government will review and approve. The COR will provide written approval to the Contractor. If a deliverable is unacceptable, the Government will notify the Contractor Program Manager, who shall coordinate with the COR to determine the resubmission time.

4.1 Weekly Status Reports. All programmatic information for the work performed under this order shall be submitted to the COR by every Monday by 9AM Report. The report shall include the following:

· Narrative description of activity accomplished, to include tasks in process or completed, and functional requirements reported upon

· Issues and resolutions

· Topics or issues identified by the government TTM

· Status of deliverables, as applicable

· Coordination papers, staff studies, presentations, meeting minutes, etc., as applicable for completed and ongoing tasks.

· Financial status:

· Budgeted, actual hours by name, cumulative, and remaining dollars

· Estimated costs to completion with summary

· Task / cost variances (for >10% include explanations)

· Weekly reports are a subset of the Monthly reporting requirement

4.2 Kick-off Meeting/Post Award Conference: Within ten (10) days following the contract award, the contractor shall attend a “kick-off” meeting on a date to be jointly determined to review the contract terms and conditions including project transition. The meeting location will be determined after award. The meeting shall include discussion of the goals and objectives of the Government and discuss technical and administrative reporting requirements.

5.0 Performance Requirements Summary: The Services Summary identifies the performance objectives and performance thresholds for all critical tasks associated with providing the services outlined in this PWS. This section contains only those items considered most important for mission accomplishment. The performance objectives are those services/tasks required in the PWS. The performance thresholds briefly describe the minimum acceptable levels of service required for each requirement. The thresholds are critical to mission success. The Government expects the Contractor to perform at the acceptable levels throughout the life of the task order.

Performance Threshold

6.0 Place of Performance

6.1 Geographic Locations: The contractor shall perform majority of work at the contractor U.S. facilities. The remaining of the work shall be performed at the CDC, 1600 Clifton Road, Atlanta, GA 30333.

6.2 Hours of Operation: The contractor shall perform during the same normal duty hours as the government under the Flex Tour routine, with core hours from 0900-1500. Contractor employees may report for duty between 0600-0900. These conditions do not apply to the contractors working shifts due to the 24/7/365 requirement. Certain events may require services beyond the normal duty hours. Lunch, whether 30 minutes or one hour, will be taken within the workday. It is preferred that lunch not be taken at the end of the workday.

6.2.1 Surge Support: Surge support/extended work week (EWW) is expected to be a necessary part of this task order in accordance with the PWS and a CLIN is funded to support this requirement. When surge support is required and extended hours are authorized on this task, the contractor must obtain authorization from the COR prior to anyone working extended hours. Under no circumstances shall contractor employees exceed the approved extended hour allotment. If additional extended hours are required, the contractor shall request, in writing, through the COR that the task be amended accordingly. No further exception to policy is required.

All contractors shall remain in compliance with the Department of Labor regulations for regular and extended tour of duty hours.

6.3 Federal Holidays: The following is a list of U.S. government holidays. If the holiday falls on a Saturday, the preceding Friday is observed as the holiday. If the holiday falls on a Sunday, the following Monday is observed as the holiday. Normal work operations, which fall on a government holiday, shall be performed on the day following an observed holiday.

*Observed the Friday before or the Monday after if holiday falls on a weekend day.

7.0 Government Furnished Property (GFP):

The Government will provide the contractor access to laptops and docking stations.

a. In accordance with the terms of FAR 52.245-1, Government Property, the Government reserves the right to supply the Contractor, as Government-furnished property, any additional supplies, equipment, and materials determined by the Contracting Officer to be necessary and in the best interest of the Government.

b. Contractor-Acquired Property (CAP). The Contractor must receive written consent from the Contracting Officer prior to purchase of any CAP not expressly identified in the contract, and as defined in FAR 52.245-1.

c. Accountable and Sensitive Government Property. The Government will provide property labels and other identification for contractor-acquired Government property that is considered Accountable as defined in the HHS Logistics Management Manual (LMM) (http://www.hhs.gov/hhsmanuals/logisticsmanual/LMM.pdf) or considered Sensitive as defined in CDC's Sensitive Items List http://pgo.cdc.gov/pgo/webcache/content/DocsRepository/Logistics/REVISED_SENSITVE_ITEM_10042010.xlsx

d. The contractor shall be responsible for the control and accountable record keeping of any Government property used in the performance of this contract predominately outside the confines of a Government controlled workspace in accordance with HHS LMM Appendix Q, HHS Contracting Guide for Contract of Government Property (http://www.hhs.gov/hhsmanuals/logisticsmanual/Appendix%20Q_HHS%20Contracting%20Guide.pdf).

e.

The Chief of the Logistics Management Branch, PGO, Centers for Disease Control and Prevention (CDC), is hereby designated as the Property Administrator for this contract. The Contractor shall identify each item of equipment furnished by the Government to the Contractor or acquired by the Contractor using contract funds, with a suitable decal, tag, or other marking, as prescribed by the Property Administrator, and shall follow the guidance set forth in Appendix Q, HHS Contracting Guide for Contract of Government Property (http://www.hhs.gov/hhsmanuals/logisticsmanual/Appendix%20Q_HHS%20Contracting%20Guide.pdf).

8.0 Travel: Travel will not be necessary for this requirement.

9.0 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 both of the following:

i. Access (Physical or Logical) to Government Information: A Contractor (and/or any subcontractor) employee 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 HHS 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/ [OpDiv] 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.

Note to the Requiring Activity: Complete the following section using the information obtained from the Information Security and Privacy Certification Checklist. This information may be included after award in the event it’s not yet available at the time of acquisition.

ii. Categorize all information owned and/or collected/managed on behalf of HHS/ [OpDiv] 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, or other security representative, the risk level for each Security Objective (Confidentiality, Integrity, and Availability) and the Overall Risk Level, which is the highest watermark of the three factors of the information or information system are the following:

iii. Based on the agreed-upon level of risk, implement the necessary safeguards to protect all information systems and information collected and/or managed on behalf of HHS/ [OpDiv] 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 HHS/[OpDiv] 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 HHS/ [OpDiv] 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. Comply with the E-Government and complete all the requirements below:

Note to the Requiring Activity: Complete this section using the information obtained from the Information Security and Privacy Certification Checklist. This information may be included after award in the event it’s not yet available at the time of acquisition.

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. Based on information provided by the ISSO, Privacy Office, system/data owner, or other security or privacy representative, it has been determined that this solicitation/contract involves:

[X] No PII [ ] PII PII Confidentiality Impact Level has been determined to be: [X] Low [ ] Moderate [ ] High

iii. The Contractor must assist the OpDiv Senior Official for Privacy (SOP) or designee with conducting a Privacy Threshold Analysis (PTA) for the information system and/or information handled under this contract to determine whether or not 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 assist the OpDiv SOP or designee with completing a PIA for the system or information within [OpDiv to insert contract-specific timeline] after completion of the PTA and in accordance with HHS policy and OMB M-03-22, Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002.

· The Contractor must assist the OpDiv SOP or designee 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). CUI is defined 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 Federal 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 control, destroyed when no longer needed, or held until otherwise directed. Destruction of information and/or data must be accomplished 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 in accordance with OMB Memorandum M-06-16, Protection of Sensitive Agency Information by securing it with a FIPS 140-2 validated solution.

Note to the Requiring Activity: See the HHS Standard for the Definition of Sensitive Information and the HHS Memorandum “Sensitive PII Definition and Guidance – INFORMATION”, for additional information in defining and protecting sensitive information.

g. Confidentiality and Nondisclosure of Information. Any information provided to the contractor (and/or any subcontractor) by HHS or collected by the contractor on behalf of HHS 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 HHS 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 and [OpDiv] policies. Unauthorized disclosure of information will be subject to the HHS/ [OpDiv] 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. 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 assume HTTPS at all times to reduce the number of insecure redirects and protect against attacks that attempt to downgrade connections to plain HTTP. For internal-facing websites, the HTTPS is not required, but it is highly recommended. Consult the HHS Policy for Internet and Email Security for additional information.

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

Note to the Requiring Activity: See Appendix C for baseline deliverables. Do NOT include in procurement documentation.

k. 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 FIPS 140-2 validated encryption solution.

iii. Secure all devices (i.e.: desktops, laptops, mobile devices, etc.) that store and process government information and ensure devices meet HHS and OpDiv-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 FIPS 140-2. The Contractor must provide a written copy of the validation documentation to the COR [OpDiv-provided delivery date].

v. Use the Key Management system on the HHS 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. Encryption keys must be provided to the COR upon request and at the conclusion of the contract.

l. 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 OpDiv non-disclosure agreement. [OpDiv inserted information/link should be cited here], as applicable. A copy of each signed and witnessed NDA must be submitted to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition.

Note to the Requiring Activity: See Appendix D for the HHS Contractor Non-Disclosure Agreement. Do NOT include in procurement documentation.

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 HHS/OpDiv 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 [OpDiv-specified] Information Security Awareness, Privacy, and Records Management training at least annually, during the life of this contract. All provided training must be compliant with HHS 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 policy and the HHS Role-Based Training (RBT) of Personnel with Significant Security Responsibilities Memorandum.

c. Training Records. The Contractor (and/or any subcontractor) must maintain training records for all its employees working under this contract in accordance with HHS 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 the HHS Information Technology General Rules of Behavior, HHS Rules of Behavior for Privileged Users, and [insert any OpDiv-specific rules, as applicable].

b. All Contractor employees performing on the contract must read and adhere to the Rules of Behavior before accessing Department 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 OpDiv 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 HHS Computer Security Incident Response Center (CSIRC)/ [OpDiv] IRT teams within 24 hours, whether the response is positive or negative.

FISMA defines an incident as “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. The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines incidents as events involving cybersecurity and privacy threats, such as viruses, malicious user activity, loss of, unauthorized disclosure or destruction of data, and so on.

A privacy breach is a type of incident and is defined by Federal Information Security Modernization Act (FISMA) as 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. The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines a breach as “a suspected or confirmed incident involving PII”.

b. In the event of a suspected or confirmed incident or breach, the Contractor (and/or any subcontractor) must:

i. Protect all sensitive information, including any PII created, stored, or transmitted in the performance of this contract so as to avoid a secondary sensitive information incident with FIPS 140-2 validated encryption.

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

iii. Report all suspected and confirmed information security and privacy incidents and breaches to the OpDiv Incident Response Team (IRT) [OpDiv inserted contact information should be cited here], COR, CO, OpDiv SOP (or his or her designee), and other stakeholders, including incidents 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 OpDiv and HHS 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, contract 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.

iv. Comply with OMB M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information, HHS/OpDiv and [OpDiv] incident response policies when handling PII breaches.

v. 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 [OpDiv insert timeline if required].

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:

Note to the Requiring Activity: The Requiring Activity Representative, in conjunction with Personnel Security, must use the OPM Position Sensitivity Designation automated tool (https://www.opm.gov/investigations/) to determine the sensitivity designation for background investigations. After making those determinations, include all applicable position sensitivity designations.

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; HHS HSPD-12 policy; and Executive Order 13467, Part 1 §1.2.

Note to the Requiring Activity: For additional information, see HSPD-12 policy at: https://www.dhs.gov/homeland-security-presidential-directive-12)

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 within [OpDiv Specific timeline] of the effective date of this contract. Any revisions to the roster as a result of staffing changes must be submitted within [OpDiv Specific timeline] of the change. The COR will notify the Contractor of the appropriate level of investigation required for each staff member. [If the OpDiv has an electronic template, include that information here along with a link, if applicable.]

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, HHS Enterprise Architecture requirements to ensure information is appropriately…