Encryption Keys Sample Clauses

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.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Encryption Keys. For the security of clients’ backed up data, the C-XxxX Client Software installed in the C-XxxX XX- CLIENT encrypts every file it sends with an encryption key provided by the client. The files are stored and remain encrypted on the C-XxxX XX-SYSTEM at all times. The decryption process occurs during recovery and is performed by the C-XxxX XX-CLIENT. This ensures that all backed up data transferred and stored outside the client location is always encrypted. The C-XxxX XX-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.
Sample 1Sample 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.
Sample 1Sample 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.
Sample 1
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.
Sample 1
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 Xxxxxxx 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 Xxxxxxx shall have no liability to the Customer in such circumstances.
Sample 1
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.
Sample 1
AutoNDA by SimpleDocs
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.
Sample 1

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

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

  • Passwords Passwords are an important aspect of computer security. A poorly chosen password may result in unauthorized access and/or exploitation of Placer County’s resources. All users, including contractors and vendors with access to the County’s systems, are responsible for the creation and protection of passwords and additionally any updates to County Password policies must be followed. Users must not use the same password for Placer County accounts and personal accounts. The reliability of passwords for maintaining confidentiality cannot be guaranteed. Always assume that someone, in addition to the intended or designated recipient, may read any and all messages and files. Any user suspecting that his/her password may have been compromised must, without delay, report the incident to Placer County IT. 10.2.4.1 Passwords must never be shared or disclosed. If a password is accidentally exposed or suspected of exposure, the password should be changed immediately. 10.2.4.2 All passwords must be changed on a specified, periodic basis. 10.2.4.3 Default passwords provided by the vendor for access to applications/systems on the network must be changed to unique and secret passwords. 10.2.4.4 Immediately inform the Information Technology Service Desk when user accounts are no longer required or will not be used for a period of 30 days or more. 10.2.4.5 All accounts not used for 90 days will be automatically disabled.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • Password To enable you, and only you, to use the Service, you will be asked to choose a password when you register and are accepted as a customer of the Service. This password is stored in encrypted form by us. You are responsible for maintaining the confidentiality of your Funds Transfer customer number and password. No one at OneUnited Bank has access to your Accounts passwords or user ID's. You are responsible for uses of the Service whether or not actually or expressly authorized by you. Therefore, it is important that you DO NOT SHARE YOUR ACCOUNT NUMBER OR PASSWORD WITH ANYONE FOR ANY REASON. No one at OneUnited Bank will know or need to know your password, and OneUnited Bank employees will never ask for your password. If you believe your password has been lost or stolen, or that someone has transferred or may transfer money from your Account without your permission, call: (877) ONE-UNITED or fax: (000) 000-0000, or e-mail: xxxxxxxxxxxxxxx@xxxxxxxxx.xxx, or write: Funds Transfer Administrator, OneUnited Bank 0000 Xxxxxxxx Xxxx, Los Angeles, CA, 90016. You agree to notify us AT ONCE if you believe your password has been lost or stolen. Telephoning us promptly is the best way to protect yourself from possible losses. If you never tell us, you could lose all of the money in your account (plus your maximum overdraft line of credit). However, if you tell us within 2 business days, you can lose no more than $50 if someone used your password without your permission. If you do NOT tell us within 2 business days after you learn of the loss or theft of your password, and we can prove we could have stopped someone from using your password without your permission if you had told us, you could lose as much as $500. You can see a complete statement of all your funds transfers effected or pending at any time by clicking on the History tab. If your statement shows transfers that you did not make, notify us AT ONCE. If you do not tell us within 60 days after the transfer was posted to your statement, you may not get back any money you lost after the 60 days, if we can prove that we could have stopped someone from taking the money if you had told us in time. If a good reason (such as a long trip or a hospital stay) kept you from telling us, we will extend the time periods.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!