Encryption in Transit Clause Samples

POPULAR SAMPLE Copied 1 times
Encryption in Transit. We significantly reduce the likelihood that any data we send across the public Internet is browsed by an unauthorized party by doing the following: 1. We only use third-party services that are available over HTTPS. 2. We never transmit secrets such as passwords or keys over internal chat systems and instead use Keybase to encrypt all such messages. 3. Our limited web services are all available exclusively via HTTPS.
View Source
Encryption in Transit. Service Provider should utilize latest industry recognized and utilized encryption technologies (encryption consistent with NIST (National Institute of Standards and Technology) such as 256-bit TLS (1.2 or above) Certification and ▇▇▇▇-▇▇▇ ▇▇▇ public keys for internet transactions, secure FTP for transfer of files, encrypted e-mail and any other communications.
View SourceView Similar (2)
Encryption in Transit. Company will ensure that all access to Republic Data and Personal Data is protected by Transport Layer Security, IPSec, or equivalent protocols. Company will only use encryption algorithms and protocols that comply with industry best practices and that are approved in the then-current version of the National Institute of Standards and Technology Special Publication 800-52. An alternative algorithm or protocol may only be used upon Republic's prior written consent.
View Source
Encryption in Transit. Cross service communication between Brightmile services internally is always encrypted by default using HTTPS (TLS 1.2). All Brightmile APIs enforce HTTPS (TLS 1.2) as standard. All APIs enforce strict transport and x-domain requests are restricted. HTTPS provides security by using a TLS connection, which ensures the authenticity, integrity, and privacy of requests and responses. To accept HTTPS requests, the receiver requires a public–private key pair and an
View Source
Encryption in Transit. 7.1.1. All HTTP interfaces are to be served as encrypted (TLS / HTTPS) by default. 7.1.2. Otherwise, unless a data flow is entirely with a trusted network segment, encryption in transit must be implemented.
View Source
Encryption in Transit. All data in transit between the Customer's device, the LST's systems, and any integrated third-party services is protected using industry-standard encrypted transport protocols (e.g., HTTPS).
View Source
Encryption in Transit. Supplier will use TLS 1.2 or above to encrypt Personal Information transmitted outside of Supplier’s network.
View Source

Related to Encryption in Transit

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

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