Customers Security Responsibilities and Assessment Sample Clauses

Customers Security Responsibilities and Assessment. 7.3.1. Customer’s Security Responsibilities. Customer agrees that, without prejudice to Processor’s obligations under Section 7.1 (Processor’s Security Measures, Controls and Assistance) and Section 7.2 (Data Incidents): (a) Customer is solely responsible for its use of the Services, including: (i) making appropriate use of the Services to ensure a level of security appropriate to the risk in respect of the Customer Data; (ii) securing the account authentication credentials, systems and devices Customer uses to access the Services; and (iii) backing up its Customer Data; and (b) Processor has no obligation to protect Customer Data that Customer elects to store or transfer outside of Processor’s and its Subprocessors’ systems.
AutoNDA by SimpleDocs
Customers Security Responsibilities and Assessment. 6.3.1. Customer’s Security Responsibilities 6.3.1.1. Customer agrees that, without prejudice to AIS’s obligations under Section 6.1 (AIS’s Security Measures, Controls and Assistance) and Section 0 (Data Incidents): 6.3.1.1.1. Customer is solely responsible for its use of the Services, including: (a) making appropriate use of the Services to ensure a level of security appropriate to the risk in respect of the Customer Data; (b) securing the account authentication credentials, systems and devices Customer uses to access the Services; and (c) backing up its Customer Data; and 6.3.1.1.2. AIS has no obligation to protect Customer Data in the event that the Customer elects to store or transfer outside of AIS’s and its Sub-Processors’ systems (for example, offline or on-premise storage).
Customers Security Responsibilities and Assessment. (i) Customer’s Security Responsibilities. Customer agrees that, without limitation of Provider’s obligations under Section 4 (Security), Customer is solely responsible for its use of the Service, including (a) making appropriate use of the Service to ensure a level of security appropriate to the risk in respect of the Personal Data; (b) securing the account authentication credentials, systems and devices Customer uses to access the Service; (c) securing Customer’s systems and devices that Provider uses to provide the Service; and (d) backing up Personal Data.
Customers Security Responsibilities and Assessment. 7.3.1. Customer’s Security Responsibilities. Customer agrees that, without prejudice to the Company's obligations under Section 7.1 (Company’s Security Measures and Controls) and Section 7.2 (Data Incidents): (a) Customer is solely responsible for its use of the Services, including: (i) making appropriate use of the Services to ensure a level of security appropriate to the risk in respect of the Customer Data; (ii) securing the account authentication credentials, systems and devices Customer uses to access the Services; and (iii) backing up its Customer Data; and (b) Company has no obligation to protect Customer Data that Customer elects to store or transfer outside of Company’s platform provided through the use of Services.
Customers Security Responsibilities and Assessment. Customer agrees that, without prejudice to Supplier’s obligations under Sections 13-15 (Supplier’s Security Measures, Controls and Assistance) and Section 16 (Data Incidents): (a) Customer is solely responsible for its use of the Services, including: (i) making appropriate use of the Services to ensure a level of security appropriate to the risk in respect of the Customer Data; (ii) securing the account authentication credentials, systems and devices Customer uses to access the Services; and (iii) backing up Customer Data; and (b) Supplier has no obligation to protect Customer Data that Customer elects to store or transfer outside of Processor’s and its Subprocessors’ systems (for example, offline or on-premise storage, or Customer’s Third-Party Service Provider). Customer is solely responsible for evaluating whether the Services, the Security Measures and Supplier’s commitments under Sections 13-17 meet Customer’s needs, including with respect to any security obligations of Customer under the Data Protection Legislation and/or Non-European Data Protection Legislation, as applicable. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the Processing of Customer Personal Data as well as the risks to individuals) the Security Measures implemented and maintained by Supplier as set out in Section 13 (Supplier’s Security Measures) and Appendix 2 provide a level of security appropriate to the risk in respect of the Customer Data.
Customers Security Responsibilities and Assessment. ▪ 7.3.1. Customer’s Security Responsibilities. Customer agrees that, without prejudice to Google’s obligations under Section 7.1 (Google’s Security Measures, Controls and Assistance) and Section 7.2 (Data Incidents): ▪ (a) Customer is solely responsible for its use of the Services, including: ▪ (i) making appropriate use of the Services and the Additional Security Controls to ensure a level of security appropriate to the risk in respect of the Customer Data; ▪ (ii) securing the account authentication credentials, systems and devices Customer uses to access the Services; and ▪ (iii) retaining copies of its Customer Data as appropriate; and ▪ (b) Google has no obligation to protect copies of Customer Data that Customer elects to store or transfer outside of Google’s and its Subprocessors’ systems (for example, offline or on-premise storage), or to protect Customer Data by implementing or maintaining Additional Security Controls except to the extent Customer has opted to use them.
Customers Security Responsibilities and Assessment. The Customer agrees that, without prejudice to SiteGround’s obligations under Section 7. (Security Responsibilities of SiteGround) and other relevant Sections in this DPA: The Customer is solely responsible for their use of the Services, including: making appropriate use of the Services to ensure a level of security suitable to the risk in respect of the Customer Data; securing the account authentication credentials, systems, and devices the Customer uses to access the Services; ensuring that all programs, scripts, addons, plugins and other software installed on the account are secure and their utilization does not impose any security risk in respect to the Customer Data and the account itself; securing all installed programs, scripts, addons, plugins and other software, their configuration and their regular maintenance; any content of the account; any actions and activity on the account; and backing up their Customer Data; and SiteGround has no obligation to protect Customer Data that the Customer chooses to store or transfer outside of SiteGround’s and its Sub - processors’ systems (for example, offline or on-premise storage), or to protect Customer Data by implementing or maintaining Additional Security Controls except to the extent the Customer has opted to use them. The Customer is solely responsible for reviewing the documentation and evaluating whether the Services, the Security Measures, SiteGround’s commitments under this Section and the following meet the Customer’s needs, including any security obligations of the Customer under the European Data Protection Legislation and/or Non-European Data Protection Legislation, as applicable. The Customer acknowledges and agrees that (taking into account the costs of implementation and the nature, scope, context and purpose of processing of Customer data as well as the risks to individuals) the Security Measures implemented and maintained by SiteGround as set out in Section 7.1. provide the needed level of security appropriate to the risk in respect to the Customer Data. It is the Customer's responsibility to backup Customer Data and all data and consent stored within the account in order to prevent potential data loss. SiteGround Backup Services are provided "as-is" and are subject to all limitations of liability set out in the applicable Agreement. Even if the Customer purchases Backup Services, they agree that they will maintain their own set of backups independent of those that SiteGround maintains and ...
AutoNDA by SimpleDocs
Customers Security Responsibilities and Assessment 

