Encryption at Rest Sample Clauses

The 'Encryption at Rest' clause requires that data stored on physical or virtual storage devices is encrypted to protect it from unauthorized access. This typically applies to sensitive information such as customer data, financial records, or proprietary business information, and may specify the use of certain encryption standards or technologies. By mandating encryption of stored data, the clause helps ensure data confidentiality and mitigates the risk of data breaches in the event of device theft or unauthorized system access.
Encryption at Rest. All Ministerio de Hacienda Data and Personal Data at rest in persistent storage (such as spinning disk, SSD, and flash drive or other removable media) must be encrypted. The granularity of encryption will be commensurate with the use case and risks of this data (for example, on a single-user system, whole-disk encryption will meet the requirement, but on a multi-tenant system with registered data, field-level encryption is required).
Encryption at Rest. The hard disks of all servers are encrypted thanks to an encrypted file system that encrypts all of your data and metadata at rest using an industry standard AES-256 encryption algorithm. Cryptographic keys protected by certificates, relying on the SHA256 signature algorithm.
Encryption at Rest. All Republic Data and Personal Data at rest in persistent storage (such as spinning disk, SSD, and flash drive or other removable media) must be encrypted. The granularity of encryption will be commensurate with the use case and risks of this data (for example, on a single-user system, whole-disk encryption will meet the requirement, but on a multi-tenant system with registered data, field-level encryption is required).
Encryption at Rest. ‌ 10.7.1 All user-writable partitions on portable devices (laptops, phones, etc.) and portable storage media MUST be encrypted at the media-level (i.e. Full Disk Encryption (FDE)).
Encryption at Rest. Supplier will use AES 256 or above to encrypt Personal Information Processed on its network.
Encryption at Rest. All PII and education records, whether stored in databases (e.g., Azure SQL) or other storage mechanisms, are encrypted at rest. This includes leveraging Azure SQL's built-in encryption capabilities, ensuring data is encrypted within the database and on the underlying storage.
Encryption at Rest. State Street shall encrypt any laptops, mobile devices (e.g. Blackberries, PDAs), containing Client Data used by State Street’s personnel using an industry recognized encryption algorithm with at least 256 bit encryption AES (or equivalent).
Encryption at Rest. 7.2.1. Where a device that forms part of any solution or product is not permanently held within a physically secure boundary within a site listed in the respond to the ITT, or subsequently notified to Census Security and received approval for adequate physical security, it must have storage device level encryption applied. 7.2.2. Where any element of backup/recovery provision uses tape storage, the Service Provider will consult with Census Security to determine appropriate security measures which may include tape encryption.
Encryption at Rest. All Brightmile data is stored using standard encryption mechanisms for both data in transit between services and at rest. We use the Advanced Encryption Standard (“AES”) algorithm to encrypt data at rest. All data at the storage level is encrypted with AES256 by default. Data stored is encrypted at the storage level using AES, in Galois/Counter Mode (GCM) in almost all cases. In select cases, AES is used in Cipher Block Chaining (CBC) mode with a hashed message authentication code (HMAC) for authentication; and for some replicated files, AES is used in Counter (CTR) mode with HMAC. In addition to the storage system level encryption described above, in most cases data is also encrypted at the storage device level with AES256 for hard disks (HDD) and solid state drives (SSD), using a separate device-level key (which is different than the key used to encrypt the data at the storage level). A small number of legacy HDDs use AES128.

Related to Encryption at Rest

  • Encryption The Fund acknowledges and agrees that encryption may not be available for every communication through the System, or for all data. The Fund agrees that Custodian may deactivate any encryption features at any time, without notice or liability to the Fund, for the purpose of maintaining, repairing or troubleshooting the System or the Software.

  • Data Encryption 2.1. For all COUNTY data, The CONTRACTOR shall encrypt all non-public data in transit regardless of the transit mechanism. 2.2. For all COUNTY data, if the CONTRACTOR stores sensitive personally identifiable or otherwise confidential information, this data shall be encrypted at rest. Examples are social security number, date of birth, driver’s license number, financial data, federal/state tax information, and hashed passwords. 2.3. For all COUNTY data, the CONTRACTOR’S encryption shall be consistent with validated cryptography standards as specified in National Institute of Standards and Technology Security Requirements as outlined at ▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇.▇▇▇/nistpubs/Legacy/SP/nistspecialpublication800-111.pdf

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the County Information Security Office.

  • Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128-bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.