A1 - (b) - Statement of Work.docx

Statement of Work Development, Maintenance and Enhancements of NCCDPHP IT Services I. Background and Need:

The Centers for Disease Control and Prevention (CDC) National Center for Chronic Disease Prevention and Health Promotion (NCCDPHP), Office of Informatics and Information Resources Management (OIIRM) provides information technology and informatics portfolio management services for the Center. This involves analysis, design, development, implementation, support and evaluation of all information systems residing on the NCCDPHP Platform, and under the OCIO consolidated platform allocated to NCCDPHP or other Centers in DDNID. The applications in this portfolio continuously evolve and are subject to change throughout the period of performance of this contract. OIIRM also provides data management, integration services, and consultation to support NCCDPHP lines of business as well as integration with programmatic functions. OIIRM also provides knowledge management services including information retrieval, information mapping, information sharing, daDevta categorization, infrastructure support, and knowledge capture.

The products and services developed, managed, and maintained by OIIRM are used across NCCDPHP and other Centers hosted on the NCCDPHP platform or the OCIO consolidated platform or utilize shared services provided by OIIRM. This includes applications that were formerly NCCDPHP and remain hosted on the NCCDPHP platform, and other program work that are not hosted on the NCCDPHP platform. This also includes applications from other Centers in an effort to avoid duplication of services and IT modernization and consolidations efforts across CDC and as the need for public health collaborative efforts expand. This work order will directly support numerous important CDC programs and initiatives in achieving the Agency’s public health objectives. As public health missions and needs evolve, OIIRM must continually modernize, monitor and update its’ software and information management capabilities to meet those needs and to capitalize on emerging capabilities and technologies.

OIIRM operations are supported, in part, by contractor personnel tasked with a full range of support functions across the application development lifecycle and consistent with CDC’s implementation of the HHS Enterprise Performance Lifecycle (EPLC). NCCDPHP is establishing this NCCDPHP Application Portfolio Support and Information Services (NAPSIS) work order to provide NCCDPHP and affiliated Centers with a reliable, flexible, cost-effective, and innovative source of application development and related support services including operations, communications, training, information assurance, research, and other services necessary for the execution of the NCCDPHP mission. In addition, and on a limited and selective basis, other Centers, Institutes, and Offices (CIOs) within CDC will be permitted to use this contract in support of in-scope requirements.

II. Project Objective:

The purpose of this contract is to obtain support for NCCDPHP’s Informatics and public health information and data systems development activities and ensure that these are:

· Effectively, efficiently and collaboratively managed

· Consistent with CDC’s IT investment policies and frameworks

· Responsive and relevant to diverse NCCDPHP and other CDC program mission needs and requirements

· Strategically anticipatory to ensure effective use of current and emerging technologies and methods

· Innovative and cost-effective

· Supportive of ongoing maintenance and operations

The scope of this contract is for contractor support services such as: technical support and consultation for IT applications development, data management and analysis, and information services across the portfolio of applications for the purpose of providing high quality and reliable software and systems.

III. Description of Work:

Task 1: Security Ensuring a modern, cloud enabled, high quality infrastructure and architecture is important for the ongoing operations of the NCCDPHP informatics and public health systems portfolio. Coordination with other Centers and Offices within CDC as well as other potential or existing service providers will be a necessary part of new development as well as ongoing operations and maintenance. There will be quality improvement activities related to data modernization, cloud migration, and strengthening the infrastructure and architecture.

The contractor must conduct vulnerability scans on new and existing software, applications, and components to help define, identify, classify and prioritize vulnerabilities affecting CDC systems. These scans shall proactively identify exploitable vulnerabilities, confirm remediation of identified vulnerabilities, assist with investigating possible system compromise, and contribute to certifying or recertifying a system for an Authority to Operate (ATO).

The vulnerability scans are part of security monitoring of all new and existing systems and applications to identify weaknesses. Once identified, the contractor will develop, implement, and manage a corrective action plan, also known as a Plan of Action and Milestone (POA&M) for all programs and systems. A POA&M shall outline identified information security program and system weaknesses along with the tasks necessary to mitigate them and provide a means of planning and monitoring the corrective actions. CDC has established timeframes for remediation of system vulnerabilities, based on the risk to the enterprise. These timeframes apply to all CDC information systems and all applications operated by or on behalf of CDC, including those at contractor-operated and cloud provider sites.

