Pseudonymisation and Encryption Sample Clauses

Pseudonymisation and Encryption. The following measures should be implemented to perform pseudonymisation of personal data: • Data are stored on the back-end virtualized platform under the name of the cloud host. • All the files corresponding to the Cloud host are stored in the form of block storage on the back-end. In extreme cases, even if the data are stolen, the customer data cannot be inverted to obtain Customer’s data. • Other.
AutoNDA by SimpleDocs
Pseudonymisation and Encryption. 2. Confidentiality
Pseudonymisation and Encryption. - Article 32 Section 1 lit. a) GDPR – pseudonymisation and encryption of personal data.

Related to Pseudonymisation and Encryption

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

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

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

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

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

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