Common use of Standard for Encryption language Clause in Contracts

Standard for Encryption language. a. The Contractor shall use Federal Information processing Standard (FIPS) 140-2-compliant encryption (Security) Requirements for Cryptographic Module, as amended) to protect all instances of HHS sensitive information during storage and transmission. (Note: The Government has determined that HHS information under this contract is considered "sensitive" in accordance with FIPS 199, Standards for Security Categorization of Federal Information and Information Systems, dated February 2004).

Appears in 2 contracts

Samples: www.chainbridgetech.com, myacuity.com

AutoNDA by SimpleDocs

Standard for Encryption language. a. The Contractor shall use Federal Information processing Standard (FIPS) 140-2-2- compliant encryption (Security) Requirements for Cryptographic Module, as amended) to protect all instances of HHS sensitive information during storage and transmission. (Note: The Government has determined that HHS information under this contract is considered "sensitive" in accordance with FIPS 199, Standards for Security Categorization of Federal Information and Information Systems, dated February 2004).

Appears in 2 contracts

Samples: oamp.od.nih.gov, oamp.od.nih.gov

AutoNDA by SimpleDocs
Time is Money Join Law Insider Premium to draft better contracts faster.