Incident Reporting Sample Clauses

Incident Reporting. USAC and SERVICE PROVIDER agree to report and track incidents in accordance with the PII breach reporting requirements as set forth in Office of Management and Budget (“OMB”) Memorandum M-17-12, “Preparing for and Responding to a Breach of Personally Identifiable Information” (2017). SERVICE PROVIDER will promptly notify these contacts at USAC simultaneously: USAC Privacy, ▇▇▇▇▇▇▇@▇▇▇▇.▇▇▇. USAC IT Security Operations, ▇▇▇▇▇▇▇▇@▇▇▇▇.▇▇▇. USAC will promptly notify this contact at SERVICE PROVIDER: SERVICE PROVIDER [TO FILL OUT] As soon as possible after notifying SERVICE PROVIDER of an incident, or receiving notification of an incident from SERVICE PROVIDER, USAC will notify the FCC’s Network Security Operations Center (“NSOC”) at ▇▇▇▇-▇▇▇▇▇▇▇@▇▇▇.▇▇▇ or (▇▇▇) ▇▇▇-▇▇▇▇ of incidents within one (1) hour of notification. If the Party experiencing the incident cannot contact the other Party’s System Security Contacts within one (1) hour, or if contacting the System Security Contact is not practical, then this contact information shall be used: USAC Manager of Security Operations - (▇▇▇) ▇▇▇-▇▇▇▇ SERVICE PROVIDER [TO FILL OUT] USAC and SERVICE PROVIDER agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The Party that experienced the incident will also be responsible for following its internal established procedures, including: Notifying the proper organizations (e.g., Information Systems Security Officers (ISSOs”), and other contacts listed in this document); Conducting a breach and risk analysis, and making a determination of the need for notice and/or remediation to individuals affected by the loss; and Providing such notice and credit monitoring at no cost to the other Party, if the analysis conducted by the Party having experienced the loss incident indicates that individual notice and credit monitoring are appropriate. In the event of any incident arising from or in connection with this Agreement, each Party will be responsible only for costs and/or litigation arising from a breach of the Party’s own systems; USAC is responsible only for costs and litigation associated with breaches to USAC systems and SERVICE PROVIDER is responsible only for breaches associated with SERVICE PROVIDER systems. USAC shall not be liable to SERVICE PROVIDER or to any third person for any cause of action arising from the possession, control, ...

Incident Reporting. (1) The Provider must develop and implement processes for defining, recording, and resolving incidents and adverse events that include an internal documented reporting process that enables the early identification of any incidents and adverse event trends and the appropriate corrective and preventive strategies available.

Incident Reporting. Transfer Agent will use commercially reasonable efforts to promptly furnish to Fund information that Transfer Agent has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

Incident Reporting. The Construction Manager shall immediately notify the County and Professional, both orally and in writing, of the nature and details of all incidents which may adversely affect the quality or progress of the Work including, but not limited to, union jurisdictional disputes, accidents, delays, damages to Work and other significant occurrences.

Incident Reporting. 6.1.1. Business Associate shall report to Covered Entity the following: 6.1.1.1. Any use or disclosure of PHI which is not in compliance with the terms of this Agreement or applicable law of which it becomes aware; and 6.1.1.2. Any security incident of which it becomes aware. For purposes of this Agreement, “security incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system. 6.1.2. Within 24 hours of discovery of a suspected reportable incident as described in 6.1.1 above, Business Associate shall notify Covered Entity of the existence and nature of the incident as understood at that time. Business Associate shall immediately investigate the incident and within 72 hours of discovery shall provide Covered Entity, in writing, a report describing the results of Business Associate’s investigation, including: 6.1.2.1. What data elements were involved, the extent of the data involved in the incident, and the identification of affected individuals, if applicable; 6.1.2.2. A description of the unauthorized persons known or reasonably believed to have improperly used or disclosed PHI, or to have been responsible for the incident; 6.1.2.3. A description of where the PHI is believed to have been improperly transmitted, sent, or utilized, if applicable; 6.1.2.4. A description of the probable causes of the incident; 6.1.2.5. A description of the proposed plan for preventing similar future incidents, including ongoing risk remediation plan approval; and 6.1.2.6. Whether the Associate believes any federal or state laws requiring notifications to individuals are triggered. 6.1.3. Reporting and other communications made to the Covered Entity under this section must be made to the agency’s HIPAA privacy officer at: Ohio Department of Administrative Services Office of Legal Services ▇▇ ▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇▇, ▇▇▇▇ ▇▇▇▇▇ Main: (▇▇▇) ▇▇▇-▇▇▇▇ Direct: (▇▇▇) ▇▇▇-▇▇▇▇ Fax: ▇▇▇.▇▇▇.▇▇▇▇

