Transport Layer Security Sample Clauses

Transport Layer Security. (TSL) is a protocol that ensures privacy between communicating applications and their users on the Internet.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Transport Layer Security. (TLS): A protocol (standard) that ensures privacy between communicating applications and their users on the Internet. When a server and client communicate, TLS ensures that no third party may eavesdrop or tamper with any message. TLS is the successor to the Secure Sockets Layer (SSL). Terms used, but not otherwise defined, in this Agreement shall have the same meaning given those terms under HIPAA, the HITECH Act, and other applicable federal law.
Sample 1Sample 2
Transport Layer Security. Interaction between devices on the Internet domain and Media Service Provider Domains is over an untrusted network, the Internet. To secure interaction over this channel, FLAME uses protocols based on HTTPS using strong encryption.
Sample 1Sample 2
Transport Layer Security. Each Component must undergo certification and thus have a valid X.509 certificate, in order to establish trust among interacting parties and to enable the possibility of remote attestation. This requirement allows for trustworthy identification and authentication by using a central public key infrastructure (PKI). Main functionalities Component and identify certification Digital Certificates and key pairs management and provisioning (Public Key Infrastructure) Requirements Mapping 12009, 12025, 12033 certification Provide Digital Certificates and related metadata for a specific entity (component or account) verifyCertification Verify a specific certificates and its status Identity and Access Management Send and verify certificates Data Connector Send and verify certificates Marketplace Application metadata Module Description This component ensures further authorization enforcement restricting unauthorized access to data resources, by relying on Role Based and/or Attribute Based Access Control models (RBAC, ABAC). Once the access token has been validated by the Authorization Server (IAM), this component then can perform Access Control decisions on requested data, also relying on policy languages such as XACML (Extensible Access Control Mark-up Language) [14] or ODRL [15] (Open Digital Rights Language). The component will act as a Policy Enforcement Point (PEP), by monitoring the platform actions and intercepting incoming data requests. It will grant access on the decisions made by the Data Usage Control (acting as a Policy Decision Point). Main functionalities Role-based access control (RBAC) Attribute-based access control (ABAC) Policy Enforcement Point. Policy Decision Point Requirements Mapping 13020, 12009, 12025, 12033, 12036 grantDataAccess Grant access to a specific resource against specific access and usage policy and context Identity and Access Management Validate access token Data Usage Control Verify usage rules Audit Logger Store access events Data Connector Perform access and usage enforcement Marketplace Perform access and usage enforcement Module Description As the Usage Control concept is an extension of Access Control, the target of this component is to enforce restrictions on data usage and data processing, after access to data has been granted by the IAM and Data Access components. Those policies compose a Usage Contract, regulating what may be done with a data asset and what not and for which purpose. This component is in charge of ensur...
Sample 1
Transport Layer Security. All web service communication within CHIC MUST go over a secured HTTP connection by using the HTTP SSL/TLS protocol as specified in [15],[16],[17],[18]  SSL version 1.0 or 2.0 MUST NOT be used.  TLS 1.1/1.2 are RECOMMENDED  SSL version 3.0 or TLS 1.0/1.1/1.2 MUST be used.
Sample 1
Transport Layer Security. All Illuminate web traffic is encrypted over the wire via SSL. Firewalls are used to limit access to only essential services. Direct database access for district technical staff is managed by Illuminate, and all database traffic is also encrypted in transit via SSL. Illuminate products hosted in the Google Cloud Platform benefit from the same security precautions Google uses for its own products. Physical data centers include multi-layered security featuring camera and physical monitoring, credential scanning, and biometric checks. Illuminate also leverages a physical data center in Los Angeles and a cloud-based data center at Amazon Web Services. Google data center security includes: ● Key card access ● Biometric scanners ● Double mantrap entry ● 24x7x365 perimeter and interior recorded video surveillance ● 24x7x365 in-house security guards ● Locked server cabinets Google data center certifications include: ● NIST SP 800–61 ● ISO 50001 Illuminate maintains both onsite and offsite backups for all client databases, allowing us to store and retrieve data anytime. Backups are shipped offsite nightly, and are encrypted at rest to prevent data theft. In the event of a catastrophic data center failure, we can retrieve data that is at most 24 hours old. Logging occurs at multiple levels within the system. We maintain a log in the system database that records data-changing operations. Page accesses can also optionally be recorded in a flat file showing the page accessed, the user performing the access, and the date/time of the access. Certain areas of the system, such as official student grades, also have their own logging features that track more detailed information about each transaction.
Sample 1

