Common use of COORDINATING, REPORTING, AND RESPONDING TO BREACHES AND SECURITY INCIDENTS Clause in Contracts

COORDINATING, REPORTING, AND RESPONDING TO BREACHES AND SECURITY INCIDENTS. A. Reporting of Breach or Security Incident: If Supplier reasonably suspects or confirms a Breach and/or a Security Incident impacting Institutional Information and/or IT Resources, Supplier must promptly notify UC both orally and in writing using the contacts in the Agreement. Supplier must provide such notifications no later than (1) seventy-two (72) calendar hours after the initial suspicion of a Security Incident and/or Breach and (2) seventy-two (72) calendar hours after the initial confirmation of a Security Incident and/or Breach, if Supplier is able to make such a confirmation. Supplier’s notification must identify:

Appears in 5 contracts

Samples: Purchasing Agreement, Purchasing Agreement, www.omniapartners.com

AutoNDA by SimpleDocs

COORDINATING, REPORTING, AND RESPONDING TO BREACHES AND SECURITY INCIDENTS. A. Reporting of Breach or Security Incident: If Supplier reasonably suspects or confirms a Breach and/or a Security Incident impacting Institutional Information and/or IT Resources, Supplier must promptly notify UC both orally and in writing using the contacts in the Agreement. Supplier must provide such notifications no later than (1) seventy-two (72) calendar hours after the initial suspicion of a Security Incident and/or Breach and (2) seventy-two (72) calendar hours after the initial confirmation of a Security Incident and/or Breach, if Supplier is able to make such a confirmation. Supplier’s notification must identify: {{Int_es_:signer1:initials}} {{Int_es_:signer2:initials}} {{Int_es_:signer3:initials}}

Appears in 1 contract

Samples: Business Associate Agreement

AutoNDA by SimpleDocs
Time is Money Join Law Insider Premium to draft better contracts faster.