Encryption and Decryption Sample Clauses

Encryption and Decryption. The Approved UHD Content Protection System shall use AES (as specified in NIST FIPS-197) with a key length of 128 bits or greater, DVB-CSA3 or other encryption algorithm approved in writing by Licensor. DVB-CSA (version 1) is NOT approved. New keys must be generated each time content is encrypted (though different instances of the same title on the same service may be encrypted with the same key). A single key shall not be used to encrypt more than one piece of content or more data than is considered cryptographically secure. The random number generator (RNG) used for key generation shall be cryptographically secure and shall be on the list of RNGs approved in FIPS 140-2 Annex C. The content protection system shall only decrypt content into memory temporarily for the purpose of decoding and rendering the content and shall never write decrypted content (including, without limitation, portions of the decrypted content) or streamed encrypted content into permanent storage. Memory locations used to temporarily hold decrypted content shall be secured from access by any code running outside of the Trusted Execution Environment and any trusted application other than the content protection system trusted application(s). (A "Trusted Execution Environment" or "TEE" is a computing environment which is isolated from the application execution environment using a security mechanism such as a verified implementation of ARM TrustZone, hardware enforced virtualization, a separate security processor or processor core or other similar security technology.). Decrypted content shall be securely deleted and overwritten as soon as possible after the content has been decoded and passed to rendering functions. Keys, passwords, and any other information that are critical to the cryptographic strength of the Approved UHD Content Protection System (“critical security parameters”, CSPs) may never be transmitted or permanently or semi-permanently stored in unencrypted form. Memory locations used to temporarily hold CSPs must be secured from access by any code running outside of the Trusted Execution Environment and any trusted application other than the content protection system trusted application(s). Where decrypted content is carried on buses or data paths that are accessible with Widely Available Tools or Specialized Tools it must be encrypted, for example during transmission to the graphics or video subsystem for rendering. The Approved UHD Content Protection System shall encrypt ...
AutoNDA by SimpleDocs
Encryption and Decryption. When applicable, Contractor shall furnish encryption and decryption software compatible with DOL’s software to ensure security and confidentiality (when using SDT process or Confidential Information received is in motion or at rest).
Encryption and Decryption. (i) All content in Your Submissions (including data, material, communications or information, in any format whatsoever, including, without limitation, any data files, text, computer software, images, graphics, photos, videos, sound, audio files, recordings directories, documents, that is made available on or transmitted through eProQ by you, your employees, directors, representatives or agents) (“Your Content”) shall be encrypted for security reasons when uploaded or submitted by you and transmitted through eProQ. You agree that any of Your Content that is so encrypted shall be complete and accurate after decryption and in any event, you accept any error, misstatement or omission that may occur upon decryption or encryption.
Encryption and Decryption. 3.1. The Content Protection System shall use AES (as specified in NIST FIPS- 197) with a key length of 128 bits or greater.
Encryption and Decryption. GCHD has determined that it is appropriate to implement encryption software on systems that contain ePHI.
Encryption and Decryption. The three entities A, B and C may use their common key for encrypting and decrypting the messages. Encryption Scheme1:
Encryption and Decryption. This subsection considers the braid cryptosystem proposed in chapter 3. The encryption and decryption scheme is as follows.
AutoNDA by SimpleDocs

Related to Encryption and Decryption

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

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

  • DATA PROTECTION AND DATA PROCESSING 6.1 The Company and the Client acknowledge that for the purposes of the Data Protection Xxx 0000 and the GDPR, that the Client and the Company shall be considered separate data controllers in relation to the provision of the Services, save and except that in the case of lead generation services, the Client shall be the data controller and the Company shall be the data processor.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • LOCATION AND DESCRIPTION The subject property is a 3-bedroom apartment unit and bearing postal address Xxxx Xx. X-0-00, Xxxxx X, Xxxxx Xxxxx, Xxxxx Xxxxx Xxxxxx Xxxxxxxx 0, Xxxxx Xxxxxx Xxxxxxxx, 00000 Xxxxxxxx, Xxxxxx Xxxxxxxx. Accommodation:- Foyer, kitchen, yard, dining area, living area opening onto a balcony, master bedroom with an attached bath 1, bedroom 2, bedroom 3 and bath 2.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

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