Task 2: Microsoft 365 As M365 continue to evolve and become more valuable in the center, the contractor shall design and support custom solutions that improve user adoption, productivity, increase efficiencies and abilities to process and respond to informational requests, provide technical assistance, and streamline processes. These applications will support functions across NCCDPHP and NCBDDD. Activities could include:

2.1 Plan, Design, Create, Modify, Manage, and Maintain Division SharePoint sites, services, and solutions

· Using out-of-the-box document management, workflow, and collaboration functions. Sites, MS Teams, and solutions will support collaboration across workgroups and units within NCCDPHP & NCBDDD.

· Each will have sites containing lists, libraries, pages, and connected SharePoint hubs. MS Teams, MS Planner, and MS Forms are often used as well.

· Design specifications will be consistent with “out-of-the-box” SharePoint and should not to be enhanced or extended beyond its original purpose, but can be natively integrated with other Microsoft 365 products and services.

· Nintex forms and workflows will often be necessary.

· SharePoint Framework (SPFx) may be required in rare circumstances but only as last resort when other tools and services are not sufficient to meet the need.

2.2 Conduct Needs Assessments with NCCDPHP regarding their M365 project needs

2.3 Advice and Technical Consultation

· Provide advice, technical consultation and guidance to customers by analyzing and resolving problems, and evaluating alternative means of satisfying user requirements.

· Advise on changes/enhancements to existing help desk, or provide a new “help desk” concept (a standardized way for staff in each division to email or call in their SharePoint, Office 365, and Teams questions, and a way to track and record the resolution of these questions) to improve support response times and quality of service.

2.4 Develop, Plan, and Execute Microsoft 365 “Continuing Education” events

2.5 Participate in SharePoint User Groups

Task 3: IT Modernization and Cloud Migration Modernization and cloud migration is vital to the continuing success of the CDC and NCCDPHP’s technical infrastructure. The consultant will assist NCCDPHP data modernization efforts by providing information technology, data science, systems engineering, and knowledge management services. These services will support data modernization in the following areas:

3.1 Information Technology and Modeling Services

· Help business leaders enable their future-state business capabilities that, in turn, drive the organization’s targeted business outcomes for data modernization through the choice of programs, projects, and initiatives the chooses to invest in.

· Practically applying existing, new and emerging technologies to new and evolving business and operating models. Deliver signature-ready, actionable recommendations to business leaders, so they can adjust policies and project achieve target business outcomes.

· Assist with managing and balancing a bimodal architecture program, tactical, to run, grow and transform the business, and strategy, which designs and enables future-state business capabilities with a focus on technology disruption, speed, agility, and flexibility.

· Inform the design of current state and future state diagrams for each data modernization and IT Systems Modernization effort using common data modeling (CDM) principles and UML modeling.

3.2 Data Science Consultation

· Serves as an expert resource in supporting maximizing of data as part of our Cloud Migration Strategy, Data Integration efforts, Data Inventory, and Data Mapping activities related to data management, analysis, reporting, and visualization.

· Development, use, and evaluation of standards, models, processes, and systems to optimize the design and inform public health decision making at all levels.

· Close collaboration with other disciplines and departments within and across NCCDPHP Divisions and Programs is necessary.

3.3 System Engineering and Design Optimisation Consultation

· Aid NCCDPHP in leading agile software development efforts. This role will respond to audits and contribute to the RFP process. Ensure data governance and best practice is embraced. Responsible for understanding business and IT strategy to align with outcomes.

· Write quality code, assist with problem solving, root cause analysis, trouble shooting and coaching.

· Understand big picture from a business standpoint within the context of the application.

· Define improvements to increase system reliability, security and performance. Perform rich data visualizations and presentations to senior management on value adds.

· Participate in defining strategic IT objectives and leading subordinates toward that strategic vision for their products.

· Tracks all project requests in functional area and updates status of projects on a regular basis.

· Assists in estimating work effort associated with new project requests.

· Assists in planning for the development and support of a functional systems area.

· Participates in planning and budgeting

