Encryption Standards Sample Clauses

Encryption Standards. State Street will define in its Security Policy minimum standards for encryption methods and strength.

Encryption Standards. DST will define in its WISP minimum standards for data encryption. DST will employ approved industry standards designed to ensure that applicable requirements are implemented to protect the data. DST must: (i) encrypt Fund Confidential Information while in transit across public networks; (ii) encrypt Fund Confidential Information at rest on portable computing devices including laptops, electronic media (including removable media), and electronic storage devices. Use of removable media (floppy disk, recordable CD/DVD, USB drive, etc.) to store Fund Confidential Information must be prohibited without a business need and explicitly authorized internally. DST allows AES256 encryption on the mainframe disk controllers; however, encryption at the database layer is not implemented; and (iii) document procedures for managing encryption keys. Access to encryption keys must be restricted to named administrators governed by an access management program with at least annual review. Encryption keys must be protected in storage, and must not be stored on the same systems that perform the encryption / un-encryption.

Encryption Standards. Encryption algorithms that are publicly or commercially available, with key lengths sufficient to prevent commercially reasonable attempts to decrypt through brute force the encrypted information.

Encryption Standards. Stored Data Contractor’s and Subcontractors’ workstations and portable devices that are used to access, store, receive and/or transmit County PI, PHI or MI (e.g., mobile, wearables, tablets, thumb drives, external hard drives) require encryption (i.e., software and/or hardware) in accordance with: (a) Federal Information Processing Standard Publication (FIPS) 140-2, (b) National Institute of Standards and Technology (NIST) Special Publication 800-57 Recommendation for Key Management – Part 1: General (Revision 3), (c) NIST Special Publication 800-57 Recommendation for Key Management – Part 2: Best Practices for Key Management Organization; and (d) NIST Special Publication 800-111 Guide to Storage Encryption Technologies for End User Devices. Advanced Encryption Standard (AES) with cipher strength of 256-bit is minimally required. Contractor’s and Subcontractors’ use of remote servers (e.g., cloud storage, Software-as-a-Service or SaaS) for storage of County PI, PHI and/or MI will be subject to written pre-approval by the County’s Chief Executive Office.

Encryption Standards. Transmitted Data All transmitted (e.g., network) County PI, PHI and/or MI require encryption in accordance with: (a) NIST Special Publication 800-52 Guidelines for the Selection and Use of Transport Layer Security Implementations, and

Encryption Standards. The Software uses industry standard, strong encryption algorithms to encrypt Customer’s files and secure Customer’s Data that Customer backs-up with the Code42 Subscription Services prior to any transmission from the Device where the Customer Data resides. Customer Data remains encrypted at Code42’s Public Cloud secure data centers or within Customer’s Private Cloud or Managed Private Cloud, as elected by Customer. Unless another party, including Code42, is provided with Customer’s passwords and encryption keys, only Customer can decrypt and view its unencrypted Customer Data.

Encryption Standards. Contractor agrees to utilize strong encryption standards (AES/256 bit or greater) for the storage, transport, and transmission of County data for purposes of executing the agreement between the County and Contractor.

Encryption Standards. Transmitted Data

Encryption Standards. Stored Data

Encryption Standards. Stored Data Any Confidential Information at rest, wherever the information is stored, must be encrypted using Advanced Encryption Standard (AES), or equivalent protocol, with cipher strength of 256-bit, or equivalent. Contractor’s and sub-contractors’ use of remote servers (e.g. cloud storage, Software-as-a-Service or SaaS) for storage of County PI, PHI and/or MI shall be subject to written pre-approval by the County’s Chief Information Security Officer.