Security of Client Data Sample Clauses

Security of Client Data. Each party shall implement appropriate technical, physical and organizational security measures to safeguard Client Personal Data from unauthorized processing or accidental loss or damage, as further described in the applicable Service Description (the “Data Safeguards”). Taking into account the ongoing state of technological development, the costs of implementation and the nature, scope, context and purposes of the processing of the Client Personal Data, as well as the likelihood and severity of risk to individuals, Accenture’s implementation of and compliance with the Data Safeguards is designed to provide a level of security appropriate to the risk in respect of the processing of the Client Personal Data.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Security of Client Data. AdvancedMD agrees to maintain the security of Client Data using industry- standard data security protocols, and other methods reasonably deemed to be adequate for secure business data. AdvancedMD shall employ commercially reasonable storage and reasonable precautions to prevent the loss of or alteration to Client’s Data, but AdvancedMD does not guarantee against any such loss or alteration. AdvancedMD is not, and will not be, Client’s official record keeper.
Sample 1
Security of Client Data. 2-1-1 San Diego shall establish, implement and maintain commercially reasonable security measures to ensure the privacy and security of Client Data while at rest in the Database and during its transmittal to and from Participants through the Database.
Sample 1
Security of Client Data. 4.1 The Sub-Administrator shall adopt written security policies and procedures intended to prevent unauthorized access or damage to Client Data in accordance with good industry practice and shall follow such procedures at all times during the terms of this Agreement.
Sample 1
Security of Client Data. Poka will maintain during the Term the appropriate technical and organizational measures to ensure the security and backup of Client Data including protection against unauthorized or unlawful processing and against accidental or unlawful destruction, loss or alteration in accordance with Xxxx’s Security Policy.
Sample 1

Related to Security of Client Data

  • Client Data The Subrecipient shall maintain client data demonstrating client eligibility for services provided. Such data shall include, but not be limited to, client name, address, income level or other basis for determining eligibility, and description of service provided. Such information shall be made available to Grantee monitors or their designees for review upon request.

  • SECURITY OF PERSONAL INFORMATION 19.1 For this clause “personal information” has the meaning given to it in the Privacy Act 1988 (Cth).

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

  • Government Data Practices and Intellectual Property 22.1. Government Data Practices. Vendor and MMCAP must comply with the Minnesota Data Practices Act, Minn. Stat. ch.13 as it applies to all data provided by MMCAP under this Contract, and as it applies to all data created, collected, received, stored, used, maintained, or disseminated by Vendor under this Contract. The civil remedies of Minn. Stat. Section 13.08 apply to the release of the data governed by the Minnesota Government Data Practices Act, Ch. 13, by either the Vendor or MMCAP. If Vendor receives a request to release the data referred to in this article, Vendor must immediately notify MMCAP, and consult with MMCAP as to how the Vendor should respond to the request. The Vendor’s response to the request will comply with applicable law. Vendor agrees to indemnify, save, and hold the State of Minnesota, its agent and employees, harmless from all claims arising out of, resulting from, or in any manner attributable to any violation of any provision of the Minnesota Government Data Practices Act, including legal fees and disbursements paid or incurred to enforce this provision of the Contract. In the event Vendor subcontracts any or all of the work to be performed under the Contract, Vendor shall retain responsibility under the terms of this paragraph for such work.

  • Security of Information Unless otherwise specifically authorized by the DOH Chief Information Security Officer, Contractor receiving confidential information under this contract assures that: • Encryption is selected and applied using industry standard algorithms validated by the National Institute of Standards and Technology (NIST) Cryptographic Algorithm Validation Program against all information stored locally and off-site. Information must be encrypted both in-transit and at rest and applied in such a way that it renders data unusable to anyone but authorized personnel, and the confidential process, encryption key or other means to decipher the information is protected from unauthorized access. • It is compliant with the applicable provisions of the Washington State Office of the Chief Information Officer (OCIO) policy 141, Securing Information Technology Assets, available at: xxxxx://xxxx.xx.xxx/policy/securing-information-technology-assets. • It will provide DOH copies of its IT security policies, practices and procedures upon the request of the DOH Chief Information Security Officer. • DOH may at any time conduct an audit of the Contractor’s security practices and/or infrastructure to assure compliance with the security requirements of this contract. • It has implemented physical, electronic and administrative safeguards that are consistent with OCIO security standard 141.10 and ISB IT guidelines to prevent unauthorized access, use, modification or disclosure of DOH Confidential Information in any form. This includes, but is not limited to, restricting access to specifically authorized individuals and services through the use of: o Documented access authorization and change control procedures; o Card key systems that restrict, monitor and log access; o Locked racks for the storage of servers that contain Confidential Information or use AES encryption (key lengths of 256 bits or greater) to protect confidential data at rest, standard algorithms validated by the National Institute of Standards and Technology (NIST) Cryptographic Algorithm Validation Program (CMVP); o Documented patch management practices that assure all network systems are running critical security updates within 6 days of release when the exploit is in the wild, and within 30 days of release for all others; o Documented anti-virus strategies that assure all systems are running the most current anti-virus signatures within 1 day of release; o Complex passwords that are systematically enforced and password expiration not to exceed 120 days, dependent user authentication types as defined in OCIO security standards; o Strong multi-factor authentication mechanisms that assure the identity of individuals who access Confidential Information; o Account lock-out after 5 failed authentication attempts for a minimum of 15 minutes, or for Confidential Information, until administrator reset; o AES encryption (using key lengths 128 bits or greater) session for all data transmissions, standard algorithms validated by NIST CMVP; o Firewall rules and network address translation that isolate database servers from web servers and public networks; o Regular review of firewall rules and configurations to assure compliance with authorization and change control procedures; o Log management and intrusion detection/prevention systems; o A documented and tested incident response plan Any breach of this clause may result in termination of the contract and the demand for return of all personal information.

  • Contractor Security Clearance Customers may designate certain duties and/or positions as positions of “special trust” because they involve special trust responsibilities, are located in sensitive locations, or have key capabilities with access to sensitive or confidential information. The designation of a special trust position or duties is at the sole discretion of the Customer. Contractor or Contractor’s employees and Staff who, in the performance of this Contract, will be assigned to work in positions determined by the Customer to be positions of special trust, may be required to submit to background screening and be approved by the Customer to work on this Contract.

  • Security Technology When the service is accessed using a supported web browser, Secure Socket Layer (“SSL”), or equivalent technology shall be employed to protect data from unauthorized access. The service security measures shall include server authentication and data encryption. Provider shall host data pursuant to the DPA in an environment using a firewall that is periodically updated according to industry standards.

  • Personal Information security breach Supplier/Service Provider’s Obligations

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