Task 4: NCCDPHP Data Lake/Hub The preliminary strategy for the NCCDPHP Data Lake is to enable NCCDPHP to address timely disease management, reporting, and analytic needs by providing a repository of "curated" data from Chronic Surveillance systems and non-Chronic data sources with the addition of "in-progress" or "operational" data as the lake matures. All data will be hosted with CDC infrastructure with ingestion pipelines specific to divisions/datasets and visualization specific to division needs.

4.1 Strategic Approach

The development of a strategic approach to NCCDPHP data lake activities should include:

· Future integration with DDNID activities

· Needs assessments (current and future state) and use case development (and/or identify data assets for ingest)

· Data acquisition plans

· Identification and implementation of the Data Lake artifacts

· Short- and long-term IT governance approach that includes onboarding new activities, maintaining existing, and retiring assets

· Data governance strategy that includes data management plans, data use agreements, ingest new data assets and maintain existing assets

· Identify "in-progress" and "operational" data assets and feeds from existing NCCDPHP systems

· Understand Visualization and AI/ML needs and implement

4.2 Analytics Strategy

As NCCDPHP continues to mature its Data Lake, the focus of the project will shift from populating the Lake with curated data to analytics. As the work continues, analysis of tools will be needed to allow NCCDPHP to:

· Identify any analytics tools unique to NCCDPHP (e.g. Social Determinants of Health)

· Leverage existing resources from CDC’s Enterprise Data Analytics and Visualization tools

· Leverage best practices and existing resource from other CDC Center data lakes

4.3 Implementation

Once the overall strategy is laid out and approved, the focus of the project will shift to building out the lake and any associated assets. This includes completing its full design and supporting applications; facilitating its implementation and dissemination throughout NCCDPHP and to external partners; integrating its data, design, and practices with agency data modernization initiatives; and supporting maintenance and improvements through the life of this contract.

· Create data pipelines ingesting source data and transforming it to “gold” data products for consumption

· Create analytic tools for downstream program use

· Create visualization products for CDC program use and external use

Task 5 : Data Modernization Strategic Coordination and Tools Development

5.1 IT Strategic Planning and Reporting Tool, Knowledge Repository, and DMI Dashboard

Build upon previous development efforts by:

· Working closely with OIIRM to identify and implementing system enhancements and developing requirements documents.

· Development of project artifacts that support the above. These could include, but not limited to:

· Business and Functional Requirements

· Test Plan/Cases and Results

· In-scope features

· Database Architecture and Design

· System Architecture

· Developing a roadmap module within the IT Strategic Planning and Reporting tool which should include assessment questions, recommendations, templates for different DMI-related roadmaps, etc.

· Exploring auto-generation of current and future state diagrams.

· Developing a prioritization and ROI module.

· Expanding the knowledge repository to include, but not limited to, interface for users to search documents and use cases, upload documents, etc.

· Developing backlog items transferred from previous contractor.

· Working with OIIRM to identify, prioritize, and implement dashboard enhancements throughout the contract period. Some enhancements include, but not limited to, integration with the IT Strategic Planning and Reporting Tool, PowerApp refinement, refine pages for different personas.

· Providing consultation and support to OIIRM on development of new views in the DMI dashboard developed by OIIRM within PowerBI.

· Maintenance of the suite of IT Strategic Planning and Reporting Tool, Knowledge Repository, DMI Dashboard, and PowerApp.

5.2 Community of Practice (CoP)

Provide the following consultation and/or participate in OIIRM’s data modernization data lake, cloud, and IT Surveillance Systems Modernization CoPs and office hours.

· Work with OIIRM to plan CoP topics and develop presentations

· Consult on how to best achieve CoP deliverables.

· Attend CoPs and Office Hours for data lake, cloud, and IT Surveillance Systems Modernization.

· Provide facilitation services for CoPs and Office Hours including scheduling meetings, recording minutes, identifying next steps, and documenting outcomes

· Provide input on evaluating CoPs.

Task 6 : NCCDPHP Governance Provide support to OIIRM in managing the progress and appropriate governance of NCCDPHP projects including tracking of all IT and data investments that require local governance review and submission to the ITDG, as well as Stage Gate Reviews for active projects.

Dashboards will be created to allow information to be shared at the appropriate level.

Information to be collected/Displayed include:

· Project inventory and status

