SOW CADCA.pdf

STATEMENT OF WORK

Continuation of Specialized Professional and Program Support for the Drug-Free Communities Branch

Background

The Drug-Free Communities (DFC) Program has been a central component of our nation’s drug use reduction strategy since 1998. The premise of the DFC program is simple: communities around the country must be organized and equipped to deal with their individual substance misuse problems in a comprehensive and coordinated manner. The program has grown from $10 million in 1998 to $100 million in 2019, a testament to the program’s popularity and bi-partisan support.

The DFC Program is directed by the White House Office of the National Drug Control Policy (ONDCP) and is currently managed by CDC in the National Center for Injury Prevention (NCIPC), Division of Overdose Prevention (DOP). DFC provides grants to approximately 750 community coalitions to achieve 2 main goals: 1) establish and strengthen collaboration among communities and 2) reduce substance abuse among youth, focusing on alcohol, tobacco, marijuana, prescription drugs, and other drugs.

Project Objective: The purpose of this contract is to secure specialized professional and training services from the Community Anti-Drug Coalitions of America (CADCA), a critical partner of the DFC Program.

Scope of Work: The contractor shall develop and coordinate in-person and virtual opportunities to engage Drug-Free Communities (DFC) grant recipients and youth leaders working in youth substance use prevention. These opportunities will include specific trainings, tools, and materials that will assist in implementing prevention strategies at the state and local level.

Description of Work:

Task 1: Communication with CDC Within 14 business days after the award of the task order, the Contractor shall attend a virtual kick off meeting with the CDC SMEs, Contracting Officer’s Representative (COR), and other appropriate CDC staff to discuss the project, related tasks for each phase of the project, roles and responsibilities, timelines and deliverables, and communication and reporting requirements. Within one week of the kickoff meeting, the Contractor shall prepare a one to two-page overview of the project, its objectives, proposed approach, and timeline, and include notes documenting key decisions made at the meeting and critical upcoming action items.

1.2: The Contractor shall maintain ongoing communications with the COR through conducting monthly conference calls to provide updates, discuss progress, and plan future activities. The frequency of project calls can be adjusted through mutual agreement between the Contractor and CDC. The Contractor shall submit the agenda for each scheduled call to the COR 48 hours before the call. Within 10 business days after the calls and/or meetings the Contractor shall provide a brief summary of notes and action items to the COR.

1.3: In addition, the Contractor shall provide bi-monthly progress reports (not to exceed 4 pages) that contain, at a minimum:

a) progress made during the two-month period and deliverables submitted; b) problems encountered during the month and how addressed; c) work planned for next two-month period; d) timeline or funding issues to be addressed; and e) actions required by the Contractor and/or COR.

Task 2: National Community of Practice The Contractor shall develop trainings for the core competencies listed below and conduct up to three (3) DFC Communities of Practice (CoP) workshops to train community leaders on engaging with and/or implementing youth prevention strategies at the state and local level. CADCA must work with CDC to identify CDC Subject Matter Experts to help develop and/or participate on CoPs with topic areas relevant to the DFC Grant Program.

Core Competencies must include the following areas of interest:

• Public health/Health promotion and health behavior

• Educating about Policy

• Equity

• Technology & Prevention

• Leadership

• Collaboration/Networking within the Field

• Strategic Communication

• Sustainability

• Change Management

• Non-Federal Funding

• Evidence Informed Interventions

2.2: The Contractor shall also provide a report of recommendations and findings from the CoPs with a particular focus on strategies for youth engagement and involvement with youth substance use prevention activities. The report must be in MS Word and no more than 5 pages. A draft report and final report shall be provided to CDC.

Task 3: DFC “What’s Trending” In collaboration with CDC, the Contractor shall design and produce two “What’s Trending” informational resource infographics for prevention practitioners and coalitions members to become aware of the latest trends in the field. The infographics should reflect emerging issues and be relevant to DFC youth prevention topic areas. Topic areas must be approved by CDC.

The infographics must be 1-page front and back and 508 compliant. The Contractor must provide first and second draft of each infographic in MS Word format for COR to review and approval. The final infographics must be in MS Word and PDF formats.

3.2: The Contractor must also submit a Communications Plan for how the infographics will be shared among DFC coalitions.

Task 4: 2025 CADCA National Forum – February 3-6, 2025 in Washington, DC 4.1: CADCA shall work with CDC to create and deliver three customized training sessions and a Meet and Greet at the 2025 CADCA National Leadership Forum.

• CADCA shall work with CDC to ensure content of customized training is aligned with learning objectives, audience skills and needs, and goals, and that training is not duplicative with other offerings. CADCA shall ensure the training needs and interests of the intended audience are met and delivered in a manner and level that ensures a great learning opportunity for participants.

