RFQ75D301-19-Q-71156.doc

75D301-19-Q-71156

REQUEST FOR QUOTATIONS

(THIS IS NOT AN ORDER)

THIS RFQ

PAGE OF PAGES

1. REQUEST NO.

75D301-19-Q-71156

2. DATE ISSUED

9/26/2019

3. REQUISITION/PURCHASE REQUEST NO.

00HCPNCD-2020-34977

4. CERT. FOR NAT. DEF.

UNDER BDSA REG. 2

AND/OR DMS REG. 1

RATING

5a. ISSUED BY

Centers for Disease Control and Prevention (CDC)

Office of Acquisition Services (OAS)

2900 Woodcock Blvd, MS TCU-4

Atlanta GA 303414004

6. DELIVERY BY (Date) See Sectiion B, Line items

5b. FOR INFORMATION CALL (No collect calls)

DIGITAL SCIENCE & RESEARCH SOLUTIONS INC.

625 MASSACHUSETTS AVE FL 2

10. PLEASE FURNISH QUOTATIONS TO

THE ISSUING OFFICE IN BLOCK 5a ON

OR BEFORE CLOSE OF BUSINESS (Date)

10/3/2019@2pm EST IMPORTANT: This is a request for information, and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or services. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this Request for Quotations must be completed by the quoter.

11. SCHEDULE (Include applicable Federal, State and local taxes)

ITEM NO.

(a)

SUPPLIES/SERVICES

(b)

QUANTITY

(c)

UNIT

(d)

UNIT PRICE

(e)

AMOUNT

(f)

“See Continuation Page”

b. 20 CALENDAR DAYS

c. 30 CALENDAR DAYS

d. CALENDAR DAYS

NOTE: Additional provisions and representations

SIGN QUOTATION

15. DATE OF

QUOTATION

a. NAME OF QUOTER

c. COUNTY

AREA CODE

AUTHORIZED FOR LOCAL REPRODUCTION

STANDARD FORM 18 (REV. 6-95)

Previous edition not usable

Prescribed by GSA

FAR (48 CFR) 53.215-1(a)

SECTION B - Line Items

Base Period - Year 1 Items

IAW/the Statement of Work (SOW) in Section C below, provide Altmetric Explorer for Institutions (one year subscription) 11/1/2019 - 10/31/2020. All CDC Users.

Custodial Account #: 40115 1 Each

IAW/the SOW in Section C below, provide Altmetric Journal Badges for MMWR, EIS, and PCD. 11/1/19 - 10/31/20.

3 Each

Total Year 1

Option 1 - Year 2 Items:

IAW/the SOW in Section C below, provide Altmetric Explorer for Institutions (one year subscription) 11/1/2020 - 10/31/2021. All CDC Users.

1 Each

IAW/the SOW in Section C below, provide Altmetric Journal Badges for MMWR, EIS, and PCD. 11/1/20 - 10/31/21.

3 Each

Total Year 2

Option 2 - Year 3 Items:

IAW/the SOW in Section C below, provide Altmetric Explorer for Institutions (one year subscription) 11/1/2021 - 10/31/2022. All CDC Users.

1 Each

IAW/the SOW in Section C below, provide Altmetric Journal Badges for MMWR, EIS, and PCD. 11/1/21 - 10/31/22.

3 Each

Total Year 3

NOTES:

1. Award on the basis of firm-fixed-price is being contemplated. Payments will be made IAW/FAR Clause 52-212-4(i), Payments.

2. To ensure payment, invoice must reference the PO# ________________, DUNS, and Tax ID Number. Invoice/Payment information: for inquiring about payment status contact ocfoservicedesk@cdc.gov or call 678-475-4510.

3. Send Invoices to FAX: 404-638-5324 or Email at fmoapinv@cdc.gov.

4. Vendor POC:

5. CDC PoC:

SECTION C- STATEMENT OF WORK

Title: Altmetrics Services – Stephen B. Thacker CDC Library

Period of Performance: Nov 1, 2019 – Oct 31, 2022

I.

DESCRIPTION AND BACKGROUND

The Centers for Disease Control and Prevention (CDC), headquartered in Atlanta, GA, is an agency of the Department of Health and Human Services (HHS). CDC is the leading public health agency responsible for promoting health and quality of life by preventing and controlling disease, injury and disability. CDC works with partners throughout the nation and the world to develop and apply disease prevention and control, environmental health, and health promotion and education activities that are designed to improve the health of the people.