· Portfolio Management including

· System inventory management

· Informatics portfolio

· IT planning tool

· Data modernization roadmaps

· Procurement portfolio

· Capture of funding for current procurements

· Monthly division contract status reports

Task 7 : IT Architecture

· Convert complex and nuanced business problems into customized solutions within emerging health sciences.

· Working across diverse teams, develop solutions and execute excellent client delivery within a fast-pace and growing industry.

· Understand process improvement and risk and control design and utilize knowledge and skills to analyze and improve business processes within NCCDPHP

· Actively contribute to research, analysis, and presentation development. Play a critical role in program transformation and sustainable, human-centered change, working together with other teams and partners to co-create and deliver strategy and operations solutions for delivery and improvement in support of NCCDPHP’s public health mission.

· Develop high-quality, logically structured, and technically accurate process flows, analyses, and written and verbal communications to guide client conversations and deliver actionable recommendations

· Co-creates new business processes that demonstrably improve efficiency and effectiveness for the client

· Tactfully delivers and graciously receives timely, constructive, and actionable feedback to lead and learn from team members across client engagements and internal initiatives

· Conducts analyses to support the development of budgets, project plans, operational and risk assessments, and organizational structures that improve the efficiency and effectiveness of government agencies

· Builds and shares knowledge to contribute to our team and firm’s capabilities including in areas of health sciences, strategy, innovation, operational excellence, change management, and risk management

V. Deliverables:

Conduct vulnerability scans on new and existing software, applications, and components to help define, identify, classify and prioritize vulnerabilities affecting CDC systems. These scans shall proactively identify exploitable vulnerabilities, confirm remediation of identified vulnerabilities, assist with investigating possible system compromise, and contribute to certifying or recertifying a system for an Authority to Operate (ATO).

Scan/Review (2 days before) Remediation (1 week after)

Planner tasks submitted to COR one day before assessment is started

By end of contract

VI. Special Considerations

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

In order 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 a 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 are 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

Requirements for Information Security and/or Physical Access Security Information Security Requirements

1. Baseline Security Requirements

1) Applicability. The requirements herein apply whether the entire contract or order (hereafter “contract”), or portion thereof, includes either or both of the following:

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

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

2) Safeguarding Information and Information Systems. In accordance with the Federal Information Processing Standards Publication (FIPS)199, Standards for Security Categorization of Federal Information and Information Systems, the Contractor (and/or any subcontractor) shall:

a. Protect government information and information systems in order to ensure:

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

b. Provide security for any Contractor systems, and information contained therein, connected to an HHS network or operated by the Contractor on behalf of HHS regardless of location. In addition, if new or unanticipated threats or hazards are discovered by either the agency or contractor, or if existing safeguards have ceased to function, the discoverer shall immediately, within one (1) hour or less, bring the situation to the attention of the other party.

c. Adopt and implement the policies, procedures, controls, and standards required by the HHS 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 the HHS Information Security Program security requirements, outlined in the HHS Information Security and Privacy Policy (IS2P), by contacting the CO/COR or emailing fisma@hhs.gov.

d. Comply with the Privacy Act requirements and tailor FAR clauses as needed..

3) Information Security Categorization. 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, Appendix C, and based on information provided by the ISSO, CISO, or other security representative, the risk level for each Security Objective and the Overall Risk Level, which is the highest watermark of the three factors (Confidentiality, Integrity, and Availability) of the information or information system are the following:

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 [ ] Yes PII Personally Identifiable Information (PII). Per the Office of Management and Budget (OMB) Circular A-130, “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.

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

4) 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. All sensitive information that has been identified as CUI by a regulation or statute, handled by this solicitation/contract, shall be:

a. marked appropriately;

b. disclosed to authorized personnel on a Need-To-Know basis;

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

d. returned to HHS control, destroyed when no longer needed, or held until otherwise directed. Destruction of information and/or data shall be accomplished in accordance with NIST SP 800-88, Guidelines for Media Sanitization.

5) 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) shall 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.

6) 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 shall be used only for the purpose of carrying out the provisions of this contract and shall 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 shall ensure that all work performed by its employees and subcontractors shall 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 shall 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 shall be protected in accordance with HHS and CDC policies. Unauthorized disclosure of information will be subject to the HHS/CDC sanction policies and/or governed by the following laws and regulations:

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

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

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

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

