E1 Authority Data E1.1 For the purposes of clauses E1 and 2, the terms “Data Controller”, “Data Processor”, “Data Subject”, “
CHILD AND DEPENDENT ADULT/ELDER ABUSE REPORTING CONTRACTOR shall establish a procedure acceptable to ADMINISTRATOR to ensure that all employees, agents, subcontractors, and all other individuals performing services under this Agreement report child abuse or neglect to one of the agencies specified in Penal Code Section 11165.9 and dependent adult or elder abuse as defined in Section 15610.07 of the WIC to one of the agencies specified in WIC Section 15630. CONTRACTOR shall require such employees, agents, subcontractors, and all other individuals performing services under this Agreement to sign a statement acknowledging the child abuse reporting requirements set forth in Sections 11166 and 11166.05 of the Penal Code and the dependent adult and elder abuse reporting requirements, as set forth in Section 15630 of the WIC, and shall comply with the provisions of these code sections, as they now exist or as they may hereafter be amended.
Balancing Authority Area Notification At least three months before Initial Synchronization Date, the Interconnection Customer shall notify the CAISO and Participating TO in writing of the Balancing Authority Area in which the Large Generating Facility intends to be located. If the Interconnection Customer intends to locate the Large Generating Facility in a Balancing Authority Area other than the Balancing Authority Area within whose electrically metered boundaries the Large Generating Facility is located, and if permitted to do so by the relevant transmission tariffs, all necessary arrangements, including but not limited to those set forth in Article 7 and Article 8 of this LGIA, and remote Balancing Authority Area generator interchange agreements, if applicable, and the appropriate measures under such agreements, shall be executed and implemented prior to the placement of the Large Generating Facility in the other Balancing Authority Area.
Authority Data The Contractor shall use the Authority Data only as necessary for the performance of its obligations under this Contract unless otherwise authorised in writing by the Authority.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:
System Security Review All systems processing and/or storing DHCS PHI or PI must have at least an annual system risk assessment/security review which provides assurance that administrative, physical, and technical controls are functioning effectively and providing adequate levels of protection. Reviews should include vulnerability scanning tools.
Archival Back-Up and Disaster Recovery Licensee may use and copy the Product and related Documentation in connection with: i) reproducing a reasonable number of copies of the Product for archival backup and disaster recovery procedures in the event of destruction or corruption of the Product or disasters or emergencies which require Licensee to restore backup(s) or to initiate disaster recovery procedures for its platform or operating systems; ii) reproducing a reasonable number of copies of the Product and related Documentation for cold site storage. “Cold Site” storage shall be defined as a restorable back-up copy of the Product not to be installed until and after the declaration by the Licensee of a disaster; iii) reproducing a back-up copy of the Product to run for a reasonable period of time in conjunction with a documented consolidation or transfer otherwise allowed herein. “Disaster Recovery” shall be defined as the installation and storage of Product in ready-to-execute, back-up computer systems prior to disaster or breakdown which is not used for active production or development.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
Client Authority If Client is an individual, Client represents that he or she is of the age of majority. If Client is a corporation, partnership or limited liability company, the person signing this Agreement for the Client represents that he or she has been authorized to do so by appropriate action. If this Agreement is entered into by a trustee or other fiduciary, the trustee or fiduciary represents that Advisor’s investment management strategies, allocation procedures, and investment advisory services are authorized under the applicable plan, trust, or law and that the person signing this Agreement has the authority to negotiate and enter into this Agreement. Client will inform Advisor of any event that might affect this authority or the propriety of this Agreement.