• CADCA shall ensure the trainings focus on strengthening collaborations with coalitions, alcohol, and other drug abuse and intervention strategies.

• CADCA must provide CDC access to training rooms, including all room setup, room support as needed, and other typically standard facilities including audio / visual and any other materials needed at the 2024 CADCA National Leadership Forum.

• CADCA will provide CDC with an exhibit table in the Exhibit Hall and a dedicated or shared office space.

• No more than 40 CDC participants will attend.

Task 5: 2025 CADCA Mid-Year Training Institute – July 20-24, 2025 in Nashville, TN 5.1: CADCA shall work with CDC to create and deliver three customized training sessions and a Meet and Greet at the 2025 CADCA Mid-Year Training Institutes.

• CADCA shall work with CDC to ensure content of customized training is aligned with learning objectives, audience skills and needs, and goals, and that training is not duplicative with other offerings. CADCA shall ensure the training needs and interests of the intended audience are met and delivered in a manner and level that ensures a great learning opportunity for participants.

• CADCA shall ensure the trainings focus on strengthening collaborations with coalitions, alcohol, and other drug abuse and intervention strategies.

• CADCA must provide CDC access to training rooms, including all room setup, room support as needed, and other typically standard facilities including audio / visual and any other materials needed at the 2023 CADCA Mid-Year Training Institute.

• CADCA will provide CDC with an exhibit table in the Exhibit Hall and a dedicated or shared office space.

• No more than 40 CDC participants will attend.

Period of Performance: September 22, 2024 – September 21, 2025

Place of Performance: 100% of the work will be performed at the Contractor’s facility.

CADCA

625 Slaters Lane Suite 300 Alexandria, VA 22314

Travel: None

Deliverables:

Type Description Due Date Deliver To 1 Attend Kickoff Meeting 14 Days Post Award COR, SME 1 Project Overview Within one week of Kickoff Meeting COR, SME

1.2 Meeting Agenda and Notes

Agenda 2 business days before each call; Notes within 10 business days after each call

COR, SME

1.3 Bi-Monthly Progress Report

By the 10th day of the month (reporting on previous two- month period)

COR, SME

Start Conducting up to 3 Communities of Practice (CoP)

Ongoing Starting 3 Months Post Award

2.2 Draft CoP Report of Findings 10 Months Post Award COR, SME

2.2 Final CoP Report of Findings 11 Months Post Award COR, SME 3 Finalize topic areas for the Infographics 2 Months Post Award COR, SME 3 Draft of first ‘What’s Trending” Infographics 3 Months Post Award COR, SME

Minimum Vendor Qualifications: A minimum of a bachelor’s degree is required for all staff.

3 Draft of second ‘What’s Trending” Infographics 6 Months Post Award COR, SME 3 Final ‘What’s Trending” Infographics 11 Months Post Award COR, SME

3.2 ‘What’s Trending” Infographics Communication Plan 1 Months Post Award

COR, SME

4.1 Provide Potential Topic Areas for CDC National Forum Sessions

Within 2 Month Post Award COR, SME

4.1 Determine Draft Content for CDC National Forum Sessions

3 Months Post Award COR, SME

4.1

Final Content for CDC National Forum Sessions to include location/times of session, A/V needs finalized, Exhibit Table, and Office Space

4 Months Post Award COR, SME

4.1 Conduct Training at the 2025 CADCA National Forum

5 Months Post Award COR, SME

5.1 Provide Potential Topic Areas for CDC Mid-Year Sessions

Within 7 Month Post Award COR, SME

5.1 Determine Draft Content for CDC Mid-Year Sessions

8 Months Post Award COR, SME

5.1

Final Content for CDC Mid-Year Sessions to include location/times of session, A/V needs finalized, Exhibit Table, and Office Space

9 Months Post Award COR, SME

5.1 Conduct Training at the 2025 CADCA Mid-Year Training Institute

10 Months Post Award COR, SME

Desired Outcomes SLA Performance Standard (completeness, cost, reliability, accuracy, timeliness, quality)

Acceptable Quality Level (AQL) Monitoring Method (Quality Assurance Surveillance Plan/QASP)

Incentives/ Disincentives

Perform all tasks listed in the SOW, specifically tasks outlined in Description of Work: Tasks 1 – 3.

Quality and timeliness of tasks

100% compliance with CDC requirements.

Work completed within a timely manner, at acceptable quality, and with a professional demeanor.

3) No more than 2 documented complaints of performance within a one-month period.

1) COR review and acceptance

2) Date of delivery

1) Favorable or Unfavorable Performance Evaluation

2) Performance is considered in determining whether to exercise the option periods.

3) Repeated complaints will be elevated for higher level resolution (senior management).

Monthly Conference Call