8) 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 shall 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.

9) Contract Documentation. The Contractor shall use provided templates, policies, forms and other agency documents to comply with contract deliverables as appropriate.

10) Standard for Encryption. The Contractor (and/or any subcontractor) shall:

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

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

c. Secure all devices (i.e.: desktops, laptops, mobile devices, etc.) that store and process government information and ensure devices meet HHS and CDC-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).

d. 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 shall provide a written copy of the validation documentation to the COR and ISSO within 30 days of contract award.

e. 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 shall be provided to the COR upon request and at the conclusion of the contract.

11) Contractor Non-Disclosure Agreement (NDA). Each Contractor (and/or any subcontractor) employee having access to non-public government information under this contract shall complete the CDC non-disclosure agreement. A copy of each signed and witnessed NDA shall be submitted to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition.

12) Privacy Threshold Analysis (PTA)/Privacy Impact Assessment (PIA) – The Contractor shall assist the CDC Senior Official for Privacy (SOP) or designee with conducting a PTA for the information system and/or information handled under this contract to determine whether or not a full PIA needs to be completed.

a. If the results of the PTA show that a full PIA is needed, the Contractor shall assist the CDC SOP or designee with completing a PIA for the system or information within 30 days 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.

b. The Contractor shall assist the CDC 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.

Training

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

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

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

Rules of Behavior

1) The Contractor (and/or any subcontractor) shall ensure that all employees performing on the contract comply with the HHS Information Technology General Rules of Behavior, and any CDC-specific rules, as applicable.

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

Incident Response The Contractor (and/or any subcontractor) shall respond to all alerts/Indicators of Compromise (IOCs) provided by HHS Computer Security Incident Response Center (CSIRC)/CDC CSIRT 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” .

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

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

2) 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 shall send CDC approved notifications to affected individuals following CDC’s designated process.

3) Report all suspected and confirmed information security and privacy incidents and breaches to the CDC’s Computer Security Incident Response Team (CSIRT) [CSIRT@CDC.gov], COR, CO, CDC 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 CDC 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 shall:

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

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

c. encrypt sensitive information in attachments to email, media, etc.

4) Comply with OMB M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information HHS and CDC’s incident response policies when handling PII breaches.

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

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: Not Applicable or Level 1: Non-sensitive, depending on roles and responsibilities.

Homeland Security Presidential Directive (HSPD)-12 The Contractor (and/or any subcontractor) and its employees shall comply with Homeland Security Presidential Directive (HSPD)-12, Policy for a Common Identification Standard for Federal Employees and Contractors; OMB M-05-24; FIPS 201, Personal Identity Verification (PIV) of Federal Employees and Contractors; HHS HSPD-12 policy; and Executive Order 13467, Part 1 §1.2. For additional information, see HSPD-12 policy at: https://www.dhs.gov/homeland-security-presidential-directive-12) Roster. The Contractor (and/or any subcontractor) shall 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 shall be submitted to the COR and/or CO within the CDC Specified timeline of the effective date of this contract. Any revisions to the roster as a result of staffing changes shall be submitted within 7 days of the 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 shall provide a position description and the Government will determine the appropriate suitability level.

Contract Initiation and Expiration

1) General Security Requirements. The Contractor (and/or any subcontractor) shall comply with information security and privacy requirements, Enterprise Performance Life Cycle (EPLC) processes, HHS 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 shall follow the CDC EPLC framework and methodology and in accordance with the HHS Contract Closeout Guide (2012). CDC EPLC requirements may be located here: https://www2a.CDC.gov/CDCup/library/other/eplc.htm.

2) System Documentation. Contractors (and/or any subcontractors) must follow and adhere to NIST SP 800-64, Security Considerations in the System Development Life Cycle, 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.

3) Sanitization of Government Files and Information. As part of contract closeout and at expiration of the contract, the Contractor (and/or any subcontractor) shall 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.

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

5) Contractor Responsibilities Upon Physical Completion of the Contract. The contractor (and/or any subcontractors) shall 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 shall 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 HHS and/or CDC policies.

6) The Contractor (and/or any subcontractor) shall perform and document the actions identified in the…