Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.
Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
CLEARANCE PATTERNS 7.1 The State shall develop separate clearance patterns for each of the following:
Substance Abuse Treatment Information Substance abuse treatment information shall be maintained in compliance with 42 C.F.R. Part 2 if the Party or subcontractor(s) are Part 2 covered programs, or if substance abuse treatment information is received from a Part 2 covered program by the Party or subcontractor(s).
System Security and Data Safeguards When SAP is given access to Licensee’s systems and data, SAP shall comply with Licensee’s reasonable administrative, technical, and physical safeguards to protect such data and guard against unauthorized access. In connection with such access, Licensee shall be responsible for providing Consultants with user authorizations and passwords to access its systems and revoking such authorizations and terminating such access, as Licensee deems appropriate from time to time. Licensee shall not grant SAP access to Licensee systems or personal information (of Licensee or any third party) unless such access is essential for the performance of Services under the Agreement. The parties agree that no breach of this provision shall be deemed to have occurred in the event of SAP non-conformance with the aforementioned safeguard but where no personal information has been compromised.
Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.
Prohibition Against Selecting and Installing Products Containing Hazardous Materials The Contractor shall not select, install or otherwise incorporate any products or materials containing Hazardous Materials within the boundaries of the Site. Should the Contractor or any Subcontractors have knowledge that, or believe that, an item, component, material, substance, or accessory within a product or assembly selected by the Contractor or any Subcontractor may contain Hazardous Materials it is the Contractor’s responsibility to secure a written certification from the manufacturer of any suspected material which identifies the specific Hazardous Material(s) contained, together with the Material Safety Data Sheets (MSDS) for such materials which shall be submitted to the Owner and Design Professional.
Workplace Violence Prevention A. In order to provide a safe and healthy workplace for employees, the State agrees to develop and implement "Workplace Violence Prevention" policies and programs.
Anti-‐Abuse Registry Operator may suspend, delete or otherwise make changes to domain names in compliance with its anti-‐abuse policy.
Anti-Boycott Verification To the extent this Agreement constitutes a contract for goods or services within the meaning of Section 2270.002 of the Texas Government Code, as amended, solely for purposes of compliance with Chapter 2270 of the Texas Government Code, and subject to applicable Federal law, the Developer represents that neither the Developer nor any wholly owned subsidiary, majority-owned subsidiary, parent company or affiliate of Developer (i) boycotts Israel or (ii) will boycott Israel through the term of this Agreement. The terms “boycotts Israel” and “boycott Israel” as used in this paragraph have the meanings assigned to the term “boycott Israel” in Section 808.001 of the Texas Government Code, as amended.
