Subscriber’s Security Responsibilities and Assessment of Sightengine. 3.3.1. Subscriber agrees that, without prejudice to Sightengine’s obligations under Section 3.1 (Security Measures) and Section 3.2 (Data Incidents):
Subscriber’s Security Responsibilities and Assessment of Sightengine Sample Clauses
Related to Subscriber’s Security Responsibilities and Assessment of Sightengine
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.
ADDITIONAL CONTRACTOR RESPONSIBILITIES 13 In addition to providing the services described in Paragraph 5 of this 14 Exhibit A, CONTRACTOR agrees to:
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.
FACILITY RESPONSIBILITIES (1) The Facility will retain responsibility for the care of its clients and will maintain administrative and professional supervision of students insofar as their presence and program assignments affect the operation of the Facility and its care, direct and indirect, of its clients. No provision of this MOU shall prevent any Facility client from requesting not to be a teaching client or prevent any member of the Facility’s staff from designating any client as a non-teaching client.
Responsibilities of Covered Entity With regard to the use and/or disclosure of PHI by the Business Associate, Covered Entity hereby agrees:
Contractor Responsibility and Debarment 14.1 A responsible contractor is a contractor who has demonstrated the attribute of trustworthiness, as well as quality, fitness, capacity and experience to satisfactorily perform the contract. It is the COUNTY’s policy to conduct business only with responsible contractors.
Engineer Responsibilities No subcontract relieves the Engineer of any responsibilities under this contract.
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.
User Responsibilities i. Users are required to follow good security practices in the selection and use of passwords;
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.