Related to Transport Layer Security

  • User Security You agree to take every precaution to ensure the safety, security and integrity of your account and transactions when using Mobile Banking. You agree not to leave your Device unattended while logged into Mobile Banking and to log off immediately at the completion of each access by you. You agree not to provide your username, password or other access information to any unauthorized person. If you permit other persons to use your Device, login information, or other means to access Mobile Banking, you are responsible for any transactions they authorize and we will not be liable for any damages resulting to you. You agree not to use any personally identifiable information when creating shortcuts to your Account. We make no representation that any content or use of Mobile Banking is available for use in locations outside of the United States. Accessing Mobile Banking from locations outside of the United States is at your own risk.

  • Server Security Servers containing unencrypted PHI COUNTY discloses to 4 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 5 must have sufficient administrative, physical, and technical controls in place to protect that data, based 6 upon a risk assessment/system security review.

  • Cyber Security Insurance for loss to the Owner due to data security and privacy breach, including costs of investigating a potential or actual breach of confidential or private information. (Indicate applicable limits of coverage or other conditions in the fill point below.) « »

  • Tender Security 18.1 The Tenderer shall furnish as part of its Tender, either a Tender-Securing Declaration or a Tender Security, as specified in the TDS, in original form and, in the case of a Tender Security, in the amount and currency specified in the TDS. 18.2 A Tender Securing Declaration shall use the form included in Section IV, Tendering Forms. 18.3 If a Tender Security is specified pursuant to ITT 18.1, the Tender Security shall be a demand guarantee in any of the following forms at the Tenderer option: i) cash; ii) a bank guarantee; iii) a guarantee by an insurance company registered and licensed by the Insurance Regulatory Authority listed by the Authority; or

  • EMPLOYER SECURITY 4.1 The Union agrees that during the life of this Agreement it will not cause, encourage, participate in or support any strike, slow-down or other interruption of or interference with the normal functions of the Employer.

  • System Security (a) If any party hereto is given access to the other party’s computer systems or software (collectively, the “Systems”) in connection with the Services, the party given access (the “Availed Party”) shall comply with all of the other party’s system security policies, procedures and requirements that have been provided to the Availed Party in advance and in writing (collectively, “Security Regulations”), and shall not tamper with, compromise or circumvent any security or audit measures employed by such other party. The Availed Party shall access and use only those Systems of the other party for which it has been granted the right to access and use. (b) Each party hereto shall use commercially reasonable efforts to ensure that only those of its personnel who are specifically authorized to have access to the Systems of the other party gain such access, and use commercially reasonable efforts to prevent unauthorized access, use, destruction, alteration or loss of information contained therein, including notifying its personnel of the restrictions set forth in this Agreement and of the Security Regulations. (c) If, at any time, the Availed Party determines that any of its personnel has sought to circumvent, or has circumvented, the Security Regulations, that any unauthorized Availed Party personnel has accessed the Systems, or that any of its personnel has engaged in activities that may lead to the unauthorized access, use, destruction, alteration or loss of data, information or software of the other party hereto, the Availed Party shall promptly terminate any such person’s access to the Systems and immediately notify the other party hereto. In addition, such other party hereto shall have the right to deny personnel of the Availed Party access to its Systems upon notice to the Availed Party in the event that the other party hereto reasonably believes that such personnel have engaged in any of the activities set forth above in this Section 9.2(c) or otherwise pose a security concern. The Availed Party shall use commercially reasonable efforts to cooperate with the other party hereto in investigating any apparent unauthorized access to such other party’s Systems.

  • E7 Security The Authority shall be responsible for maintaining the security of the Authority premises in accordance with its standard security requirements. The Contractor shall comply with all security requirements of the Authority while on the Authority premises, and shall ensure that all Staff comply with such requirements.

  • Network Security The AWS Network will be electronically accessible to employees, contractors and any other person as necessary to provide the Services. AWS will maintain access controls and policies to manage what access is allowed to the AWS Network from each network connection and user, including the use of firewalls or functionally equivalent technology and authentication controls. AWS will maintain corrective action and incident response plans to respond to potential security threats.

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

  • Engine A. Any internal repairs or replacement of internal components, or replacement of engine assembly.

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