The CDC Library Science Branch supports and enables the scientific work of the agency. CDC requires library services to support its broad research agenda and its commitment to excellence in science. Credible, timely information is fundamental to improving health research, health care, and quality of life. It is central to responding to public health emergencies, promoting healthy behaviors and disease prevention, and providing informed responses to public health issues.

II.

PURPOSE

The Stephen B. Thacker CDC Library has been subscribing to an altmetrics product on behalf of all CDC users since 2015. This product allows the library to provide information to CDC scientists and leadership about the social media impact of scientific publications authored by CDC users, as well as being able to follow the social media activity for any article that is being tracked by the altmetrics product, whether or not it is has a CDC author. This information provides valuable feedback to CDC scientists and leaders about who is talking about CDC research in the online media. Types of online media tracked by the current altmetrics product includes Facebook, Twitter, Reddit, selected blogs, diverse news sources, Google+, Wikipedia and a number of other social media products and sources. The altmetrics product provides a search interface for the altmetrics data with many search and filtering options which allow users to explore the data in a number of different ways. The CDC library regularly supplies a list of CDC publications and authors to the vendor which provides CDC users with the ability to search a CDC specific subset of the altmetrics database.

This requirement will consist of a continuation of the currently subscribed altmetrics services. It will also include provision for three altmetrics “Publisher Badges” for the three CDC journals – Mortality and Morbidity Weekly Reports (MMWR), Emerging Infectious Diseases (EID) and Preventing Chronic Disease (PCD). The publisher badges provide both the ability to use the altmetrics graphical badge on the publication’s website, but also additional services customized for the use of journal publishers.

III.

SCOPE OF WORK

This requirement will provide a continuation of current altmetrics services and the publisher badges for one or more one year periods as outlined below. This requirement will provide continued access to altmetrics software and altmetrics data as provided by our current vendor. These services will include access to a CDC-specific, customized instance of the altmetrics database, including regular updating of the CDC-specific data on an at least weekly basis, and programmatic access via an API. The vendor will provide user support for the product in a timely manner, including advice, training and assistance in implementation.

The altmetrics product provided should include article-level data for all published journal articles for which social media mentions have been identified for at least the last seven years (starting by 2012 or earlier). This means that any article, published at any date, if it was mentioned in a publicly available social media outlet within the last seven years would be included in the dataset. Altmetrics data for scholarly articles are not limited to CDC-authored articles, but include any published scholarly work with social media mentions. Social media mentions in this context must include mentions in the following list of classes of online media and specific platforms:

· news outlets (both national and international, in English and other languages and additional news sources available upon request)

· blogs (scholarly, scientific, economics, and popular, and the capability to add additional blogs to tracking upon request)

· Twitter (including geographic data for tweeters and number of followers per tweeter)

· Facebook (public postings)

· Policy documents from multiple countries and agencies and the ability to add additional sources upon request

· Weibo

· Google+

· Wikipedia

· Reddit

· Pinterest

· Videos (including YouTube)

· LinkedIn

· Peer Review websites (e.g.Pubpeer)

· Research highlight platforms (e.g. F1000)

The data shall also include article level citation counts from one or more large citation databases, such as the Scopus database, or an equivalent database. In addition to the actual counts for each category above, the data should include a composite score, which allows users to have and use a single composite attention score for each article, which encompasses all or most of the social media mentions listed above, which can be used to provide comparisons between articles. This can take the form of a weighted average or some other form, as long as the methodology used to generate the score is clearly documented and available to the users. A graphical representation of said composite score should also be available. Also, each of the social media mentions for a given article must be individually listed within the altmetrics user interface, and a direct link provided from the altmetrics user interface to the actual mention (tweet, Facebook or blog posting, etc.) in the appropriate native social media interface. The altmetrics web interface, for each included article, must also include a link to the actual article on the appropriate publisher platform.

