Incident Management/Notification of Breach Sample Clauses

Incident Management/Notification of Breach. DST shall develop, implement and maintain an incident response plan that specifies actions to be taken when DST or one of its subcontractors if in DST’s discretion it is applicable to such subcontractor, suspects or detects that a party has gained material confirmed unauthorized access to Client Data or systems or applications containing any Client Data (the “Response Plan”). Such Response Plan shall include the following: i. Escalation Procedures - An escalation procedure that includes notification to senior managers and appropriate reporting to regulatory and law enforcement agencies, as applicable. This procedure shall provide for reporting of incidents that compromise the confidentiality of Client Data (including backed up data) to Client via telephone or email (and provide a confirmatory notice in writing as soon as practicable); provided that the foregoing notice obligation is excused for such period of time as DST is prohibited by law, rule, regulation or other governmental authority from notifying Client. ii. Incident Reporting - DST will use commercially reasonable efforts to promptly furnish to Client information that DST has regarding the general circumstances and extent of such unauthorized access to the Client Data.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs

Related to Incident Management/Notification of Breach

  • Notification of Breach During the term of this Agreement:

  • Providing Notice of Breaches 8.1 If Covered Entity determines that an impermissible acquisition, access, use or disclosure of PHI for which one of Business Associate’s employees or agents was responsible constitutes a Breach as defined in 45 CFR § 164.402, and if requested by Covered Entity, Business Associate shall provide notice to the individual(s) whose PHI has been the subject of the Breach. When requested to provide notice, Business Associate shall consult with Covered Entity about the timeliness, content and method of notice, and shall receive Covered Entity’s approval concerning these elements. The cost of notice and related remedies shall be borne by Business Associate. 8.2 If Covered Entity or Business Associate determines that an impermissible acquisition, access, use or disclosure of PHI by a Subcontractor of Business Associate constitutes a Breach as defined in 45 CFR § 164.402, and if requested by Covered Entity or Business Associate, Subcontractor shall provide notice to the individual(s) whose PHI has been the subject of the Breach. When Covered Entity requests that Business Associate or its Subcontractor provide notice, Business Associate shall either 1) consult with Covered Entity about the specifics of the notice as set forth in section 8.1, above, or 2) require, by contract, its Subcontractor to consult with Covered Entity about the specifics of the notice as set forth in section 8.1 8.3 The notice to affected individuals shall be provided as soon as reasonably possible and in no case later than 60 calendar days after Business Associate reported the Breach to Covered Entity. 8.4 The notice to affected individuals shall be written in plain language and shall include, to the extent possible, 1) a brief description of what happened, 2) a description of the types of Unsecured PHI that were involved in the Breach, 3) any steps individuals can take to protect themselves from potential harm resulting from the Breach, 4) a brief description of what the Business Associate is doing to investigate the Breach, to mitigate harm to individuals and to protect against further Breaches, and 5) contact procedures for individuals to ask questions or obtain additional information, as set forth in 45 CFR § 164.404(c). 8.5 Business Associate shall notify individuals of Breaches as specified in 45 CFR § 164.404(d) (methods of individual notice). In addition, when a Breach involves more than 500 residents of Vermont, Business Associate shall, if requested by Covered Entity, notify prominent media outlets serving Vermont, following the requirements set forth in 45 CFR § 164.406.

  • Notification of Termination 22.3.2.1 Upon the occurrence at District's sole determination of any of the above conditions, or upon Developer’s failure to perform any material covenant, condition or agreement in this Facilities Lease, District may, without prejudice to any other right or remedy, serve written notice upon Developer and its Surety of District's termination of this Facilities Lease and/or Developer’s right to perform the Work of this Facilities Lease. This notice will contain the reasons for termination. 22.3.2.2 Unless, within fifteen (15) days after the service of the notice, any and all condition(s) shall cease, and any and all violation(s) shall cease, or arrangement satisfactory to District for the correction of the condition(s) and/or violation(s) be made, this Facilities Lease and the Site Lease shall cease and terminate; provided, however, if the failure stated in the notice cannot be corrected within fifteen (15) days after the service of notice, District may consent to an extension of time, provided Developer instituted and diligently pursued corrective action within the applicable fifteen (15)-day period and until the violation is corrected. Upon District determination, Developer shall not be entitled to receive any further payment until the entire Work is finished. 22.3.2.3 Upon Termination, District may immediately serve written notice of tender upon Surety whereby Surety shall have the right to take over and perform this Facilities Lease only if Surety: 22.3.2.3.1 Within three (3) days after service upon it of the notice of tender, gives District written notice of Surety’s intention to take over and perform this Facilities Lease; and 22.3.2.3.2 Commences performance of this Facilities Lease within three (3) days from date of serving of its notice to District. 22.3.2.4 Surety shall not utilize Developer in completing the Project if the District notifies Surety of the District’s objection to Developer’s further participation in the completion of the Project. Surety expressly agrees that any developer which Xxxxxx proposes to fulfill Surety’s obligations is subject to District’s approval. 22.3.2.5 If Surety fails to notify District or begin performance as indicated herein, District may take over the Work and execute the Work to completion by any method it may deem advisable at the expense of Developer and/or its Surety. Developer and its Surety shall be liable to District for any excess cost or other damages the District incurs thereby. Time is of the essence in this Facilities Lease. If the District takes over the Work as herein provided, District may, without liability for so doing, take possession of and utilize in completing the Work all materials, appliances, plan, and other property belonging to Developer as may be on the Site of the Work, in bonded storage, or previously paid for.

  • Termination of Related Party Agreements Except as set forth on Schedule 9.7, all existing agreements between the Company and the Stockholders (and between the Company and entities controlled by the Stockholders) shall have been canceled effective prior to or as of the Consummation Date.

  • Notification of Event of Default Borrower shall notify Agent immediately of the occurrence of any Event of Default.

  • Event of Breach 7.1 The following circumstances shall be deemed Event of Default: 7.1.1 Pledgor’s any breach to any obligations under the Transaction Documents and/or this Agreement. 7.1.2 Party C’s any breach to any obligations under the Transaction Documents and/or this Agreement. 7.2 Upon notice or discovery of the occurrence of any circumstances or event that may lead to the aforementioned circumstances described in Section 7.1, Pledgor and Party C shall immediately notify Pledgee in writing accordingly. 7.3 Unless an Event of Default set forth in this Section 7.1 has been successfully resolved to Pledgee’s satisfaction within twenty (20) days after the Pledgee and /or Party C delivers a notice to the Pledgor requesting ratification of such Event of Default, Pledgee may issue a Notice of Default to Pledgor in writing at any time thereafter, demanding the Pledgor to immediately exercise the Pledge in accordance with the provisions of Section 8 of this Agreement.

  • Employee Notification A copy of any disciplinary action or material related to employee performance which is placed in the personnel file shall be provided to the employee (the employee so noting receipt, or the supervisor noting employee refusal to acknowledge receipt) or sent by certified mail (return receipt requested) to the employee's last address appearing on the Employer's records.

  • Termination for continuing Force Majeure Event Either Party may, by written notice to the other, terminate this Framework Agreement if a Force Majeure Event endures for a continuous period of more than one hundred and twenty (120) Working Days.

  • Written Notification Failing settlement at this level, the Union shall in writing notify the Employer of the alleged discrepancy and the names of the employees involved, and the period of time that such discrepancy is claimed to cover. Upon receipt of such written notice, the Employer agrees to promptly furnish the representative of the Union wage data pertaining to the alleged wage discrepancy.

  • Termination for Cause with Notice to Cure Requirement Contractor may terminate this contract for the Department’s failure to perform any of its duties under this contract after giving the Department written notice of the failure. The written notice must demand performance of the stated failure within a specified period of time of not less than 30 days. If the demanded performance is not completed within the specified period, the termination is effective at the end of the specified period.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!