Server-Side Encryption Sample Clauses

Server-Side Encryption. The parties will discuss in good faith the feasibility of implementing a mechanism to provide encryption of Included Programs on the server side; provided, however, unless otherwise agreed by Amazon in writing, Amazon shall have no obligation to implement any such mechanism or encryption.
AutoNDA by SimpleDocs

Related to Server-Side Encryption

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Platform (a) The Borrower agrees that the Agent may, but shall not be obligated to, make the Communications (as defined below) available to the Lenders by posting the Communications on the Platform. (b) The Platform is provided “as is” and “as available.” The Agent Parties (as defined below) do not warrant the adequacy of the Platform and expressly disclaim liability for errors or omissions in the Communications. No warranty of any kind, express, implied or statutory, including any warranty of merchantability, fitness for a particular purpose, non-infringement of third-party rights or freedom from viruses or other code defects, is made by any Agent Party in connection with the Communications or the Platform. In no event shall the Agent nor any of its directors, officers, agents, employees, advisors, shareholders, attorneys or Affiliates (collectively, the “Agent Parties”) have any liability to any Borrower, any Lender or any other Person or entity for damages of any kind, including direct or indirect, special, incidental or consequential damages, losses or expenses (whether in tort, contract or otherwise) arising out of the Borrower’s or the Agent’s transmission of communications through the Platform, unless it is determined by a final and nonappealable judgment or court order that the damages were the result of acts or omissions constituting gross negligence or willful misconduct of the Agent Party. “Communications” means, collectively, any notice, demand, communication, information, document or other material provided by or on behalf of the Borrower pursuant to any Loan Document or the transactions contemplated therein that is distributed to the Agent or any Lender by means of electronic communications pursuant to this Section, including through the Platform.

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

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Encryption The Fund acknowledges and agrees that encryption may not be available for every communication through the System, or for all data. The Fund agrees that Custodian may deactivate any encryption features at any time, without notice or liability to the Fund, for the purpose of maintaining, repairing or troubleshooting the System or the Software.

  • Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.

  • Password To enable you, and only you, to use the Service, you will be asked to choose a password when you register and are accepted as a customer of the Service. This password is stored in encrypted form by us. You are responsible for maintaining the confidentiality of your Funds Transfer customer number and password. No one at MIT Federal Credit Union has access to your Accounts passwords or user ID’s. You are responsible for uses of the Service whether or not actually or expressly authorized by you. Therefore, it is important that you DO NOT SHARE YOUR ACCOUNT NUMBER OR PASSWORD WITH ANYONE FOR ANY REASON. No one at MIT Federal Credit Union will know or need to know your password, and MIT Federal Credit Union employees will never ask for your password. If you wish to make a transfer to an Account of another person, you will be asked to provide a separate code word or phrase (the “Shared Secret”) that is known only to you and to the person to whom you are transferring the funds (the “Recipient”). We recommend that you do not use commonly used words, phrases or dates. In order to complete the transfer, the Recipient must provide the Shared Secret and certain other identifying information. YOU AGREE THAT YOU WILL NOT GIVE THE SHARED SECRET TO ANYONE EXCEPT THE RECIPIENT FOR ANY REASON. YOU FURTHER AGREE THAT YOU WILL INSTRUCT THE RECIPIENT NOT TO GIVE THE SHARED SECRET TO ANYONE ELSE FOR ANY REASON. If you believe your password or Shared Secret has been lost or stolen, or that someone has transferred or may transfer money from your Account without your permission, call: 000-000-0000 or fax: 000-000-0000 , or e-mail: xxxxxx@xxx.xxx, or write: Funds Transfer Administrator, MIT Federal Credit Union 000 Xxxxxxxxxx Xxxxxx, Xxxxxxxxx, XX 00000-0000. You agree to notify us AT ONCE if you believe your password has been lost or stolen. Telephoning us promptly is the best way to protect yourself from possible losses. If you never tell us, you could lose all of the money in your account (plus your maximum non-sufficient funds/overdraft (NSF/OD) line of credit). However, if you tell us within 2 business days, you can lose no more than $50 if someone used your password without your permission. If you do NOT tell us within 2 business days after you learn of the loss or theft of your password, and we can prove we could have stopped someone from using your password without your permission if you had told us, you could lose as much as $500. You can see a complete statement of all your funds transfers effected or pending at any time by clicking on the History tab. If your statement shows transfers that you did not make, notify us AT ONCE. If you do not tell us within 60 days after the transfer was posted to your statement, you may not get back any money you lost after the 60 days, if we can prove that we could have stopped someone from taking the money if you had told us in time. If a good reason (such as a long trip or a hospital stay) kept you from telling us, we will extend the time periods.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

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