Access to the altmetrics data should be provided through a searchable web-based user interface which is customizable by the library for CDC users, and to which access can be restricted to CDC users only by means of IP authentication or unique user logins. The library will provide the vendor with a list of IP address or ranges to be included. The user interface should allow searching for articles by multiple criteria, including at least, article title, author name, journal title, unique article identifiers (including PMID, DOI, ISSN and ISBN), unique author identifiers (including ORCID), and integrated PubMed query results. In addition, the interface should allow search limits or results filtering based on mentions in a specific class of social media or a specific platform, and/or mentions within a specific time period. And, the search results should be sortable by the total/composite score for each article and/or the date of first mention in the altmetrics dataset. It should also be possible to obtain journal-level results for any search query, i.e. results grouped by journal title, with summary statistics available for each journal in the grouping.

The altmetrics system should also be capable of providing CDC users access to a CDC-specific subset of data based on articles having CDC authors. The library will provide a file containing bibliographic data for approximately seven years’ worth of CDC authored articles, including identifying the CDC authors for each article, in a format to be mutually agreed upon between the library and the altmetrics provider. File formats could include RIS, HTML, and/or XML. Individual CDC authors will not be required to provide information about their publications to the altmetrics provider. This CDC data subset should include the ability to be searched by a browsable list of CDC authors with links to the altmetrics data for the articles written by those authors. The capability to provide searching or filtering based on the organizational affiliation of the CDC authors within CDC should also be available.

Additional capabilities of the web user interface should include both an anonymous institutional level login access and the option to create a personalized log-in and to create saved and automatic searches, including automated reporting via email of updates or changes to the database based on the saved searches or datasets created by the user. Datasets of all sizes and types, based on any of the queries described above, should be able to be exported from the interface to local files, either in Excel format, or readily converted to Excel spreadsheet format. This data should be able to include data from multiple articles. It should be possible for any user, affiliated with CDC or not, to place email alerts on any single article in the dataset, so that the user will be alerted by email to any new mentions of that article within the altmetrics dataset.

The altmetrics user interface should provide as close to real-time tracking of social media and other online mentions as possible. Users should be able to view precisely which articles are receiving online attention in a given time-span and said data can be filtered based on user-specified criteria.

IV. TASKS (Requirements) TO BE PERFORMED

1. Task 1 – Altmetrics product - institutional access REQUIRED

a. Provide access to the altmetrics institutional product for CDC users connecting from the designated range of CDC IP addresses.

b. Provide access to the CDC-specific data provided by the library to allow customization of the product for CDC users, included the ability of users to create personal accounts to track specific subsets of the available data.

c. Provide data processing services to import CDC-specific data provided by the library into the altmetrics database on at least a monthly basis.

d. Provide technical support and training for CDC library staff and CDC users in the functionality and use of the altmetrics institutional product.

2. Task 2 – Publisher Badges REQUIRED

a. Provide access and support for three (3) altmetrics Publisher Badges, to be used by three CDC publications: Mortality and Morbidity Weekly Reports (MMWR), Emerging Infectious Diseases (EID) and Preventing Chronic Disease (PCD).

V.

GOVERNMENT FURNISHED MATERIALS

N/A

VI.

PERIOD OF PERFORMANCE

Base: Altmetrics Web-based Interface and Publisher Badges

Nov 1, 2019 – Oct 31, 2020

Option One: Altmetrics Web-based Interface and Publisher Badges Nov 1, 2020 – Oct 31, 2021

Option Two: Altmetrics Web-based Interface and Publisher Badges Nov 1, 2021 – Oct 31, 2022

VII.

PLACE OF PERFORMANCE

The work will be performed at the vendor’s site or sites, with the possible (optional) exception of on-site training, should that be arranged.

VIII.

DELIVERABLES/REPORTING SCHEDULE

The vendor will provide the CDC Library with the necessary access to the altmetrics service, customized for CDC users, documentation, maintenance support, technical assistance and training necessary to ensure successful implementation and operation, including regularly incorporating CDC specific article and author data as provided by the CDC Library. The vendor will supply timely training in the use of the altmetrics products and updates. The vendor will provide CDC with the use of the publisher badges for the three CDC publications, Mortality and Morbidity Weekly Reports (MMWR), Emerging Infectious Diseases (EID) and Preventing Chronic Disease (PCD).

IX.

TRAVEL

No travel is explicitly required by this statement of work. Please see section VII. Place of Performance.

X.

SPECIAL REQUIREMENTS: INFORMATION TECHNOLOGY, SECUIRTY AND PRIVACY

