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.
View SourceView Similar (4)
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.
View Source
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.
View Source
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.
View Source
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.
View Source
Data in Transit. The Data Importer restricts access to Personal Data leaving the Data Importer’s network (e.g., through encryption).
View Source

Related to Data in Transit

  • Errors in Transmission By using the Services you accept the risk that an item may be intercepted or misdirected during transmission. The Bank bears no liability to you or others for any such intercepted or misdirected items or information disclosed through such errors.

  • Data Input Control It will be possible to retrospectively examine and establish whether and by whom Personal Data have been entered, modified or removed from SAP data processing systems.

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Certain Transfers The sale of all or substantially all of Tenant's assets (other than bulk sales in the ordinary course of business) or, if Tenant is a corporation, an unincorporated association, or a partnership, the transfer, assignment or hypothecation of any stock or interest in such corporation, association, or partnership in the aggregate of twenty-five percent (25%) (except for publicly traded shares of stock constituting a transfer of twenty-five percent (25%) or more in the aggregate, so long as no change in the controlling interest of Tenant occurs as a result thereof) shall be deemed an assignment within the meaning and provisions of this Article. Notwithstanding the foregoing, Landlord's consent shall not be required for the assignment of this Lease as a result of a merger by Tenant with or into another entity, so long as (i) the net worth of the successor entity after such merger is at least equal to the greater of the net worth of Tenant as of the execution of this Lease by Landlord or the net worth of Tenant immediately prior to the date of such merger, evidence of which, satisfactory to Landlord, shall be presented to Landlord prior to such merger, (ii) Tenant shall provide to Landlord, prior to such merger, written notice of such merger and such assignment documentation and other information as Landlord may request in connection therewith, and (iii) all of the other terms and requirements of this Article shall apply with respect to such assignment.