Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-‐to-‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work.
4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work.
4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged.
4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents.
4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents.
4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof.
4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals.
4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Agreement with Respect to Leased Data Processing Equipment (a) The Receiver hereby grants to the Assuming Bank an exclusive option for the period of ninety (90) days commencing the day after Bank Closing to accept an assignment from the Receiver of any or all Data Processing Leases to the extent that such Data Processing Leases can be assigned.
(b) The Assuming Bank shall (i) give written notice to the Receiver within the option period specified in Section 4.7(a) of its intent to accept or decline an assignment or sublease of any or all Data Processing Leases and promptly accept an assignment or sublease of such Data Processing Leases, and (ii) give written notice to the appropriate lessor(s) that it has accepted an assignment or sublease of any such Data Processing Leases.
(c) The Receiver agrees to facilitate the assignment or sublease of Data Processing Leases or the negotiation of new leases or license agreements by the Assuming Bank; provided, that neither the Receiver nor the Corporation shall be obligated to engage in litigation or make payments to the Assuming Bank or to any third party in connection with facilitating any such assumption, assignment, sublease or negotiation.
(d) The Assuming Bank agrees, during its period of use of any property subject to a Data Processing Lease, to pay to the Receiver or to appropriate third parties at the direction of the Receiver all operating costs with respect thereto and to comply with all relevant terms of the applicable Data Processing Leases entered into by the Failed Bank, including without limitation the timely payment of all rent, taxes, fees, charges, utilities, insurance and assessments.
(e) The Assuming Bank shall, not later than fifty (50) days after giving the notice provided in Section 4.7(b), (i) relinquish and release to the Receiver all property subject to the relevant Data Processing Lease, in the same condition as at Bank Closing, normal wear and tear excepted, or (ii) accept an assignment or a sublease thereof or negotiate a new lease or license agreement under this Section 4.7.
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:
(1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute;
(2) Limit unsuccessful logon attempts;
(3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions;
(4) Authorize wireless access prior to allowing such connections;
(5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity;
(6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions;
(7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles;
(8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services;
(9) Enforce a minimum password complexity and change of characters when new passwords are created;
(10) Perform maintenance on organizational systems;
(11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance;
(12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1;
(13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital;
(14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse;
(15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas;
(16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems;
(17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems;
(18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception);
(19) Protect the confidentiality of Student Data at rest;
(20) Identify, report, and correct system flaws in a timely manner;
(21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems;
(22) Monitor system security alerts and advisories and take action in response; and
(23) Update malicious code protection mechanisms when new releases are available.
Operator Materials Operator retains all right, title and interest in and to any and all of Operator’s software, materials, tools, forms, documentation, training and implementation materials and intellectual property (“Operator Materials”). Operator grants to the LEA a personal, nonexclusive license to use the Operator Materials for its own non-commercial, incidental use as set forth in the Service Agreement. Operator represents that it has all intellectual property rights necessary to enter into and perform its obligations in this DPA and the Service Agreement, warrants to the District that the District will have use of any intellectual property contemplated by the Service Agreement free and clear of claims of any nature by any third Party including, without limitation, copyright or patent infringement claims, and agrees to indemnify the District for any related claims.
PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:
SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.
11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses.
11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.
COVID-19 Employees of Contractor and/or persons working on its behalf, including, but not limited to, subcontractors (collectively, “Contractor Personnel”), while performing services under this Agreement and prior to interacting in person with City employees, contractors, volunteers, or members of the public (collectively, “In-Person Services”) must be fully vaccinated against the novel coronavirus 2019 (“COVID-19”). “Fully vaccinated” means that 14 or more days have passed since Contractor Personnel have received the final dose of a two-dose COVID-19 vaccine series (Moderna or Pfizer-BioNTech) or a single dose of a one-dose COVID-19 vaccine (Xxxxxxx & Xxxxxxx/Xxxxxxx) and all booster doses recommended by the Centers for Disease Control and Prevention. Prior to assigning Contractor Personnel to perform In-Person Services, Contractor shall obtain proof that such Contractor Personnel have been fully vaccinated. Contractor shall retain such proof for the document retention period set forth in this Agreement. Contractor shall grant medical or religious exemptions (“Exemptions”) to Contractor Personnel as required by law. If Contractor wishes to assign Contractor Personnel with Exemptions to perform In- Person Services, Contractor shall require such Contractor Personnel to undergo weekly COVID-19 testing, with the full cost of testing to be borne by Contractor. If Contractor Personnel test positive, they shall not be assigned to perform In-Person Services or, to the extent they have already been performing In-Person Services, shall be immediately removed from those assignments. Furthermore, Contractor shall immediately notify City if Contractor Personnel performing In-Person Services (1) have tested positive for or have been diagnosed with COVID-19, (2) have been informed by a medical professional that they are likely to have COVID-19, or (3) meet the criteria for isolation under applicable government orders.
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