A. 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) employee 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:

Confidentiality:

[X] Low [ ] Moderate [ ] High

Integrity:

[X] Low [ ] Moderate [ ] High

Availability:

[X] Low [ ] Moderate [ ] High

Overall Risk Level:

[X] Low [ ] Moderate [ ] High

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

4) 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

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

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

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

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

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

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

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

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 CDC Office of Chief Information Security Officer (OCISO).

12) 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, as applicable. 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.

13) 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 in accordance with HHS policy and OMB M-03-22, Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002.

a. 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 CDC SOP that a review is required based on a major change to the system (e.g., new uses of information collected, changes to the way information is shared or disclosed and for what purpose, or when new types of PII are collected that could introduce new or increased privacy risks), whichever comes first.

B. 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 Security Awareness Training (SAT), 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 (RBT) within 60 days of assuming their new responsibilities. Thereafter, they shall complete RBT at least annually in accordance with HHS policy and the HHS Role-Based Training (RBT) of Personnel with Significant Security Responsibilities Memorandum.

All HHS employees and contractors with SSR who have not completed the required training within the mandated timeframes shall have their user accounts disabled until they have met their RBT requirement.

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.

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

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

D. Incident Response

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.

OMB Memorandum M-17-12, “Preparing for and Responding to a Breach of Personally Identifiable Information” (03 January 2017) states:

Definition of an Incident:

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. Definition of a Breach:

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.

It further adds:

A breach is not limited to an occurrence where a person other than an authorized user potentially accesses PII by means of a network intrusion, a targeted attack that exploits website vulnerabilities, or an attack executed through an email message or attachment. A breach may also include the loss or theft of physical documents that include PII and portable electronic storage media that store PII, the inadvertent disclosure of PII on a public website, or an oral disclosure of PII to a person who is not authorized to receive that information. It may also include an authorized user accessing PII for any 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”.

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

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

2) 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 so as to avoid a secondary sensitive information incident with FIPS 140-2 validated encryption.

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

4) All contractors and subcontractors shall report a suspected or confirmed breach in any medium as soon as possible and no later than 1 hour of discovery, consistent with applicable CDC IT acquisitions guidance, HHS/CDC and incident management policy, and United States Computer Emergency Readiness Team (US-CERT) notification guidelines. To this end, the Contractor (and/or any subcontractor) shall respond to all alerts/Indicators of Compromise (IOCs) provided by HHS Computer Security Incident Response Center (CSIRC) or CDC Computer Incident Response Team (CSIRT) within 24 hours via email at csirt@cdc.gov or telephone at 866-655-2245, whether the response is positive or negative.

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

6) All contractors and subcontractors shall allow for an inspection, investigation, forensic analysis, and any other action necessary to ensure compliance with HHS/CDC Policy and the HHS/CDC Breach Response Plan and to assist with responding to a breach.

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

8) Identify roles and responsibilities, in accordance with HHS/CDC Breach Response Policy and the HHS/CDC Breach Response Plan. To this end, the Contractor shall NOT notify affected individuals unless and until so instructed by the Contracting Officer or designated representative. If so instructed by the Contracting Officer or representative, all notifications must be pre-approved by the appropriate CDC officials, consistent with HHS/CDC Breach Response Plan, and the Contractor shall then send CDC- approved notifications to affected individuals; and,

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

E. 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 requiring activity representative, in conjunction with Personnel Security, shall 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.

F. 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 by the effective date of this contract. Any revisions to the roster as a result of staffing changes shall 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 shall provide a position description and the Government will determine the appropriate suitability level.

G. 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 HHS EPLC framework and methodology and in accordance with the HHS Contract Closeout Guide (2012).

HHS EA requirements may be located here: https://www.hhs.gov/ocio/ea/documents/proplans.html

CDC EPC Requirements: 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 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 CDC Out-Processing Checklist (http://intranet.cdc.gov/od/hcrmo/pdfs/hr/Out_Processing_Checklist.pdf) when an employee terminates work under this contract. All documentation shall be made available to the CO and/or COR upon request.

H. Records Management and Retention

The Contractor (and/or any subcontractor) shall maintain all information in accordance with Executive Order 13556 -- Controlled Unclassified Information, National Archives and Records Administration (NARA) records retention policies and schedules and HHS policies and shall not dispose of any records unless authorized by HHS. In the event that a contractor (and/or any subcontractor) accidentally disposes of or destroys a record without proper authorization, it shall be documented and reported as an incident in accordance with HHS policies.

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

2) The Contractor (and/or any subcontractor) shall follow secure coding best practice requirements, as directed by United States Computer Emergency Readiness Team (US-CERT) specified standards and the Open Web Application Security Project (OWASP), that will limit system software vulnerability exploits.

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

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