Incident Reporting. 1.10.1 Users shall immediately report any unusual activity, incident or suspected event following Avangrid incident reporting procedures (e.g. Service (Help) Desk, REPORTER, etc.)

Incident Reporting. Pursuant to Rule 63F-11.001-006, Florida Administrative Code (F.A.C.), Central Communications Center (CCC), the Provider shall comply with all Department incident reporting requirements as outlined in the Department’s incident reporting policy and procedure (FDJJ–2020 and 2020P, Revised 4/20/16). The Provider shall develop an internal numbering process for all incident reports to ensure that all reports are present and maintained in accordance with Department policy, including implementation of a written Arrest Reporting procedure requiring all owners, operators, directors, caretaker/direct contact staff, and subcontracted staff, who have been arrested for any criminal offense to make a report of their arrest, either written or oral, to their immediate supervisor and the CCC within two (2) hours (pending availability/release from jail) per the CCC Rule that requires the arrested staff member to report the arrest to the CCC within two (2) hours pending availability/release from jail.

Incident Reporting. The Employer shall notify CUPE of the submission of any injury/incident reports in which an employee identifies their employee group as CUPE.

Incident Reporting. 13.1 As soon as the Contractor becomes aware, it shall immediately report any incident affecting the delivery of the Service(s) to the Framework Public Body. The Contractor will undertake an immediate investigation and will provide feedback in writing on findings, including corrective actions required and trends observed, to the Framework Public Body within 24 hours of the incident being reported by telephone/e-mail. 13.2 Serious incidents can be categorised as but not limited to:  Any breach of security which may affect the security of data supplied by the Framework Public Body to the Contractor;  Failure to deliver the required Services due to any type of service disruption. 13.3 These examples are indicative only and the Framework Public Body may provide for further categories of serious incidents at the call-off level. 13.4 The Contractor shall, in the event of a serious incident, provide from within Contractor’s senior management, a single point of contact person within 1 hour of notification. 13.5 It shall be the responsibility of the contact person to pursue the investigation and mitigation of the incident to the satisfaction of the Framework Public Body and they shall be required to provide progress updates to the Framework Public Body on request. 13.6 In addition to the above notification requirements, the Contractor shall have in place an effective and efficient incident handling procedure for dealing with security breaches in the provision of Service(s) to the Framework Public Body and these should be agreed by the Framework Public Body and Contractor in advance. As a minimum it must include but not be limited to:  Early identification of any loss of data;  Early notification to Framework Public Body on any security breaches;  Set procedures in place to conduct thorough premises searches;  Ability to provide immediate feedback on investigations to Framework Public Body contacts that may be requested at any time from the notification;  Internal escalation procedures in place to notify senior Contract Managers and Security Managers;  Ability within workforce planning to provide on-site management and assistance to ascertain the causes of the security breach and implement any immediate remedial actions in mitigation;  Final reporting writing procedures in agreement with the Framework Public Body;  Full co-operation with any requests for written reports and information pertaining to security incidents that may be requested by the Informati...