Your own breach reporting clock often starts when a vendor tells you about its incident, so the notice deadline in the vendor contract decides whether you can meet the regulator's deadline at all. Several US financial and health rules now put a specific notice duty on service providers, or require the regulated firm to impose one by contract: 72 hours under the SEC's amended Regulation S-P, "as soon as possible" for bank service providers under the US banking agencies' rule, 60 days for HIPAA business associates, and treatment of provider events as your own under NYDFS Part 500 and the NAIC model law. DORA adds contract content requirements for EU financial entities. This guide sets out who each rule covers, what the vendor must tell you and when, and how to write and test the clause. It is for third-party risk, procurement, legal and incident response teams. Status line: rules checked on 27 October 2026 against eCFR, SEC, NYDFS, NAIC and EUR-Lex texts. This guide is not legal advice.
Key takeaways
- The vendor clause sets your real deadline: under NYDFS Part 500 and the NAIC model law, a provider's incident is reportable by you, and under NAIC Section 6D your 72 hours can start the day after the provider tells you.
- Two rules name a vendor deadline directly: Regulation S-P requires policies ensuring service providers notify you no later than 72 hours after becoming aware of a breach; HIPAA business associates must notify within 60 calendar days of discovery.
- Bank service providers have their own duty: 12 CFR 53.4 requires notice to the bank "as soon as possible" for incidents that disrupt covered services for four or more hours.
- Contracts must also give you the facts: report contents in your own filings (data types, numbers affected, systems) only exist if the vendor is obliged to supply them.
- Write one clause stricter than all regimes: a 24-hour initial notice with staged updates satisfies every deadline above and leaves you time for your own filing.
Scope: who and what is covered
| Rule | Regulated party | Third party in scope | Mechanism |
|---|---|---|---|
| SEC Regulation S-P, 17 CFR 248.30 | Broker-dealers, investment companies, registered investment advisers and transfer agents ("covered institutions") | A service provider that receives, maintains, processes or is otherwise permitted access to customer information | Your policies must ensure the provider notifies you |
| US banking agencies' computer-security incident rule (OCC: 12 CFR Part 53) | National banks, federal savings associations, federal branches and agencies of foreign banks (OCC rule) | Bank service providers performing covered services | Direct duty on the provider |
| NYDFS 23 NYCRR 500.11 and 500.17(a) | DFS-licensed covered entities | Third-party service providers | Contract or diligence must address notice; you report provider incidents that affect you |
| NAIC Insurance Data Security Model Law (Model 668), Sections 4F and 6D | Insurance licensees in states that adopted it | Third-party service providers holding or accessing nonpublic information | You oversee the provider and report its events as your own |
| HIPAA Breach Notification Rule, 45 CFR 164.410 | Covered entities | Business associates | Direct duty on the business associate |
| FTC Safeguards Rule, 16 CFR 314.4(f) and (j) | Non-bank financial institutions under FTC jurisdiction | Service providers | Contractual safeguards and oversight; you notify the FTC |
| DORA, Regulation (EU) 2022/2554 | EU financial entities | ICT third-party service providers | Mandatory contract content |
For the regulator-facing deadlines across sectors see the Cyber Incident Reporting Requirements Map. This guide focuses on the vendor-to-customer leg.
Key obligations
| Rule | Vendor notice deadline | Trigger | Your downstream deadline |
|---|---|---|---|
| Reg S-P 248.30(a)(5)(i)(B) | As soon as possible, no later than 72 hours after becoming aware | Breach in security resulting in unauthorised access to a customer information system maintained by the provider | Notify affected individuals as soon as practicable, no later than 30 days after becoming aware of unauthorised access (248.30(a)(4)(iii)) |
| 12 CFR 53.4 | As soon as possible after determining the incident | Incident that has materially disrupted or degraded, or is reasonably likely to, covered services for four or more hours | Bank notifies the OCC as soon as possible and no later than 36 hours after determining a notification incident (53.3) |
| NYDFS 500.11 and 500.17(a) | Not fixed by the regulation: contracts or diligence must address notice of cybersecurity events | Cybersecurity event affecting the covered entity | Notify DFS no later than 72 hours after determining a cybersecurity incident occurred at the entity, an affiliate or a third-party service provider |
| NAIC Model 668 Section 6D | Not fixed; your clock starts the day after the provider notifies you or you have actual knowledge, whichever is sooner | Cybersecurity event involving the provider's systems | Notify the Commissioner no later than 72 hours after determination (Section 6A, where the conditions apply) |
| HIPAA 164.410(b) | Without unreasonable delay, no later than 60 calendar days after discovery | Breach of unsecured protected health information | Covered entity's notices to individuals, HHS and, where required, media |
| FTC Safeguards 314.4(j) | Not fixed by the rule; set by contract under 314.4(f) | Notification event affecting at least 500 consumers | Notify the FTC as soon as possible and no later than 30 days after discovery |
What the vendor must tell you
- HIPAA: 164.410(c) requires, to the extent possible, identification of each affected individual and any other available information the covered entity needs for its notices, at the time of notice or promptly afterwards.
- Bank service providers: 53.4 requires notice to at least one bank-designated contact, or, if none was given, to the bank's CEO and CIO or two people with comparable responsibilities. Previously communicated scheduled maintenance, testing or updates do not trigger notice.
- FTC Safeguards: your FTC notice must include the types of information involved, the date or date range, the number of consumers affected and a general description. Require the provider to give you those fields.
- NYDFS: 500.11 says contracts or diligence should address access controls including MFA, encryption, notice of cybersecurity events and cybersecurity representations and warranties.
- DORA: recitals 71 and 72 of the regulation describe contract provisions requiring the ICT provider to give assistance in ICT incidents at no additional cost or a cost set in advance, to observe notice periods and reporting obligations for developments that could materially affect its services, and to participate in threat-led penetration testing. See the DORA ICT Third-Party Risk and Register of Information Guide.
Timeline and current status
| Rule | Status at 27 October 2026 |
|---|---|
| Reg S-P amendments | Published in the Federal Register on 3 June 2024 (89 FR 47786). The SEC set compliance at 18 months after publication for larger entities and 24 months for smaller entities, so both compliance dates have now passed. See the SEC Regulation S-P Amendments Guide. |
| Banking agencies' incident rule | In force in 12 CFR Part 53 for OCC-supervised institutions. See the US Bank Computer-Security Incident Notification Rule Guide. |
| NYDFS Part 500 | 500.17 transition ended 30 days after the 1 November 2023 second amendment. |
| NAIC Model 668 | Model adopted in the fourth quarter of 2017; applies only where a state has enacted it, with state variations. See the NAIC Insurance Data Security Model Law Guide. |
| HIPAA 164.410 | In force. See the HIPAA Breach Notification Rule Guide. |
| DORA | Applies from 17 January 2025. |
Enforcement and penalties
- You carry the liability: in most of these regimes the regulator enforces against the regulated firm, so a slow vendor becomes your late filing. Under NYDFS 500.20 a material failure to comply for any 24-hour period is a violation.
- Direct vendor duties: HIPAA business associates and bank service providers have their own obligations under 164.410 and 53.4.
- Contract remedies: where the regulation is silent on the vendor deadline, your remedy is the contract: termination rights, indemnity and audit rights. See the Third-Party Security Contract Clauses Template.
What it means for AI agents and non-human identities
Many vendor breaches that reach customers travel through machine credentials: OAuth tokens, API keys and service accounts that the vendor holds into your tenant. The Salesloft Drift breach showed integration tokens stolen from one vendor being used against many customers' Salesforce instances. Notice clauses should therefore cover:
- Credential compromise as a trigger: any suspected exposure of credentials, tokens or keys that grant access to your systems or data, even before data access is confirmed.
- Credential inventory in the notice: which client IDs, keys, service accounts and scopes were affected, so you can revoke the right ones.
- Agent and sub-processor chains: where the vendor runs AI agents or fourth-party integrations with access to your data, events in those components count.
- Revocation support: a duty to rotate or revoke vendor-held credentials on request within hours.
See the OWASP NHI Top 10 NHI3 Vulnerable Third-Party NHI Guide and the Third-Party Access Guide.
Compliance steps
- Map regimes to vendors: for each vendor, record which rules apply (S-P, Part 53, Part 500, NAIC, HIPAA, FTC, DORA) based on the data and services involved.
- Set one house standard: initial notice within 24 hours of the vendor becoming aware of a suspected incident, an update at 72 hours, and a full report within 30 days, with a named contact list. This beats every deadline in the table.
- Define triggers broadly: suspected unauthorised access to systems holding your data, compromise of credentials into your environment, ransomware, and service disruption of four hours or more for banking services.
- Specify contents: data types, affected records or individuals, systems and credentials involved, timeline, containment steps, law enforcement status and a contact.
- Add cooperation terms: forensic information sharing, log retention, assistance at no or pre-agreed cost (the DORA recital language), and sub-processor flow-down.
- Remediate the back book: prioritise renewal amendments for vendors with privileged access or regulated data.
- Test it: include a vendor notification inject in tabletop exercises and check whether the contact list reaches a person within an hour. See the Third-Party Incident Response Playbook.
Sample clause wording
"[Supplier] shall notify [Customer] at [designated contacts] within 24 hours of becoming aware of any actual or reasonably suspected Security Incident affecting [Customer] Data, systems used to provide the Services, or credentials, tokens or keys that grant access to [Customer] environments. [Supplier] shall provide updates at least every 72 hours and a written report within 30 days, including the data categories and number of records or individuals affected, systems and credentials involved, timeline, containment and remediation steps, and law enforcement involvement. These obligations apply equally to incidents at [Supplier]'s subcontractors."
Decision guidance
- Large vendors refusing 24 hours: accept their standard terms only where they at least meet the strictest regime that applies to that service (for example 72 hours for S-P customer information systems), and record the residual risk.
- Small firms: use one clause across all vendors rather than regime-specific clauses; the operational overhead is lower and the strictest deadline covers the rest.
- Critical services: add a direct technical feed, such as security event webhooks or shared status pages, so you are not depending on email alone.
Framework mapping and metrics
| Element | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 |
|---|---|---|
| Supplier contract requirements | GV.SC-05 | SR-3, SA-9 |
| Supplier inclusion in incident planning | GV.SC-08 | IR-6, SR-8 |
| Supplier monitoring | GV.SC-07 | SA-9 |
- Share of critical vendors with a notice clause at or below 72 hours (target 100%).
- Share of vendors with a tested 24-hour contact path.
- Median hours from vendor awareness to your notification in real incidents.
- Vendor-held credentials into your environment with an owner and revocation runbook.
Common failure patterns
- "Without undue delay" and nothing else: clauses with no hour count give you no lever when the vendor waits for its own investigation to finish, and your 72-hour NYDFS or NAIC clock may already be running.
- Trigger limited to confirmed data loss: many incidents begin as credential exposure or unusual access. If the trigger is "confirmed breach of personal data", you hear last. The Snowflake breach involved customer credentials used against a platform, where the facts needed on both sides took time to establish.
- Stale contacts: the notice goes to a procurement mailbox or a departed relationship manager. 12 CFR 53.4 relies on a bank-designated contact for exactly this reason.
- No content obligation: the vendor tells you something happened but not which records, systems or credentials, so you cannot complete your own filing on time.
- Sub-processors outside the clause: the event happens at a fourth party and the contract only covers the vendor's own systems.
- Clause never tested: no exercise has ever checked that a vendor notice reaches incident response at 3 a.m. on a Sunday.
Practitioner checklist
- Inventory which notification regimes apply to each vendor relationship.
- Adopt a 24 hour initial, 72 hour update, 30 day final house standard.
- Include credential and token compromise as an explicit trigger.
- List required notice contents mapped to your own regulatory filings.
- For bank service providers, give each a designated contact as 12 CFR 53.4 expects.
- Confirm HIPAA business associate agreements match 164.410 timing and content.
- Flow the clause down to sub-processors and AI agent components.
- Exercise the vendor notice path at least annually.
Standards and references
- eCFR: 17 CFR 248.30 Regulation S-P procedures to safeguard customer information
- SEC: Regulation S-P amendments press release
- eCFR: 12 CFR Part 53 Computer-Security Incident Notification
- New York DFS: 23 NYCRR Part 500
- NAIC: Insurance Data Security Model Law (Model 668)
- eCFR: 45 CFR 164.410 Notification by a business associate
- eCFR: 16 CFR 314.4 Safeguards Rule elements
- EUR-Lex: Regulation (EU) 2022/2554 (DORA)
Related NHI Mgmt Group resources: Third-Party Risk Management Guide · Third-Party Security Contract Clauses Template · Cyber Incident Reporting Requirements Map · Third-Party Incident Response Playbook. This guide summarises third-party incident notification requirements and is not legal advice.