D-ISSO Clauses.pdf
PDF 110 KB Posted
- Solicitation number
- 75N95023Q00061
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ARTICLE H.51.1. INFORMATION SECURITY AND/OR PHYSICAL ACCESS SECURITY
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:
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.
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, Contractor Non-Disclosure Agreement 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:
mailto:fisma@hhs.gov
Confidentiality: [ ] Low [ X ] Moderate [ ] High Integrity: [ ] Low [ X ] Moderate [ ] High Availability: [ X] Low [ ] Moderate [ ] High Overall Risk Level: [ ] Low [ X ] 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
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 ] N/A [ ] Low [ ] Moderate [ ] High
5. Protection of Sensitive Information- For security purposes, information is or may be sensitive because it requires security to protect its confidentiality, integrity, and/or availability. The Contractor (and/or any subcontractor) shall protect all government information that is or may be sensitive in accordance with OMB Memorandum M-06-16, Protection of Sensitive Agency Information by securing it with a FIPS 140-2 validated solution.
ARTICLE H.51.1. INFORMATION SECURITY AND/OR PHYSICAL ACCESS SECURITY
File details come from the government source that posted it. Updated .