5) The Contractor (and/or any subcontractor) shall remediate all risks or vulnerabilities immediately after the risks or vulnerabilities have been identified in the software.

XI.

CONTRACTING OFFICER’S REPRESENTATIVE (COR) INFORMATION

The Contracting Officer’s Representative (COR) for this procurement is:

Pamela Sedgwick-Barker

Stephen B Thacker CDC Library

Tom Harkin Global Communication Center, MS H19-1

1600 Clifton Road, NE

Atlanta, GA 30329

SECTION D- CLAUSES

FAR 52.252-2 -- Clauses Incorporated by Reference. (Feb 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address (es):

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/far1toc.htm http://www.hhs.gov/policies/hhsar/subpart301-1.html (End of Clause)

52.212-5 -- Contract Terms and Conditions Required to Implement Statutes or Executive Orders -- Commercial Items. (Aug 2019)

(a) The Contractor shall comply with the following Federal Acquisition Regulation (FAR) clauses, which are incorporated in this contract by reference, to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

(1) 52.203-19, Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (Jan 2017) (section 743 of Division E, Title VII, of the Consolidated and Further Continuing Appropriations Act 2015 (Pub. L. 113-235) and its successor provisions in subsequent appropriations acts (and as extended in continuing resolutions)).

(2) 52.204-23, Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab and

Other Covered Entities (Jul 2018) (Section 1634 of Pub. L. 115-91).

(3) 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment. (AUG 2019) (Section 89(a)(1)(A) of Pub. L. 115-232).

(4) 52.209-10, Prohibition on Contracting with Inverted Domestic Corporations (Nov 2015)

(5) 52.233-3, Protest After Award (AUG 1996) (31 U.S.C. 3553).

(6) 52.233-4, Applicable Law for Breach of Contract Claim (OCT 2004) (Public Laws 108-77, 108-78 (19 U.S.C. 3805 note)).

(b) The Contractor shall comply with the FAR clauses in this paragraph (b) that the contracting officer has indicated as being incorporated in this contract by reference to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

[Contracting Officer check as appropriate.]

X (1) 52.203-6, Restrictions on Subcontractor Sales to the Government (Sept 2006), with Alternate I (Oct 1995) (41 U.S.C. 4704 and 10 U.S.C. 2402).

X (2) 52.203-13, Contractor Code of Business Ethics and Conduct (Oct 2015) (41 U.S.C. 3509).

X (3) 52.203-15, Whistleblower Protections under the American Recovery and Reinvestment Act of 2009 (Jun 2010) (Section 1553 of Pub L. 111-5) (Applies to contracts funded by the American Recovery and Reinvestment Act of 2009).

___ (4) 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards (Oct 2018) (Pub. L. 109-282) (31 U.S.C. 6101 note).

___ (5) [Reserved]

___ (6) 52.204-14, Service Contract Reporting Requirements (Oct 2016) (Pub. L. 111-117, section 743 of Div. C).

___ (7) 52.204-15, Service Contract Reporting Requirements for Indefinite-Delivery Contracts (Oct 2016) (Pub. L. 111-117, section 743 of Div. C).

X (8) 52.209-6, Protecting the Government’s Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment (Oct 2015) (31 U.S.C. 6101 note).

___ (9) 52.209-9, Updates of Publicly Available Information Regarding Responsibility Matters (Oct 2018) (41 U.S.C. 2313).

___ (10) [Reserved]

___ (11) (i) 52.219-3, Notice of HUBZone Set-Aside or Sole-Source Award (Nov 2011) (15 U.S.C. 657a).

___ (ii) Alternate I (Nov 2011) of 52.219-3.

___ (12) (i) 52.219-4, Notice of Price Evaluation Preference for HUBZone Small Business Concerns (Oct 2014) (if the offeror elects to waive the preference, it shall so indicate in its offer)(15 U.S.C. 657a).

___ (ii) Alternate I (Jan 2011) of 52.219-4.

___ (13) [Reserved]

___ (14) (i) 52.219-6, Notice of Total Small Business Aside (Nov 2011) (15 U.S.C. 644).

___ (ii) Alternate I (Nov 2011).

___ (iii) Alternate II (Nov 2011).

___ (15) (i) 52.219-7, Notice of Partial Small Business Set-Aside (June 2003) (15 U.S.C. 644).

___ (ii) Alternate I (Oct 1995) of 52.219-7.

___ (iii) Alternate II (Mar 2004) of 52.219-7.

___ (16) 52.219-8, Utilization of Small Business Concerns (Oct 2018) (15 U.S.C. 637(d)(2) and (3)).

___ (17) (i) 52.219-9, Small Business Subcontracting Plan (Aug 2018) (15 U.S.C. 637 (d)(4)).

___ (ii) Alternate I (Nov 2016) of 52.219-9.

___ (iii) Alternate II (Nov 2016) of 52.219-9.

___ (iv) Alternate III (Nov 2016) of 52.219-9.

___ (v) Alternate IV (Aug 2018) of 52.219-9.

___ (18) 52.219-13, Notice of Set-Aside of Orders (Nov 2011) (15 U.S.C. 644(r)).

___ (19) 52.219-14, Limitations on Subcontracting (Jan 2017) (15 U.S.C. 637(a)(14)).

___ (20) 52.219-16, Liquidated Damages—Subcontracting Plan (Jan 1999) (15 U.S.C. 637(d)(4)(F)(i)).

___ (21) 52.219-27, Notice of Service-Disabled Veteran-Owned Small Business Set-Aside (Nov 2011) (15 U.S.C. 657f).

___ (22) 52.219-28, Post Award Small Business Program Rerepresentation (Jul 2013) (15 U.S.C. 632(a)(2)).

___ (23) 52.219-29, Notice of Set-Aside for, or Sole Source Award to, Economically Disadvantaged Women-Owned Small Business Concerns (Dec 2015) (15 U.S.C. 637(m)).

___ (24) 52.219-30, Notice of Set-Aside for, or Sole Source Award to, Women-Owned Small Business Concerns Eligible Under the Women-Owned Small Business Program (Dec 2015) (15 U.S.C. 637(m)).

X (25) 52.222-3, Convict Labor (June 2003) (E.O. 11755).

X (26) 52.222-19, Child Labor—Cooperation with Authorities and Remedies (Jan 2018) (E.O. 13126).

X (27) 52.222-21, Prohibition of Segregated Facilities (Apr 2015).

X (28) (i) 52.222-26, Equal Opportunity (Sep 2016) (E.O. 11246).

___ (ii) Alternate I (Feb 1999) of 52.222-26.

___ (29) (i) 52.222-35, Equal Opportunity for Veterans (Oct 2015) (38 U.S.C. 4212).

___ (ii) Alternate I (July 2014) of 52.222-35.

___ (30) (i) 52.222-36, Equal Opportunity for Workers with Disabilities (Jul 2014) (29 U.S.C. 793).

___ (ii) Alternate I (July 2014) of 52.222-36.

___ (31) 52.222-37, Employment Reports on Veterans (Feb 2016) (38 U.S.C. 4212).

___ (32) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010) (E.O. 13496).

X (33) (i) 52.222-50, Combating Trafficking in Persons (JAN 2019)

(22 U.S.C. chapter 78 and E.O. 13627).

___ (ii) Alternate I (Mar 2015) of 52.222-50, (22 U.S.C. chapter 78 and E.O. 13627).

___ (34) 52.222-54, Employment Eligibility Verification (Oct 2015). (E. O. 12989). (Not applicable to the acquisition of commercially available off-the-shelf items or certain other types of commercial items as prescribed in 22.1803.)

___ (35) (i) 52.223-9, Estimate of Percentage of Recovered Material Content for EPA-Designated Items (May 2008) (42 U.S.C. 6962(c)(3)(A)(ii)). (Not applicable to the acquisition of commercially available off-the-shelf items.)

___ (ii) Alternate I (May 2008) of 52.223-9 (42 U.S.C. 6962(i)(2)(C)).