Related to Customers Security Responsibilities and Assessment

  • Patent Filing Responsibilities and Costs 1. The invention and patent rights herein apply to any patent application or patents covering an invention made under this Agreement. Each Party is responsible for its own costs of obtaining and maintaining patents covering sole inventions of its employees. The Parties may agree otherwise, upon the reporting of any invention (sole or joint) or in any license granted. 2. Partner shall include the following in patent applications for an invention made jointly between NASA employees, its Related Entity employees and Partner employees: The invention described herein may be manufactured and used by or for the U.S. Government for U.S. Government purposes without the payment of royalties thereon or therefore.

  • Customer’s Responsibilities 9.1 If and to the extent applicable or under the control of the Customer, Customer shall provide complete and accurate information regarding requirements for the Project and the Site(s), including, without limitation, constraints, space requirements, underground or hidden facilities and structures, and all applicable drawings and specifications. 9.2 Customer shall prepare, file for, and use commercially reasonable efforts to obtain all Required Approvals necessary to perform its obligations under this Agreement. 9.3 Customer shall reasonably cooperate with Company as required to facilitate Company’s performance of the Work.

  • Reporting Responsibilities The IRA Owner agrees to provide the Custodian with information necessary for the Custodian to prepare any reports required under Code Sections 408(i), 408A(d)(3)(D), and Regulations Sections 1.408-5 and 1.408-6. The Custodian agrees to submit reports to the IRS and the IRA Owner (or Beneficiary(ies) upon the IRA Owner’s death) as prescribed by the IRS and such additional reports as the Custodian may choose to deliver. The Custodian shall furnish annual calendar-year reports concerning the status of the IRA and such information concerning required minimum distributions as is prescribed by the Commissioner of the IRS.

  • Responsibilities of Customer 5.1 To the extent that the Supplier requires access to the Customer Site to perform the Services, the Customer shall provide such access during Normal Business Hours and to provide a suitable work environment to enable the Supplier to perform such Services subject to the Supplier complying with such internal policies and procedures of the Customer (including those relating to security and health and safety) as may be notified to the Supplier in writing from time to time. 5.2 The Customer shall co-operate with the Supplier in all matters relating to the Services and shall appoint a Representative (“Customer Representative”), who shall have authority to commit the Customer on all matters relating to the relevant Service. 5.3 The Customer agrees and acknowledges the terms of the applicable Licence Agreements, Customer Agreement and that such terms shall form part of this Agreement. For the avoidance of doubt, in the event the applicable Licence Agreements and/or Customer Agreement is not applicable to the Services being received or delivered by the Supplier to the Customer under this Agreement, such agreements shall not apply. 5.4 Customer shall; (a) adhere to the Acceptable Use Policy; (b) be a bona fide licenced user of all Third-Party Software used in the provision of the Services; (c) co-operate with the Supplier in all matters relating to the Services as reasonably requested by the Supplier; (d) adhere to the dates scheduled for provision of Services by the Supplier to the Customer as stated in the applicable Statement of Work or otherwise agreed between the Parties in writing. In the event the Customer wishes to reschedule or cancel the dates for the provision of Services, liquidated damages (“Liquidated Damages”) will become payable from the Customer to Supplier on the following basis: (i) If dates are changed or cancelled at the Customer’s request more than 14 days before the scheduled start date no Liquidated Damages are payable. (ii) If dates are changed or cancelled between 7 days and 14 days before the scheduled start date Liquidated Damages equivalent to 50% of the Fees for the Services to be provided at that time will be payable. (iii) If dates are changed or cancelled less than 7 days before the scheduled start date Liquidated Damages equivalent to 100% of the Fees for the Services to be provided at that time will be payable. (e) inform the Supplier of all health and safety rules and regulations and any other reasonable security requirements that apply at any of the Customer’s premises; (f) in respect of any Microsoft funded services, sign and deliver the Microsoft Proof of Execution (XXX) within 7 days of the date of issue by Microsoft. In the event that the Customer does not return the XXX within the 7 days’ notice period, the Supplier may be entitled to charge the Customer the amounts directly and the Customer shall follow the payment terms in this Agreement.; (g) maintain continuous global admin access to the Customer’s relevant Microsoft (h) Where a Microsoft Cloud service is deployed / utilised within the project the Customer shall assign the Supplier to be the Digital Partner of Record for a minimum of twelve (12) months from project completion date; (i) provide appropriate hardware interface, software and access authorisation to enable remote diagnosis, should such capability be required; (j) provide all information and make available all resources as reasonably requested by Supplier in the execution of its obligations under this Agreement; (k) use all reasonable efforts to follow the reasonable instructions of Supplier support personnel with respect to the resolution of defects; (l) gather all relevant information prior to requesting assistance in respect of any defects including detailed defect description, and procedures required to replicate a problem if possible. Any additional information which may help in the diagnosis of a defect should be included such as network configuration details; (m) agree that if, in the course of performing the Services, it is reasonably necessary for the Supplier’s performance of its obligations under a Statement of Work for Supplier to access or use any equipment, software or data of the Customer (or which is in the possession of the Customer) then it shall where it is able to do so grant to Supplier a non-exclusive, royalty free, terminable licence to use the same solely for the purpose of delivering the Services only for as long as is strictly necessary to deliver such Services; and (n) provide network and user access between Customer’s and Supplier’s data centres. 5.5 To the extent that the Supplier requires access to the Customer’s Operating Environment to perform the Dedicated Support, the Customer shall use reasonable endeavours to provide such access during Normal Business Hours and to provide a suitable work environment to enable the Supplier to perform such Dedicated Support subject to the Supplier complying with such internal policies and procedures of the Customer (including those relating to security and health and safety) as may be notified to the Supplier in writing from time to time. 5.6 The Customer shall (unless otherwise specified in the Statement of Work or as otherwise set out in this Agreement): (a) use the Services only for lawful purposes and in accordance with this Agreement; (b) keep secure from third parties any passwords issued to the Customer by the Supplier; (c) install or, permit the Supplier to install, the current version of software required to provide the Dedicated Support from time to time when upgrades or fixes occur and to provide a reasonable level of assistance in implementation and testing; (d) provide notice of intention to change applicable Customer-side Equipment or Customer Operating Environment or data-feeds that will directly impact the Dedicated Support; (e) comply with all applicable laws and regulations with respect to its activities under this Agreement, including those set out in Clause 20; (f) carry out all other Customer responsibilities set out in this Agreement and the Statement of Work in a timely and efficient manner. In the event of any delays in the Customer's provision of such assistance as agreed by the Parties, the Supplier may adjust any timetable or delivery schedule set out in this Agreement as reasonably necessary; (g) use the Third-Party Software and/or Software correctly in accordance with its operating instructions; (h) notify Supplier promptly of any problems with the Third-Party Software and/or Software; and (i) use only versions of the Third-Party Software and/or Software covered by Microsoft in mainstream or extended support unless otherwise agreed in writing. 5.7 In the event that the Customer is in breach of its obligations under the Agreement (excluding payment obligations) then the Supplier shall provide written notice of such breach, specifying in detail the nature of the breach and providing thirty (30) Business Days’ notice to remedy such breach if capable of remedy. If the Customer fails to remedy such breach the Supplier shall be entitled to terminate or suspend the Services without prejudice to any pre-existing rights and obligations of either Party. The Supplier shall have no liability or responsibility should the Services fail to comply with the Statement of Work and/or Service Level Agreements as a direct result of the Customer (including without limitation any of its employees, subcontractors or any of its staff) being in breach of the Agreement. 5.8 In the event that the Customer is in breach of its payment obligations under the Agreement then the Supplier shall provide written notice of such breach, specifying in detail the nature of the breach and providing thirty (30) days notice to remedy such breach if capable of remedy. If the Customer fails to remedy such breach the Supplier shall be entitled to terminate or suspend the Services without prejudice to any pre- existing rights and obligations of either Party. The Supplier shall have no liability or responsibility should the Services fail to comply with the Statement of Work and/or Service Level Agreements as a direct result of the Customer (including without limitation any of its employees, subcontractors or any of its staff) being in breach of the Agreement.

  • Contractor Responsibilities 19.1. Contractor shall perform national criminal history checks for Ohio, Indiana, and Kentucky, and 10-panel drug screening tests on all prospective employees performing work under this RFP or coming onto a CMHA property and any resulting contract and provide summaries of the results to the Authority if requested. For the purposes of this section, the term “employees” includes contractor. Prospective employees whose criminal background check discloses a misdemeanor or felony involving crimes of moral turpitude, sexual offenses or harm to persons or property shall not be employed to perform work under this RFP or any resulting contract. Contractor is required to perform drug screening of all employees and to ensure acceptable test results. Criminal history and drug screening checks will be completed at the sole expense of the contractor. Any employee of the Contractor suspected of being under the influence of drugs and or alcohol will be reported to the appropriate personnel at CMHA and/or other local law enforcement. If the employee is determined to be under the influence of drugs or alcohol in any form or manner, or believed by proper authority to be dealing in illicit sale of alcohol or drugs they will be removed and shall not be allowed to return to any job site on the Authority’s property. The Contractor’s contract may be suspended and/or terminated should such a situation occur or if the Contractor fails to submit results pursuant to this section. 19.1.1. If CMHA requests additional drug screening, the test shall be performed within 24 hours and the summary shall be sent directly to CMHA from the testing facility. 19.2. Contractor(s) shall provide uniforms and ID Badges identifying Contractor for all employees working on CMHA’s properties. No employees will be allowed on CMHA’s properties out of uniform and without his/her ID badge on his/her person. Contractor(s) must submit a picture of the uniform and a sample of his/her ID badge if requested by CMHA. 19.3. Contractor’s personnel shall be neat and conduct all work in a professional and efficient manner. If any employee of Contractor is deemed unacceptable by CMHA, Contractor shall immediately replace such personnel with an acceptable substitute to CMHA. 19.4. Contractor(s) shall practice acceptable safety precautions so as not to cause harm to any persons or property while performing services under this RFP or any resulting contract. Contractor(s) shall follow industry safety standards, and use only industry approved safety equipment in accordance with the manufacturer’s specifications in the performance of all duties. 19.5. Contractor(s) shall pay all of its employees, including any and all approved Sub-Contractors, at least the legal minimum wages as determined by the United States Department of Labor and the United States Department of Housing and Urban Development and Department of Labor Prevailing Wage. Wage Determinations can be accessed via the Department of Labor website, xxx.xxxx.xxx. 19.6. Upon completion of the work, Contractor(s) shall clean up the area where the work was performed and Contractor(s) shall remove any debris generated by the products and/or services at CMHA premises. At no time, will Contractor(s) discard debris into any CMHA refuse container. 19.7. Contractor(s) shall clearly mark all work areas that might reasonably be expected to endanger the health and safety of residents, guests, or any other persons. Contractor(s) will provide such signs, markers and barricades as required to identify all work areas and minimize inherent dangers. 19.8. The contractor shall be responsible for notifying CMHA immediately of any damages (i.e. fire, container leaking) deemed to be a health or safety hazard whether the damage is caused by the contractor or other means. 19.9. The Contractor shall be responsible for safeguarding all CMHA property provided for Contractor use. At the close of each workday, CMHA facilities, property and materials shall be inspected and secured.

  • Responsibilities of Contractor A. The Contractor shall perform all work on the described project as required by the Contract documents. The work to be performed includes the labor and services necessary to produce such replacement, and all materials, supplies, tools, transportation, equipment, and machinery required for replacement. B. This project bid includes all materials, labor and equipment to complete the reconstruction and resurfacing of streets as outlined in the Project Manual for WWREYN - XXXXXXXX SANITARY SEWER - PHASE 1 dated March 25th, 2021 as outlined in Attachment A.

  • Vendor Responsibilities Note: NO EXCEPTIONS OR REVISIONS WILL BE CONSIDERED IN C-M, O-S, V-W. Indemnification

  • Responsibilities of Client a. Client shall exclusively retain the services of Consultant to perform the Scope of Work, in accordance with, and subject to, the other provisions of this Agreement. b. Client shall provide access for Consultant and its subcontractors to the Site, and shall enter into access agreements with other third party property owners, as necessary for Consultant to complete the performance of the Scope of Work. c. Client shall, as necessary to complete the Scope of Work: (i) cooperate and assist Consultant with the preparation and submittal, to PADEP, PAUSTIF, local governing authorities and others, of all information and documents including, without limitation, correspondence, notices, reports, data submittals, restrictive covenants, engineering and institutional controls, and the like; and (ii) implement and maintain any engineering or institutional controls. d. Client shall transmit to Consultant copies of all documentation, correspondence, reports, and the like, sent or received by Client, regarding the Scope of Work at the Site. e. Client shall make a good faith effort to minimize any and all interference with the progress of the Scope of Work if the Site is remodeled or otherwise modified. Client shall also make a good faith effort to place this condition on third parties that are not a party to this Agreement including, but not limited to, current owners, future owners, current operators, future operators, current lessees and future lessees.

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

  • User Responsibilities i. Users are required to follow good security practices in the selection and use of passwords; ii. Users shall ensure that unattended equipment is protected; and iii. Users shall adopt a clear desk policy for papers and removable storage media and a clear screen policy for information processing facilities.

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