Vermont breach notification lookup
Use this Vermont breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Vermont: statute citation, stated notification deadline, residents or regulators who may need notice, consumer-reporting-agency threshold, consumer-notice trigger, official source links, and the last verified date.
Last verified 2026-08-13. Not legal advice.
| Field | Verified value | Use in the incident file |
|---|---|---|
| Statute | 9 V.S.A. § 2435 | Link the decision record to the official citation |
| Deadline | Consumer notice no later than 45 days after discovery or notification; regulator preliminary notice within 14 business days of discovery or when consumer notice is provided, whichever is sooner; immediate owner/licensee notice for maintainers; consumer-reporting-agency notice applies for more than 1,000 consumers. | Sort multi-state response work by the shortest stated clock |
| Residents | Vermont consumers whose computerized personally identifiable information or login credentials were affected by a security breach, unless misuse is not reasonably possible and the statutory regulator determination notice is provided. | Identify whether affected residents receive notice |
| Regulator | Notify the Vermont Attorney General unless the entity is regulated by the Department of Financial Regulation; DFR-regulated entities notify DFR. Preliminary notice includes breach date, discovery date, and description within 14 business days or by consumer notice, whichever is sooner, followed by affected-consumer count and consumer notice copy. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify nationwide consumer reporting agencies without unreasonable delay when notice is provided to more than 1,000 consumers at one time, unless the entity is licensed or registered under Title 8 by the Department of Financial Regulation. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | Vermont requires regulator notice to the Attorney General or Department of Financial Regulation, as applicable, including preliminary notice within 14 business days of discovery or consumer notice, whichever is sooner. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Vermont fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
9 V.S.A. § 2435 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
Vermont requires regulator notice to the Attorney General or Department of Financial Regulation, as applicable, including preliminary notice within 14 business days of discovery or consumer notice, whichever is sooner. The consumer trigger matters because the clock usually starts only after a legally meaningful incident analysis, not merely because an IT alert appeared.
The last verified date for this Vermont lookup is 2026-08-13. Use that date as a prompt to refresh counsel review before making a live notification decision.
How to use it during an incident
Start with containment and evidence preservation, then identify affected resident states and compare the shortest stated deadline first.
A practical incident file should record discovery time, encryption status, systems involved, affected consumer count, vendor involvement, and the person responsible for counsel review.
For Vermont, the WISP should say where the notification decision log lives, who contacts counsel, who checks the regulator portal, and who approves any consumer notice before it is sent.
This lookup pairs with the Incident Response Plan because the plan owns the workflow: intake, escalation, containment, preservation, notice analysis, communications, and final review.
How it fits the WISP
A WISP should not guess at state-law outcomes; it should make the breach-review path fast, documented, and source-linked.
Pair this lookup with the Vermont WISP requirements page so the firm's written program names the state-aware incident path before an event happens.
Policywright keeps the breach clock separate from the policy packet: the lookup tells you what to review, while the generated packet assigns owners, evidence records, remediation steps, and review cadence.
Not legal advice. A qualified lawyer should confirm whether the incident facts meet a statutory definition, whether substitute notice or regulator notice applies, and whether another state or federal rule changes the timeline.
FAQ
Is this Vermont lookup legal advice?
No. It is a source-linked lookup for incident planning and should be reviewed with qualified counsel before relying on it in a live notification decision.
What if affected residents live outside Vermont?
Use the multi-state lookup page and include every state where affected residents may live. The comparison table sorts selected states by the shortest stated deadline first.
Does this replace the FTC Safeguards Rule notice analysis?
No. State notice review is separate from the federal Safeguards Rule and 16 CFR 314.4(j) analysis. A serious incident file should preserve both review tracks.