Occurs at regularly scheduled times

Contractor is prepared to discuss relevant tasks, work performance, is responsive to performance issues, and documents meetings as described in SOW.

1) 100% review of work plan and agendas.

2) Unacceptable or missed conference meetings will be documented as customer complaints.

1) Favorable or Unfavorable Performance Evaluation

2) Performance is considered in determining whether to exercise the option periods.

Reporting Meeting Notes & Bi-Monthly Reports

Quality and timeliness of notes/reports

1) Meeting Notes – Delivered within 5 days after meeting.

2) Bi-Monthly Reports – Delivered by the 10th calendar day every other month.

3) Contains appropriate content as outlined in the SOW.

1) 100% review of delivered reports.

2) Unacceptable bi-monthly conference reports will be documented as customer complaints.

1) Favorable or Unfavorable Performance Evaluation

Well-designed and effective CoPs.

Completeness, timeliness, and quality of CoPs.

1) 100% compliance with CDC requirements

2) Successful CoPs and reports.

1) COR review and acceptance.

2) Documented user complaints

1) Favorable or Unfavorable Performance Evaluation

2) Repeated complaints will be elevated for higher

Government Furnished Property

The Government will not provide furnished materials, property, or office space for the Contractor.

Special Considerations

1. The contractor is prohibited from publishing, presenting, or disseminating results or information without the prior written approval of the COR and CDC SME.

2. All products developed under this task order shall become and remain the property of the Government.

3. The contractor must notify CDC in writing within 30 days of any staffing changes.

HHSAR Provision, 352.239-73: 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 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 level resolution (senior management).

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

In order to facilitate the Government's determination whether proposed EIT services meet applicable Section 508 accessibility standards, offerors must provide enough information to assist the Government in determining that the EIT services conform to Section 508 accessibility standards, including any underway remediation efforts addressing conformance issues.

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

References

INFORMATION SECURITY REQUIREMENTS

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) 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 http://hhs.gov/web/508 http://508.hhs.gov/ https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html disclosure, based on the security terms found in this contract, including means for protecting personal privacy and proprietary information;

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

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

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

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

e. Controlled Unclassified Information (CUI). Executive Order 13556 defines CUI as "information that laws, regulations, or Government-wide policies require to have safeguarding or dissemination controls, excluding classified information." The Contractor (and/or any subcontractor) must comply with Executive Order 13556, Controlled Unclassified Information, (implemented at 3 CFR, part 2002) when handling CUI. 32 C.F.R. 2002.4(aa) As implemented the term "handling" refers to "…any use of CUI, including but not limited to marking, safeguarding, transporting, disseminating, re-using, and disposing of the information." 81 Fed.

Reg. 63323. The requirements below apply only to nonfederal systems that process, store, or transmit CUI, or that provide security protection for such components. All sensitive information that has been identified as CUI by a regulation or statute, handled by this solicitation/contract, must be:

i. Marked appropriately;

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

iii. Protected in accordance with NIST SP 800-53, Security and Privacy Controls for

Information Systems and Organizations applicable baseline if handled by a Contractor system operated on behalf of the agency, or NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations if handled by internal Contractor system; and,

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

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

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

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

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

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

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

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

i. Information and Communications Technology (ICT). ICT products and services from prohibited entities/sources must not be used/acquired in compliance with Public Law 115- 232, Section 889 Parts A and B, FAR 4.21, FAR 52.204.23, FAR 52.204.24, and FAR

52.204.25. The Contractor (and/or any subcontractor) must notify the government if they identify prohibited ICT products and/or services are used during the contract performance.

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

Consult HHS/CDC Policy for Internet and Email Security for additional information. According to the CDC Web policy, all CDC web content must reside on a CDC.gov domain and must be hosted on CDC or CDC-authorized information systems .

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

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

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

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

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

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

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

m. Contractor Non-Disclosure Agreement (NDA). Each Contractor (and/or any subcontractor) employee having access to non-public government information under this contract must complete the CDC non-disclosure agreement. [inserted information/link should be cited here], as applicable. Contractors (and/or subcontractors) must submit a copy of each signed and witnessed NDA to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition.

2. Training Requirements:

a. Mandatory Training for All Contractor Staff. All Contractor (and/or any subcontractor) employees assigned to work on this contract must complete the applicable CDC Contractor Information Security Awareness, Privacy, and Records Management training (provided upon contract award) before performing any work under this contract. Thereafter, the employees must complete Information 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 http://csrc.nist.gov/publications/ 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 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)29, an incident is "an occurrence that (1) actually or imminently

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

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

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

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

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

iv. NOT notify affected individuals unless so instructed by the Contracting Officer or designated representative. If instructed by the Contracting Officer or representative, the Contractor must send approved notifications to affected individuals within 24 hours using the letter template found on OCISO/CDC Standard for Responding to Breaches of Personally Identifiable Information (PII) v2.1.

