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.
Data Encryption. 2.1. For all COUNTY data, The CONTRACTOR shall encrypt all non-public data in transit regardless of the transit mechanism.
Data Encryption. Vendor and Vendor Staff will encrypt all electronic data and communications containing Citizens Confidential Information using a strong cryptographic protocol that is consistent with industry standards.
Data Encryption. Firm and those providing services for Firm under the Contract, will encrypt all electronic data and communications containing Citizens Confidential Information using a strong cryptographic protocol that is consistent with industry standards.
Data Encryption. Vendor and Vendor Staff will encrypt Citizens Data at rest and in transit using a strong cryptographic protocol that is consistent with industry standards.
Data Encryption. Vendor agrees to store any FIU backup data as part of its designated backup and recovery process in encrypted form, using no less than 128-bit key;
Data Encryption. Contractor shall ensure security by installing firewalls and anti-virus software on computers, ensure operating systems are updated, encrypt information and email exchanges, safeguard any information stored in computers before disposing. All Data transfer must be encrypted using 256 bit (or higher) TLS 1.2 (or higher) for HTTP traffic and SSH version 2 for any batch or real-time non-http transfers. SSL certificates must be SHA 2 and signed by a trusted third party; no self-signed certificates. Data shall be encrypted when at rest in vendor storage. Decryption of data at rest must be under control of the application and not a storage platform. All Data must be stored and transmitted in the contiguous United States of America only. No offshore data transmission (e.g. for support services) or storage (e.g. hosted site or backup, disaster recovery).
Data Encryption. The Braze Services use industry-accepted encryption practices to protect Customer Data and communications during transmissions between a customer's network and the Braze Services, including 256-bit TLS Certificates and 4096-bit RSA public keys at a minimum. Braze audits the TLS ciphers used in connection with the provision of the Braze Services with third-party security auditors to ensure that anonymous or weak ciphers are not used. These audits also confirm that the Braze Services do not allow client renegotiation, support downgrade attack protection and forward secrecy. Data shipped to Amazon Web Services is encrypted in transit and at-rest using AES-256 encryption via Amazon’s managed encryption key process. Data shipped to Rackspace is encrypted in transit and at-rest using AES-256 encryption via Rackspace’s managed encryption key process. Where use of the Braze Services requires a customer to provide access to third party services (for example, AWS S3 credentials for data exports), Xxxxx performs additional encryption of that information.
Data Encryption. Supplier agrees to store all Non-Public Information and any backup of that information as part of its designated backup and recovery processes in encrypted form, using a commercially supported encryption solution. Supplier further agrees that any and all Non-Public Information, as defined herein or under applicable legislation or regulations, stored on any portable or laptop computing device or any portable storage medium is likewise encrypted.
Data Encryption. Supplier shall store and backup Data as part of its designated backup and recovery processes in encrypted form, using no less than 128 bit key encryption.
