Encryption Keys Clause Samples

The ENCRYPTION KEYS clause establishes the requirements and responsibilities for managing cryptographic keys used to secure data. It typically outlines who generates, stores, and controls access to the keys, and may specify technical standards or procedures for key rotation and protection. By clearly defining these obligations, the clause ensures that sensitive information remains protected from unauthorized access, thereby reducing the risk of data breaches and ensuring compliance with security best practices.
POPULAR SAMPLE Copied 1 times
Encryption Keys. 16.1 Where, in order to make use of the Service, the Customer is provided with any encryption keys by 2Connect, those encryption keys shall be held at the risk of the Customer and it shall be the sole responsibility of the Customer to ensure that those encryption keys are kept safe and secure. The Customer acknowledges that 2Connect shall not be able to undertake the restoration of any data where the Customer has lost any applicable encryption key provided to it and that 2Connect shall have no liability to the Customer in such circumstances.
View SourceView Similar (4)
Encryption Keys. CUSTOMER ACKNOWLEDGES AND AGREES THAT FLEXENTIAL DOES NOT MAINTAIN COPIES OF CUSTOMER ENCRYPTION KEYS. FLEXENTIAL HAS NO ABILITY TO REGENERATE OR RECOVER LOST ENCRYPTION KEYS NOR CAN FLEXENTIAL ACCESS ENCRYPTED DATA. FLEXENTIAL SHALL NOT BE LIABLE FOR LOSS OF DATA AS A RESULT OF OPERATIONAL ERRORS CAUSED BY THE SYSTEM OR SECURITY ADMINISTRATORS OF THE AGENT OTHER OPERATIONAL PERSONNEL OF CUSTOMER.
View Source
Encryption Keys. For the security of clients’ backed up data, the C-▇▇▇▇ Client Software installed in the C-▇▇▇▇ ▇▇- CLIENT encrypts every file it sends with an encryption key provided by the client. The files are stored and remain encrypted on the C-▇▇▇▇ ▇▇-SYSTEM at all times. The decryption process occurs during recovery and is performed by the C-▇▇▇▇ ▇▇-CLIENT. This ensures that all backed up data transferred and stored outside the client location is always encrypted. The C-▇▇▇▇ ▇▇-CLIENT uses up to 256 AES encryption and can be configured with private and account encryption keys. Encryption meets National Institute of Standards and Technology (NIST) FIPS 140-2 compliance and has been validated by NIST with Certificate #1240.
View SourceView Similar (3)
Encryption Keys. Encryption keys must be protected. Encryption key length must be a minimum of the latest industry recognized, and a maximum of the length authorized under applicable law and/or regulation. A log of keys must be kept for each user. Keys must be protected through a strong password (chosen by the end-user) and must be only accessible for the respective end-user where applicable. Access control for system keys must be configured as restrictive as possible. If the key is no longer needed or life-time exceeded the key must securely deleted (unrecoverable) from all storage medias.
View SourceView Similar (2)
Encryption Keys. For all infrastructure that Tanium manages on behalf of customers as part of the TaaS Offering, the security of instances is managed through public key infrastructure (PKI) and data at rest encryption with unique keys for each customer environment. AWS Key Management System (KMS) is leveraged to generate, manage and use encryption keys following industry best practices, including NIST validated FIPS 140-2 based hardware. AWS enables customers to open a secure, encrypted session to AWS servers using HTTPS where TLS may be used for all import and export data functions. Client to client and client to server communication uses Tanium’s proprietary protocol, which digitally signs messages for authenticity and transmits hashed message responses for integrity. Tanium follows AWS guidance and recommends that customers use secure protocols that offer authentication and confidentiality, such as TLS or IPsec, to reduce the risk of data tampering or loss.
View SourceView Similar (2)
Encryption Keys. 16.1 Where, in order to make use of the Service, the Customer is provided with any encryption keys by Aspire, those encryption keys shall be held at the risk of the Customer and it shall be the sole responsibility of the Customer to ensure that those encryption keys are kept safe and secure. The Customer acknowledges that Aspire shall not be able to undertake the restoration of any data where the Customer has lost any applicable encryption key provided to it and that Aspire shall have no liability to the Customer in such circumstances.
View SourceView Similar (2)
Encryption Keys. All keys used for encryption must be handled in accordance with documented key management processes and procedures that include and describe, at a minimum, the following controls: a. Secure key storage; b. Secure key distribution; c. Generation of strong keys; d. Annual encryption key changes (particularly as used to handle video); e. Addition of new keys; f. Destruction of old keys; g. Split knowledge and dual control of keys; h. Replacement of known or suspected compromised keys; i. Revocation of old or invalid keys; j. Prevention of unauthorized substitution of keys; and k. Requirements for key custodians.
View Source
Encryption Keys. 16.1 Where, in order to make use of the Service, the Customer is provided with any encryption keys by Stratus, those encryption keys shall be held at the risk of the Customer and it shall be the sole responsibility of the Customer to ensure that those encryption keys are kept safe and secure. The Customer acknowledges that ▇▇▇▇▇▇▇ shall not be able to undertake the restoration of any data where the Customer has lost any applicable encryption key provided to it and that ▇▇▇▇▇▇▇ shall have no liability to the Customer in such circumstances.
View Source

Related to Encryption Keys

  • 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 Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

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

  • Encrypt or Encryption As defined in the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security Rule at 45 CFR 164.304, means the use of an algorithmic process to transform Personally Identifiable Information into an unusable, unreadable, or indecipherable form in which there is a low probability of assigning meaning without use of a confidential process or key.

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.