v. Report all suspected and confirmed information security and privacy incidents and breaches to the CSPO Incident Response Team (IRT) at csirt@cdc.gov or telephone at 866-655-2245, 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;

30 Standard is available at: https://cdc.sharepoint.com/teams/OCIO-CSPO- PUBDOCS/Standards/CSPO%20Responding%20to%20Breaches%20of%20Personally%20Identifiable%20Information.pdf https://intranet.cdc.gov/ocio/docs/information-systems-security/PIIIncidentResponseStandard.pdf https://intranet.cdc.gov/ocio/docs/information-systems-security/PIIIncidentResponseStandard.pdf https://cdc.sharepoint.com/teams/OCIO-CSPO-PUBDOCS/Standards/CSPO%20Responding%20to%20Breaches%20of%20Personally%20Identifiable%20Information.pdf https://cdc.sharepoint.com/teams/OCIO-CSPO-PUBDOCS/Standards/CSPO%20Responding%20to%20Breaches%20of%20Personally%20Identifiable%20Information.pdf

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.

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

7. Roster:

The Contractor (and/or any subcontractor) must submit a roster by name, position, e-mail address, phone number and responsibility, of all staff working under this acquisition where the Contractor will develop, have the ability to access, or host and/or maintain a government information system(s). The roster must be submitted to the COR and/or CO by the effective date of this contract. Any revisions to the roster as a result of staffing changes must be submitted immediately upon 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 Security and Privacy Officer (previously referred to as ISSO) before an employee stops working under this contract.

e. Contractor Responsibilities upon Physical Completion of the Contract. The Contractor (and/or any subcontractors) must return all government information and IT resources (i.e., government information in non-government-owned systems, media, and backup systems) acquired during the term of this contract to the CO and/or COR. Additionally, the Contractor must provide a certification that all government information has been properly sanitized and purged from Contractor-owned systems, including backup systems and media used during contract performance, in accordance with HHS and/or CDC policies.

f. The Contractor (and/or any subcontractor) must perform and document the actions identified in the Contractor Employee Separation Checklist when an employee terminates work under this contract within 2 hours 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 policies and must not dispose of any records unless authorized by CDC/ [CDC Component].

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

10. High Value Asset (HVA):

If a system is identified as HVA,31 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.

EVALUATION FACTORS

Evaluation Criteria Maximum Points

Technical Approach 45 Similar Experience 45 Price 10 Total Points Possible: 100

Each criterion will be evaluated according to the extent that it reflects a clear understanding of the subject areas to be accomplished and on the soundness, practicality, and feasibility of the contractor’s transition-in plan and technical approach for providing the services required for this task order.

Technical Approach:

The Offeror is to provide a discussion of their technical approach for providing the services required for this 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 task order. Provide information reflecting experience of assigned staff, including a detailed resume, or curriculum vitae (CV) of each candidate. The Offeror shall specifically address aspects such as technical understanding, methodology and approach, along with the sub-factors listed below:

a. Provide a detailed and comprehensive statement of the problem, scope, and purpose of the project to demonstrate complete understanding of the intent and requirements of the contract and potential problems that may be encountered.

b. Describe the proposed technical approach to comply with each of the requirements specified in the task order statement of work. The proposal must be consistent with the stated goals and objectives. The proposed approach must ensure the achievement of timely and acceptable performance and will include a milestone and/or phasing charts to illustrate a logical sequence of proposed events.

c. Describe a plan that includes solutions for overcoming difficulties involved with performing the work requirements.

Similar Experience:

The Offeror shall provide a description of three (3) projects completed within the past three years that clearly demonstrates the Offeror’s experience in performing projects of similar scope, size and complexity to the requirements described in the SOW. The following information shall be provided for each project reference:

a. Contract number, customer/agency name and contract title;

b. Brief narrative description of the work performed for each of those contracts, including a discussion of any problems encountered/corrective actions and significant accomplishments;

c. Dollar value, contract type, period of performance, place of performance, and the number and types of personnel used in the performance of the contract; and

d. Name, address, and phone number of at least two (2) customer contacts (Contracting Officer and COR) for each of the identified contracts.

Price Evaluation:

A price analysis of the quote will be conducted to determine the reasonableness of the Offeror’s price.

Program Points of Contact:

Contracting Officer’s Representative (COR):

Christi Jones

NCIPC/DOP/DFC

Centers for Disease Control and Prevention 4770 Buford Hwy, MS S106-2 Atlanta, GA 30341 Phone: 770-488-3703 Email: BUV3@cdc.gov mailto:BUV3@cdc.gov

Information Security Requirements