Data in Transit Sample Clauses
The 'Data in Transit' clause defines the requirements and protections for data as it is transmitted between systems or parties. Typically, this clause mandates the use of secure transmission protocols such as TLS or SSL to prevent unauthorized interception or access to sensitive information while it is being sent over networks. By specifying these security measures, the clause helps ensure the confidentiality and integrity of data during transfer, addressing the risk of data breaches or leaks during communication.
POPULAR SAMPLE Copied 4 times
Data in Transit. The Contractor shall ensure all Non-Public Data is encrypted when transmitted across networks to protect against eavesdropping of network traffic by unauthorized users. In cases where source and target endpoint devices are within the same protected subnet, Non-Public Data transmission must still be encrypted due to the potential for high negative impact of a covered Data Breach. The types of transmission may include client-to-server, server-to-server communication, as well as any data transfer between core systems and third party systems.
1) Where an endpoint device is reachable via web interface, web traffic must be transmitted over Secure Sockets Layer (SSL), using only strong security protocols, such as Transport Layer Security (TLS).
2) Non-web transmission of Non-Public Data should be encrypted via application level encryption.
3) Where the application database resides outside of the application server, the connection between the database and application should also be encrypted using Federal Information Processing Standard (FIPS) compliant cryptographic algorithms referenced in FIPS Publication 197.
4) Where application level encryption is not available for non-web Non-Public Data traffic, network level encryption such as Internet Protocol Security (IPSec) or SSH tunneling shall be implemented.
5) Email is not secure and shall not be used to transmit Non-Public Data.
Data in Transit. The Service will use HTTPS using Secure Socket Layer (SSL) for communications between User and the Service. This is standard secure protocol designed to protect against tampering, man in the middle attacks, etc. All communications within the Service use secure communication protocols.
Data in Transit. Supplier uses industry standard encryption algorithms and best practice configurations to ensure security of data transmissions. For example, encryption using AES-256, Data Authentication using at least SHA1, and Handshake encryption using at least RSA-2048. In certain cases, Supplier may secure data in transit through use of its own encryption and configuration policies, which are recognized as industry standard by a technology standard organizations; like, IEEE and RFC.
Data in Transit. 281 The Service Provider shall comply, and shall procure the compliance of its employees, agents, consultants and contractors with the Security Policy.
Data in Transit. Insecure protocols such as Telnet, FTP and HTTP, which allow credentials to pass in clear text, must never be used, unless agreed upon by Amazon Information Security in writing.
Data in Transit. The Data Importer restricts access to Personal Data leaving the Data Importer’s network (e.g., through encryption).