Transport security Sample Clauses

Transport security. Each Participant Member’s security policy shall include written policies and procedures to ensure a secure channel for communications between Participant Members and Participants.
AutoNDA by SimpleDocs
Transport security. Entry control
Transport security. Each QHIN’s security policy shall include written policies and procedures consistent with the technical requirements specified in the QHIN Technical Framework to ensure a secure channel for communications between QHINs and between QHINs and Participants.
Transport security. ☐ none ☐ Basic128 ☐ Basic256 ☐ Basic256SHA256 ☐ Selfsigned ☐ Chained CAs
Transport security. (i) Data carriers are removed from the data centre only if they cease to be functional; (ii) Otherwise, data carriers for transport purposes are always carried on the respective person and are demagnetised and disposed of immediately.
Transport security. The <TransportSecurity> tag provides the security specifications for the transport layer of the TPA. It may be omitted if transport security will not be used for this TPA. Unless otherwise specified below, transport security applies to messages in both directions. For each party which is represented by a role parameter in a prototype TPA, the corresponding tags under <Party> and <LogonParty> must be given values when the role parameter is replaced by an actual name. Transport security may be either encryption or authentication. Both encryption and authentication may be used in the same TPA, especially if authentication is by userid and password. Authentication verifies the sender of the message. Encryption prevents the message from being read by unauthorized parties but by itself performs no authentication or nonrepudiation For encryption, the protocol and protocol version (optional) must be supplied by the appropriate tags. Examples of encryption protocols are RC2, RC5, and RC6. Only certificate-based encryption is defined. For authentication, the authentication type must be specified with the <PasswordAuthen> or <CertificateAuthen> tag. The protocol (e.g. SSL), protocol version (optional), and certificate parameters or optional starting userid and password must be specified. A public key certificate must be supplied for each party (except as specified below). Authentication is bi-directional if each party has to authenticate to the other during a given message exchange. The alternative is that the client authenticates to the server but not vice- versa. In most cases, the choice is determined by other factors. If SSL Ver. 3 is specified for encryption, authentication is always bi-directional. If the authentication type is PASSWORD, the client authenticates to the server. If the authentication type is CERTIFICATE, the authentication could be bi-directional or not. For the purpose of this TPA, it is defined as bi-directional unless otherwise specified below. It should be understood that in a TPA in which each party can act as either a server or a client for different actions, the security definitions must enable each party to authenticate to the other, though not necessarily in the same message exchange. The <Certificate> tag provides the parameters needed to define the certificates. The <CertType> tag identifies the type of certificate. Examples are X.509V1, X.509V2, and X.509V3. The <KeyLength> tag gives the key length in bits (e.g. 512). All parties must...
Transport security. Biohazardous materials must be secured during transport from unauthorized access or theft and not left unattended in unlocked vehicles. A chain-of-custody should be established when shipping biohazardous materials, for example, using a courier service.
AutoNDA by SimpleDocs

Related to Transport security

  • Airport Security The Contractor shall be familiar with and conduct its operations in accordance with all regulations and directives of the Authority and the Transportation Security Administration, and any other federal, state or local government having jurisdiction over the airport, with respect to the maintenance of airport security.

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

  • TRANSPORT SERVICES Upon the conclusion of such multilateral negotiations, the Parties shall conduct a review for the purpose of discussing appropriate amendments to this Agreement so as to incorporate the results of such multilateral negotiations.

  • JOB SECURITY 23.01 Subject to the willingness and capacity of individual employees to accept relocation and retraining, the Employer will make every reasonable effort to ensure that any reduction in the work force will be accomplished through attrition.

  • Safety; Security Contractor’s failure to comply with any of the requirements in this Section shall be cause for termination.

  • CONTRACT SECURITY 8.2.1 The Contractor shall, prior to the Commencement Date or within the specified time, provide to the Owner any contract security specified in row D.2 of the Information Sheet.

  • SHIPPING AND AIR TRANSPORT 1. Profits of an enterprise of a Contracting State from the operation of ships or aircraft in international traffic shall be taxable only in that State. 2. The provisions of paragraph 1 shall also apply to profits from the participation in a pool, a joint business or an international operating agency.

  • Internet Security The Service utilizes a comprehensive security strategy to protect your accounts and transactions conducted over the Internet. Prior to activating your access to the Service, our Internet Banking Department will verify your identity and authorization against information associated with the Eligible Account (s) that you request to be linked to the Service. Access IDs and Passcodes - One of the main security features protecting the Service is the unique combination of your Access Identification Code (Access ID) and Passcode. During the enrollment process, you will be asked to select a unique Access ID, and then choose a Passcode that will be used to gain access to the Service. You determine your own Passcode, which is encrypted in our database. Neither this Institution nor its Service Providers have access to this information. The Service will automatically deactivate your account after three unsuccessful login attempts within a 24-hour time frame. You may reset your passcode online or you may contact this Institution for assistance. Because your Passcode is used to access your accounts, you should treat it as you would any other sensitive personal data. • You should carefully select a Passcode that is hard to guess. • You should not use words based on your name, address or other personal information. • Special characters may be used to increase security. • Do NOT use dictionary words. The “Help” link within the Service will offer tips on choosing a secure Passcode that you can remember. • Keep your Passcode safe. • Memorize your Passcode and do NOT write it down. • You should also change your Passcode occasionally, such as every 90 days. • A Passcode should be changed immediately if you suspect that your Passcode has been compromised. This can be done at any time from the “User Services” menu after you log on to the Service. NEITHER THIS INSTITUTION NOR ITS SERVICE PROVIDERS WILL CONTACT YOU VIA TELEPHONE OR EMAIL REQUESTING PERSONAL INFORMATION, YOUR ACCESS ID, OR YOUR PASSCODE. IF YOU ARE CONTACTED BY ANYONE REQUESTING THIS INFORMATION, PLEASE CONTACT US IMMEDIATELY.

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

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

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