Lesson 11 of 12 · about 60 minutes · Updated November 14, 2026
Breach Notification: Federal, State and Idaho Law
You'll be able to
- Explain why breach notification is a separate job from incident response, with its own owners, deadlines and records
- Identify which state and federal notice rules apply to an organization and whose law governs each affected person
- State the key deadlines: Idaho's 24-hour agency rule, HIPAA's 60 days, the GLBA Safeguards Rule's 30 days, Regulation S-P, the bank 36-hour rule and Form 8-K Item 1.05
- Read Idaho Code 28-51-104 to 28-51-107, including the investigation duty, the safe harbors and the $25,000 penalty
- Run a multi-state notification process from discovery to the last letter, and keep the records that prove it was done right
- Tell the public records a reporter or advocate can use to track breaches in Idaho and nationally
Start here: the short version
- Every state, the District of Columbia, Guam, Puerto Rico and the U.S. Virgin Islands has a law that requires notice to people when certain personal information about them is breached.1 The law that applies is the law of the state where each affected person lives, so one incident at a national organization can trigger dozens of state laws at once.
- On top of the state laws sit federal sector rules with their own clocks: 60 days under the HIPAA Breach Notification Rule, notice to the FTC within 30 days for 500 or more consumers under the GLBA Safeguards Rule, 30 days to customers under the SEC's amended Regulation S-P, 36 hours from a bank to its federal regulator, and four business days for a public company's Form 8-K after it decides an incident is material.23456
- Idaho's law, Idaho Code 28-51-104 to 28-51-107, is short and dates from 2006. It requires a prompt, good-faith investigation, then notice to Idaho residents "as soon as possible" if misuse has occurred or is reasonably likely. It sets no fixed number of days for businesses, but a city, county or state agency must notify the Idaho Attorney General within 24 hours of discovering a breach.7
- Idaho's definition of personal information is narrow: a name plus a Social Security number, a driver's license or Idaho ID number, or a financial account or card number with the code needed to use it. A 2025 bill to widen it and require free credit monitoring did not pass, and nothing in the 2026 session changed the law.8910
- Encryption is the strongest single protection a notice law recognizes. In Idaho, as in most states and under HIPAA, data that was encrypted (with the key kept safe) generally does not trigger notice at all.82
- Most notice failures in public records are not about the letter. They are about delay, a first count that was far too low, telling people less than the organization already knew, or a decision to keep quiet. Write the procedure, name the decision makers, and keep a record of every decision and its date.
Rules and standards described: Idaho Code 28-51-104 to 28-51-107 (added 2006; 28-51-104 amended 2015 and 28-51-105 amended 2014; no amendment in the 2025 or 2026 sessions), read Nov. 13, 2026; Idaho Technology Authority Policy P4590 (effective May 30, 2019, revised May 31, 2022) and Standard S6010 (revised July 23, 2025), read Nov. 13, 2026; HIPAA Breach Notification Rule, 45 CFR 164.400 to 164.414 (as amended Jan. 25, 2013), eCFR current to Nov. 10, 2026; FTC Health Breach Notification Rule, 16 CFR Part 318 (as amended May 30, 2024, effective July 29, 2024); FTC Safeguards Rule, 16 CFR 314.4(j) (effective May 13, 2024); SEC Regulation S-P, 17 CFR 248.30 (amended June 3, 2024; compliance Dec. 3, 2025 for larger and June 3, 2026 for smaller entities); bank Computer-Security Incident Notification rule (86 FR 66424, compliance May 1, 2022); NCUA 12 CFR 748.1(c) (effective Sept. 1, 2023); SEC Form 8-K Item 1.05 (88 FR 51896, Aug. 4, 2023); state laws as cited, read Nov. 13, 2026. Rules change: check the current text before relying on any point.
Before you change anything. Plan changes to production systems, test them first, keep a way back, and follow your change management process. For clinical, plant-floor or other safety systems, involve the vendor, your safety lead and qualified engineers (see modules 109 and 111).

Why breach notice is its own discipline
Incident response is about stopping an attack and recovering. Breach notification is about telling the right people, in the right words, within the right time, under every law that applies. The two run side by side and share facts, but they are different jobs with different owners. A security team can do a fine job of containing a ransomware attack and the organization can still break the law if nobody tracks which residents of which states were in the stolen files and when each deadline runs. This lesson covers the notice job for regulated and large organizations. It assumes the reader has the basics from State privacy and breach laws in the small business module and the state-by-state survey in Breach notification laws in all 50 states, with Idaho's privacy laws covered in Idaho privacy law up close. The response side (detection, containment, the incident response team and ransomware decisions) is in lesson 10 of this module.
Incident, breach and "notification event" are different words
The words matter because each law defines its own. A security incident is any event that threatens the confidentiality, integrity or availability of systems or data; most incidents never become breaches. A breach, for notice purposes, is whatever the particular statute says it is. Idaho defines a "breach of the security of the system" as "the illegal acquisition of unencrypted computerized data that materially compromises the security, confidentiality, or integrity of personal information for one (1) or more persons."8 HIPAA uses a different test: any use or disclosure of protected health information not permitted by the Privacy Rule "is presumed to be a breach" unless a documented risk assessment shows "a low probability that the protected health information has been compromised."2 The FTC's Safeguards Rule uses yet another term, a notification event, meaning "acquisition of unencrypted customer information without the authorization of the individual to which the information pertains."3 The bank regulators' 36-hour rule is not about personal data at all: its "notification incident" is a computer-security incident that has materially disrupted, or is reasonably likely to materially disrupt, a bank's operations.11
So the same facts can be a breach under one law and not under another. A ransomware attack that encrypted a hospital's servers but stole nothing might require no notice under Idaho's statute (no acquisition), might be presumed a HIPAA breach unless the hospital can show a low probability of compromise, and might require a 36-hour call to a regulator if the hospital's bank was the victim instead. The procedure in this lesson starts by sorting facts against each definition, one law at a time.
One incident, many clocks
A large organization rarely faces one notice duty. Picture a regional health system headquartered in Boise with patients from Idaho, Oregon, Washington, Utah and Nevada, a self-insured employee health plan, a credit union for staff, a foundation that keeps donor card data, and publicly traded bonds. A single intrusion into its file servers can trigger HIPAA notice to patients, HHS and the media; state notices to employees and donors in every state where they live; attorney general notices in the states that require them; a contractual notice to the hospital's own customers if it provides services to other providers; a call to the credit union's regulator; and a securities disclosure analysis. Each runs on its own clock with its own content rules. The infographic in the section on federal rules lines them up.
Because the clocks are short and the facts arrive slowly, the organizations that do this well decide most of it in advance: who decides whether notice is required, who drafts, who signs, which vendors are on contract, and what goes in the file. That is the job of the sample procedure at the end of this lesson.
The state laws: 50 states plus DC and three territories
California passed the first breach notice law in 2002. Today the National Conference of State Legislatures (NCSL) reports that "All 50 states, the District of Columbia, Guam, Puerto Rico and the Virgin Islands" have laws requiring private businesses, and in most states government entities too, to notify people of breaches involving personally identifiable information.1 NCSL's summary page was last updated Jan. 17, 2022, so it gives the count and the statute citations but not the many amendments since; the state-by-state detail is in module 69, lesson 9, and the examples below were each read against a current source.
Whose law applies
State breach laws follow the person, not the company. A business in Idaho with a customer who lives in Texas owes that customer notice under Texas law, and a company in Texas with a customer in Idaho owes notice under Idaho law if it "conducts business in Idaho."7 For a national organization the practical result is that the strictest law among the states where affected people live sets the floor for the content and timing of the whole notice effort. Most large organizations simply write one letter that satisfies every state's content rules, add state-specific paragraphs where a state demands them, and mail on the earliest deadline.
What "personal information" means
Every state law starts from the same core: a person's first name or first initial and last name, combined with a Social Security number, a driver's license or state ID number, or a financial account or card number together with any code or password needed to use it. Idaho's definition stops there.8 Many states have added more data elements since 2015, for example:
- Online account credentials: a username or email address with a password or security question and answer. Pennsylvania added this in a 2022 amendment that took effect May 2, 2023.60
- Medical and health insurance information: Pennsylvania added medical and health insurance information in the same 2022 amendment; under its 2024 amendment, the medical information element applies to data held by state agencies and their contractors.6012
- Biometric data: Oklahoma's 2025 amendment, effective Jan. 1, 2026, added "unique biometric data such as a fingerprint, retina or iris image."13
- Other government identifiers: passport numbers, military ID numbers and individual taxpayer identification numbers appear in a number of states' lists.
The practical rule for a multi-state organization is to classify its data against the broadest definition among the states where its customers and employees live, not against its home state. An Idaho company whose customers are mostly in Idaho still has to know that a stolen file of usernames and passwords is outside Idaho's definition but inside the definitions of many other states.
Almost every state also excludes information lawfully available to the public from government records. Idaho's version excludes "publicly available information that is lawfully made available to the general public from federal, state, or local government records or widely distributed media."8
What triggers notice: acquisition, access and risk of harm
States split on two questions. The first is whether access to data is enough or whether the data must have been acquired. Idaho uses acquisition ("illegal acquisition of unencrypted computerized data").8 Some states use "access" or "access and acquisition," which reaches cases where an intruder could see records but there is no proof the records were copied. The FTC's Safeguards Rule handles this with a presumption: "Unauthorized acquisition will be presumed to include unauthorized access to unencrypted customer information" unless the institution has reliable evidence otherwise.3
The second question is whether notice is required for every breach or only when there is a risk of harm. Idaho is a risk-of-harm state: the duty to notify arises "If the investigation determines that the misuse of information about an Idaho resident has occurred or is reasonably likely to occur."7 The SEC's amended Regulation S-P is similar: no notice is required if, after "a reasonable investigation," the firm determines that sensitive customer information "has not been, and is not reasonably likely to be, used in a manner that would result in substantial harm or inconvenience."4 HIPAA, by contrast, presumes a breach and puts the burden of proving a low probability of compromise on the covered entity.2 When a state allows a no-notice decision, the organization should write it down: the facts, the reasoning, who decided, and the date. Several states require that written determination to be kept or sent to the attorney general, and every regulator who later reviews the decision will ask for it.
The encryption safe harbor and its catch
Nearly all state laws, and HIPAA, treat properly encrypted data as outside the notice duty. Idaho's definition reaches personal information only "when either the name or the data elements are not encrypted."8 HIPAA applies only to "unsecured" protected health information, and HHS guidance says encryption that meets its standards, with the key not compromised, takes data out of the rule.14 The catch is the key. The FTC's Safeguards Rule says customer information "is considered unencrypted for this purpose if the encryption key was accessed by an unauthorized person."3 An attacker who takes over a domain administrator account usually has the keys too, so a large organization's encryption claim needs evidence about where the keys were and whether the intruder reached them. Full-disk encryption on a server that was running, with its volume mounted, when files were copied off it does not help: the files left in readable form. Encryption choices are covered in lesson 7.
Timing: fixed deadlines and "without unreasonable delay"
The oldest laws, Idaho's among them, set no number of days. Idaho requires notice "as soon as possible" and "in the most expedient time possible and without unreasonable delay," with room for law enforcement needs and for the work of finding the scope of the breach, identifying the people affected and restoring the system.7 Since 2018 a growing list of states has added fixed outer limits. Recent examples, each read against a current source:
| State | Notice to residents | Notice to the attorney general or a state agency | Source |
|---|---|---|---|
| Idaho | As soon as possible, without unreasonable delay; no fixed days | Public agencies: Idaho Attorney General within 24 hours of discovery. Businesses: not required (may notify) | Idaho Code 28-51-105715 |
| California | Within 30 calendar days of discovery (SB 446, effective Jan. 1, 2026) | More than 500 residents: within 15 calendar days after notifying residents | Cal. Civ. Code 1798.82 as amended16 |
| New York | Within 30 days of discovery (amended Dec. 24, 2024, effective immediately) | Attorney General, Department of State, State Police and, since the 2024 amendment, the Department of Financial Services | Gen. Bus. Law 899-aa17 |
| Washington | No more than 30 calendar days after discovery | More than 500 residents: no more than 30 days after discovery | RCW 19.255.01018 |
| Texas | Not later than the 60th day after determining the breach occurred | At least 250 residents: not later than the 30th day, on the AG's electronic form (since Sept. 1, 2023) | Bus. and Com. Code 521.053, as amended by SB 768 (2023)19 |
| Pennsylvania | Without unreasonable delay | More than 500 residents: at the same time as notice to residents (since Sept. 26, 2024) | Breach of Personal Information Notification Act, as amended 202412 |
| Oklahoma | Without unreasonable delay | 500 or more residents (1,000 or more for credit bureaus): no more than 60 days after notice to residents (effective Jan. 1, 2026) | SB 626 (2025)13 |
| Maine | As expediently as possible and no more than 30 days after becoming aware of the breach and identifying its scope; after a law enforcement delay, no more than 7 business days after the agency says notice will not compromise the investigation | Attorney General, through its online reporting service | 10 M.R.S. 1348; Maine Attorney General6120 |
Two points about fixed deadlines trip up even experienced teams. First, most clocks run from discovery, not from the end of the investigation. Second, "without unreasonable delay" is not a grace period. It is judged after the fact by a regulator or a court that knows when the organization first learned of the problem. A 60-day or 30-day number is an outer limit, and an organization that had the facts on day 10 and mailed on day 59 may still have delayed unreasonably.
What the notice must say
Idaho's statute does not prescribe content; it defines only the methods of notice.8 Other laws do. Washington requires plain language and at least the name and contact information of the business, the types of personal information involved, the time frame of exposure (including the dates of the breach and of its discovery), and the toll-free numbers and addresses of the major credit reporting agencies if certain data was exposed.18 HIPAA requires, "to the extent possible," a brief description of what happened (with the date of the breach and the date of discovery), the types of information involved, the steps individuals should take to protect themselves, what the covered entity is doing to investigate, reduce harm and prevent recurrence, and contact procedures that "shall include a toll-free telephone number, an e-mail address, Web site, or postal address," all "written in plain language."2 The FTC's model letter in Data Breach Response: A Guide for Business uses plain headings that satisfy most state content rules: what happened, what information was involved, what we are doing, what you can do, other important information, and for more information.21 A large organization should keep one master template built on those headings, with a checklist of the state-specific additions (for example, a state's own consumer protection contact, or a statement about whether notice was delayed for law enforcement).
Notice to attorneys general, regulators and credit bureaus
Beyond the people affected, many states require notice to the state attorney general or another agency once a threshold is reached, commonly 500 or 1,000 residents, as the table above shows. Many states also require notice to the nationwide consumer reporting agencies (Equifax, Experian and TransUnion) when a breach requires notice to more than a set number of residents, so that the agencies can expect calls about fraud alerts and credit freezes. Idaho has neither duty for businesses.7 Oklahoma's 2025 amendment uses a 1,000-resident threshold for notice to the attorney general about breaches of credit bureau security systems.13 The FTC's guide recommends contacting the three agencies when Social Security numbers were taken and telling them in advance if the organization will recommend fraud alerts or freezes to a large group of people.21
Several attorneys general publish the notices they receive. California's Attorney General posts a searchable list with a sample of each notification letter and a downloadable file of the full list; Washington's posts each organization, the date, the number of Washingtonians affected and the types of information compromised; Maine's runs an online reporting service; and Texas's bill analysis described a public list as part of the 2023 changes.22232019 Idaho's Attorney General posts the notices it has received since Jan. 1, 2021 (see below).15 A large organization should assume that any attorney general notice will be public within days and write it accordingly.
Substitute notice
When individual notice is impractical, most laws allow substitute notice. Idaho allows it if the cost of notice would exceed $25,000, if more than 50,000 Idaho residents must be notified, or if the organization lacks sufficient contact information. Substitute notice in Idaho is all three of these: email to the residents whose addresses the organization has, a "conspicuous posting" on its website, and "Notice to major statewide media."8 HIPAA's version is narrower and tied to missing contact information: for 10 or more people with insufficient or out-of-date addresses, a conspicuous posting on the home page for 90 days or major print or broadcast media notice in the area where they likely live, with a toll-free number that stays active for at least 90 days.2 Large organizations should not reach for substitute notice simply because a breach is big. Regulators look hard at whether direct mail was truly impractical, and many of the largest breaches on record were handled by direct mail.
Credit monitoring: required in some states, expected in all
A few states require an offer of free credit monitoring or identity theft protection after breaches involving Social Security numbers. Pennsylvania's 2024 amendment, for example, requires one free credit report (if the person is not already entitled to one free under federal law) and 12 months of free credit monitoring when a breach exposes a name with a Social Security number, bank account number, or driver's license or state ID number.12 Idaho has no such requirement. Even where it is not required, regulators and plaintiffs expect it after a Social Security number breach, and the FTC's guide suggests considering "at least a year" of free monitoring or identity protection, especially where financial data or Social Security numbers were exposed.21 The real cost of notice is therefore the letters plus the monitoring plus the call center, and it scales with the number of people.
Law enforcement delay
Nearly every law lets notice wait while law enforcement says it would impede an investigation. In Idaho, notice "may be delayed if a law enforcement agency advises" that it would impede a criminal investigation, and must then be made "in good faith, without unreasonable delay and as soon as possible" after law enforcement says it no longer would.7 HIPAA requires a written statement from the agency to delay for a set period, or documentation of an oral statement, which then allows a delay of no more than 30 days unless a written statement follows.2 The Safeguards Rule lets a law enforcement official request an initial delay of up to 30 days in the FTC's public posting of a notice, extendable by up to 60 more days in writing.3 Regulation S-P's delay runs only on a determination by the U.S. Attorney General that notice poses "a substantial risk to national security or public safety."24 The organization should get the request in writing, record the name of the agent and agency, and calendar a date to ask again. A delay request covers what it says it covers: it does not excuse slow work on the investigation itself.
When you hold someone else's data
Every state law separates the owner or licensee of data, which notifies the people, from a business that only maintains data for the owner, which must tell the owner. In Idaho, an organization that maintains personal information it does not own "shall give notice to and cooperate with the owner or licensee" of any breach "immediately following discovery" if misuse has occurred or is reasonably likely, and cooperation "includes sharing with the owner or licensee information relevant to the breach."7 California's 2025 amendment gives the owner 30 days from the vendor's notice to notify people.16 Regulation S-P now requires covered firms to oversee service providers so that they notify the firm "as soon as possible, but no later than 72 hours" after becoming aware of a breach in security affecting a customer information system they maintain.24 HIPAA business associates must tell the covered entity within 60 days of discovery.2 Vendor contracts should set shorter, specific deadlines and say who pays for notice; see lesson 8.
Idaho Code 28-51-104 to 28-51-107, section by section
Idaho's breach law sits in Title 28 (Commercial Transactions), Chapter 51 (Identity Theft). It was added in 2006 (session laws chapter 258). Section 28-51-105 was last amended in 2014 and section 28-51-104 in 2015; sections 106 and 107 have not changed since 2006.872526 The text below follows the statute as posted by the Idaho Legislature and read Nov. 13, 2026. Government text may be quoted, and short quotations are used where the exact words matter.

28-51-104: the six definitions
- "Agency" means any "public agency" as defined in Idaho Code 74-101, the Public Records Act.8 That definition covers state agencies (every state officer, department, division, bureau, commission and board, including the legislative and judicial branches, with two narrow exceptions) and local agencies: "a county, city, school district, municipal corporation, independent public body corporate and politic, district, public health district, political subdivision, or any agency thereof."27 School districts, highway districts, public health districts, sewer districts and public hospitals organized as districts are all agencies for this law.
- "Breach of the security of the system" means "the illegal acquisition of unencrypted computerized data that materially compromises the security, confidentiality, or integrity of personal information for one (1) or more persons maintained by an agency, individual or a commercial entity." Good-faith acquisition by an employee or agent for the organization's purposes is not a breach "provided that the personal information is not used or subject to further unauthorized disclosure."8 Note three limits built into the words: the acquisition must be illegal, the data must be computerized (paper records are outside this law) and unencrypted, and the compromise must be material.
- "Commercial entity" includes corporations, business trusts, estates, trusts, partnerships of every kind, limited liability companies, associations, organizations, joint ventures "and any other legal entity, whether for profit or not-for-profit."8 Nonprofit hospitals, charities and churches that hold computerized personal information are covered.
- "Notice" means written notice to the most recent address in the organization's records, telephone notice, electronic notice consistent with the federal E-SIGN Act (15 U.S.C. 7001), or substitute notice under the $25,000, 50,000-resident or insufficient-contact-information tests described above.8
- "Personal information" means an Idaho resident's first name or first initial and last name with one or more of: a Social Security number; a driver's license number or Idaho identification card number; or an account number or credit or debit card number "in combination with any required security code, access code, or password that would permit access to a resident's financial account," when either the name or the data elements are not encrypted. Publicly available government records and widely distributed media are excluded.8
- "Primary regulator" is the organization's primary federal regulator if it is licensed or chartered by the United States (a national bank, for example); the Idaho Department of Finance for those it licenses; the Idaho Department of Insurance for those it licenses; and the Idaho Attorney General "for all agencies and all other commercial entities or individuals."8
28-51-105(1): the investigation duty comes first
Idaho's law, like Maine's 2005 statute, says in plain words that the investigation comes before notice.61 A city, county or state agency, individual or commercial entity "that conducts business in Idaho and that owns or licenses computerized data that includes personal information about a resident of Idaho shall, when it becomes aware of a breach of the security of the system, conduct in good faith a reasonable and prompt investigation to determine the likelihood that personal information has been or will be misused."7 Three words carry the weight: good faith, reasonable and prompt. An investigation that is slow, that is shaped to reach a no-notice answer, or that does not look at the evidence a reasonable investigator would look at (logs, the files the intruder touched, what left the network) does not meet the statute.
28-51-105(1): notice to residents "as soon as possible"
If the investigation "determines that the misuse of information about an Idaho resident has occurred or is reasonably likely to occur," the organization "shall give notice as soon as possible to the affected Idaho resident." Notice "must be made in the most expedient time possible and without unreasonable delay, consistent with the legitimate needs of law enforcement and consistent with any measures necessary to determine the scope of the breach, to identify the individuals affected, and to restore the reasonable integrity of the computerized data system."7 There is no number of days. In practice, an Idaho organization with residents of other states affected will be held to the 30-day or 60-day limits of those states anyway, and an Idaho-only incident should be handled on a similar schedule, because "as soon as possible" is a stricter phrase than "within 60 days," not a looser one.
Public agencies: the Attorney General within 24 hours
The one fixed clock in Idaho's law is for government: "When an agency becomes aware of a breach of the security of the system, it shall, within twenty-four (24) hours of such discovery, notify the office of the Idaho attorney general."7 Note the trigger. The 24-hour duty runs from discovery of a breach, not from a finding of likely misuse, so an agency must notify the Attorney General before its investigation is done. The Attorney General's office describes the rule the same way and adds that "A commercial entity that experiences a breach may notify the Attorney General's Office but is not required to do so." Reports go to the Consumer Protection Division by email or mail.15
State agencies: ITS, the Office of Risk Management and WebEOC
Section 28-51-105 adds: "Nothing contained in this section relieves a state agency's responsibility to report a security breach to the office of the chief information officer within the department of administration, pursuant to the Idaho technology authority policies."7 That office is now the Idaho Office of Information Technology Services (ITS). The Idaho Technology Authority (ITA), the body that sets statewide IT policy, carries out this sentence through two documents:
- ITA Policy P4590, Cybersecurity Incident and Breach Response Management and Reporting (effective May 30, 2019, revised May 31, 2022), requires each state agency to "document incident response guidelines that define their agencies roles and responsibilities if an incident or breach does occur" and to "investigate and report their findings on incidents and breaches in accordance with policies and standards for reporting." It is reviewed every 12 months.28
- ITA Standard S6010 of the same name (effective Feb. 19, 2019, revised April 20, 2021 and July 23, 2025) requires agencies to notify the Attorney General's office, the Office of Risk Management and ITS "no later than 24 hours after discovery of a breach," "Regardless of the determination of misuse." Incidents that are not breaches must be reported to the ITS Chief Information Security Officer's office through WebEOC (the state's emergency management reporting system) "Within five (5) business days of discovery," with weekly status reports and a full investigation report at the end. The attached State of Idaho Incident Response Reporting Handbook (revision 1.03, Oct. 16, 2020) adds that WebEOC reports also serve "to meet timing requirements for cyber insurance," tells agencies not to put affected people's information into the form, requires agencies to use the VERIS incident vocabulary, and includes a sample breach notification letter.29
The ITA documents bind state executive agencies. Counties, cities, school districts and other local agencies are "agencies" under the breach statute and owe the 24-hour Attorney General notice, but this lesson did not find a source showing that ITA policies themselves bind local governments; a local agency should treat S6010 as a strong model and follow any contract or insurance pool terms that adopt it. In 2025 the Legislature also passed House Bill 35 (session law chapter 6, effective July 1, 2025), which directs ITS to implement cybersecurity best practices and requires multifactor identification across state government; it does not change the breach notice sections.30
A misdemeanor for government employees who disclose
Section 28-51-105(1) ends with a criminal penalty aimed at public employees: "Any governmental employee who intentionally discloses personal information not subject to disclosure otherwise allowed by law is guilty of a misdemeanor and, upon conviction thereof, shall be punished by a fine of not more than two thousand dollars ($2,000), or by imprisonment in the county jail for a period of not more than one (1) year, or both."7 It covers intentional disclosure, not negligent loss, but it is a reason for public agencies to train staff on what may be released under the Public Records Act and what may not.
28-51-105(2) and (3): data you hold for others, and law enforcement delay
Subsection (2) covers service providers. An organization that maintains computerized personal information it does not own or license "shall give notice to and cooperate with the owner or licensee of the information of any breach of the security of the system immediately following discovery of a breach if misuse of personal information about an Idaho resident occurred or is reasonably likely to occur." Subsection (3) allows notice to be delayed "if a law enforcement agency advises" that notice "will impede a criminal investigation," after which notice must be made "in good faith, without unreasonable delay and as soon as possible."7 "Immediately" in subsection (2) is the strictest timing word in the statute. Idaho payroll processors, billing services, managed IT providers and cloud hosts should read it as hours, not weeks, and their customers should write a specific deadline into the contract.
28-51-106: when your own procedures count as compliance
Section 106 has two safe harbors. Under subsection (1), an organization "that maintains its own notice procedures as part of an information security policy for the treatment of personal information, and whose procedures are otherwise consistent with the timing requirements of section 28-51-105" is deemed to comply if it notifies affected Idaho residents under its own policy. Under subsection (2), an individual or commercial entity "regulated by state or federal law" that "maintains procedures for a breach of the security of the system pursuant to the laws, rules, regulations, guidances, or guidelines established by its primary or functional state or federal regulator" is deemed to comply if it follows those procedures when a breach occurs.25
For regulated organizations, subsection (2) is the most important sentence in Idaho's law. A hospital that follows a written HIPAA breach procedure, a bank that follows the federal banking agencies' response program guidance, or a broker-dealer that follows Regulation S-P is deemed to comply with Idaho's notice section, provided it actually follows the procedure. Two cautions. First, the safe harbor is only as good as the written procedure, which is a reason to have one (see the sample below). Second, it covers only Idaho's notice requirement; residents of other states are governed by their own laws, many of which have narrower safe harbors or none.
28-51-107: enforcement and the $25,000 fine
If a primary regulator "has reason to believe" an organization under its jurisdiction failed to give notice as required, it "may bring a civil action to enforce compliance" and to enjoin further violations. An organization that "intentionally fails to give notice" is "subject to a fine of not more than twenty-five thousand dollars ($25,000) per breach of the security of the system."26 The fine is per breach, not per person, and requires intent. On their face, the four sections do not create a private right for individuals to sue; people harmed by a breach in Idaho usually sue under general negligence, contract or consumer protection theories, which this lesson does not cover.
What Idaho's law leaves out
Compared with the newer laws in the state table above, Idaho's statute, as read Nov. 13, 2026, has:
- no fixed number of days for notice to residents;
- no duty for businesses to notify the Attorney General or any state agency (public agencies only);
- no duty to notify the consumer reporting agencies;
- no required content for the notice letter;
- no required credit monitoring offer;
- no coverage of online account credentials, biometric data, medical or health insurance information, passport numbers or taxpayer identification numbers;
- no coverage of paper records; and
- a maximum fine of $25,000 per breach, and only for intentional failure to notify.
None of that makes Idaho a place where an organization can do less. Regulated organizations meet the federal rules anyway; national organizations meet the strictest state rule anyway; and the Idaho residents affected by a breach will judge an organization by what it told them and when, not by the length of the statute.
The 2025 attempt to update Idaho's law
In February 2025 the Senate Commerce and Human Resources Committee introduced Senate Bill 1066. As printed, it would have replaced "personal information" with "personally identifiable information"; added online account credentials, medical and DNA information, health insurance identifiers, biometric data used for authentication and individual taxpayer identification numbers; and required an organization that found misuse occurred or was reasonably likely to offer at least 36 months of free credit monitoring plus information about credit freezes.31 At the committee hearing on Feb. 13, 2025, the sponsor, Sen. Ben Toews, said the bill would align Idaho's standards with industry practice; committee members asked about the cost to public agencies, and the minutes record the sponsor's estimate that 36 months of monitoring could cost about $450 per victim. The committee voted to send the bill to the Senate's amending order, with talk of cutting monitoring to 12 months.32 On March 4, 2025 the Senate adopted amendments that cut the monitoring period to 12 months, dropped health insurance identifiers, added a definition of encryption, and excluded acquisition of data from sources other than the organization's own systems or those of its service providers.59 A revised statement of purpose dated March 7, 2025 estimated about $150 per victim for 12 months of monitoring.33 The amended bill passed the Senate 27 to 6 on March 10, 2025, and the House Business Committee recommended it on March 17, but it was held on the House's General Orders calendar; its last recorded action, on April 4, 2025, was "Retained on General Orders," and it did not become law.9 The 2026 session laws list includes no amendment to Chapter 51.10 The question whether Idaho should update its law is taken up under Hard questions below.
The Idaho Attorney General's breach list
The Idaho Attorney General's Consumer Protection Division posts the breach notices it has received since Jan. 1, 2021, by organization and notification date.15 As read Nov. 14, 2026, the list showed 262 entries (including a few marked as supplemental notices): 37 dated in 2021, 28 in 2022, 34 in 2023, 25 in 2024, 94 in 2025 and 44 in 2026 through Nov. 9. The 2025 spike is mostly schools: 63 entries are dated January 2025 and 71 of the 94 entries for 2025 are school districts, charter schools or the school software vendor PowerSchool, which also appears on the list. These counts are this lesson's own tally of the posted page, and because businesses are not required to report, the list undercounts private-sector breaches affecting Idahoans. It is still the best single public record of public agency breaches in Idaho, and it shows cities, counties, school districts, colleges, the Idaho Department of Labor, the Idaho Transportation Department and the State Insurance Fund among the filers.15
Federal notice rules by sector
There is no general federal breach notification law for private companies. Congress has instead written notice duties into sector laws, and agencies have written them into rules. A regulated organization usually lives under one or two of these and under the state laws at the same time. The sections below cover the main ones; sector detail is in the sister modules for health care, professional firms and manufacturing and critical infrastructure.
HIPAA Breach Notification Rule (45 CFR 164.400 to 164.414)
The HIPAA rule applies to covered entities (health plans, health care clearinghouses and most health care providers) and their business associates, and only to unsecured protected health information.2 Its main parts, as read in the eCFR current to Nov. 10, 2026:
- The presumption. An impermissible use or disclosure "is presumed to be a breach" unless the covered entity or business associate shows "a low probability that the protected health information has been compromised based on a risk assessment of at least" four factors: the nature and extent of the information (including identifiers and the likelihood of re-identification), the unauthorized person who used it or received it, whether it was actually acquired or viewed, and the extent to which the risk has been mitigated. This replaced the 2009 "significant risk of harm" test in the 2013 Omnibus Rule.234
- Individuals. Notice "without unreasonable delay and in no case later than 60 calendar days after discovery," with the content listed earlier, by first-class mail (or email if the person agreed).2
- Media. For a breach involving "more than 500 residents of a State or jurisdiction," notice to "prominent media outlets serving the State or jurisdiction," on the same 60-day clock.2
- HHS. For 500 or more individuals, notice to the Secretary at the same time as the individual notices; for fewer than 500, a log submitted no later than 60 days after the end of each calendar year.2
- Business associates. Notice to the covered entity within 60 days of discovery, with the identity of each affected person to the extent possible.2
- Burden of proof. The covered entity or business associate "shall have the burden of demonstrating that all notifications were made as required" or that the event was not a breach (45 CFR 164.414), which is why the documentation discussed below matters.2
The scale is large. HHS's report to Congress for calendar year 2024 counted 663 breach reports of 500 or more people, affecting about 242,908,056 individuals, plus 74,299 reports of fewer than 500 affecting about 340,618 people.35 The largest was the Change Healthcare ransomware attack of February 2024, which HHS's frequently asked questions page says affected about 192.7 million people as of July 31, 2025, and which HHS let Change notify on behalf of the covered entities whose data it held.36 The HHS breach portal lists every breach of 500 or more under investigation from the last 24 months.37 Idaho examples on the portal and in the press include Kootenai Health's 2024 ransomware attack, which its filing with the Maine Attorney General put at 464,088 people.38

FTC Health Breach Notification Rule (16 CFR Part 318)
Health apps, fitness trackers, personal health record vendors and similar businesses that are not covered by HIPAA can fall under the FTC's Health Breach Notification Rule. The FTC amended it in a final rule published May 30, 2024 and effective July 29, 2024.39 The amended definition says a breach of security "includes an unauthorized acquisition of unsecured PHR identifiable health information in a personal health record that occurs as a result of a data breach or an unauthorized disclosure," which reaches an app's own sharing of health data without the user's authorization, not only hacking.40 Notices to individuals and the media are due "without unreasonable delay and in no case later than 60 calendar days after the discovery of a breach of security"; notice to the FTC for 500 or more people is due at the same time as the individual notices, and breaches of fewer than 500 may be logged and reported annually. Violations are treated as violations of an FTC trade regulation rule and carry civil penalties adjusted each year for inflation.40 The 2024 rulemaking cited the FTC's first two enforcement actions under the rule, against GoodRx ($1.5 million civil penalty) and Easy Healthcare, maker of the Premom app ($100,000).39
GLBA Safeguards Rule: notice to the FTC within 30 days
The FTC's Safeguards Rule applies to non-bank financial institutions under the Gramm-Leach-Bliley Act (GLBA): mortgage lenders and brokers, auto dealers that finance, payday lenders, tax preparers, accounting firms that do tax work, check cashers, collection agencies, investment advisers not registered with the SEC and others. Since May 13, 2024, the rule has required: "Upon discovery of a notification event ... if the notification event involves the information of at least 500 consumers, you must notify the Federal Trade Commission as soon as possible, and no later than 30 days after discovery of the event."341 The notice goes on an electronic form on ftc.gov and must include the institution's name and contact information, the types of information involved, the date or date range if it can be determined, the number of consumers affected or potentially affected, a general description, and whether law enforcement has asked in writing for a delay in public notice.3
Two decisions in the FTC's final rule matter for planning. First, the Commission said it "intends to enter notification event reports into a publicly available database," so the report should be written as a public statement. Second, the FTC declined to require notice to consumers, reasoning that "because all States have some form of consumer notification requirement, a direct consumer notification requirement in the Safeguards Rule would be largely duplicative of those State laws."41 An Idaho tax firm with a 600-client breach therefore notifies the FTC within 30 days under the Safeguards Rule and its clients under Idaho Code 28-51-105 and the law of every other state where clients live. Professional firms are covered in module 110, lesson 4.

SEC Regulation S-P amendments (17 CFR 248.30)
The SEC adopted amendments to Regulation S-P on May 16, 2024; they were published June 3, 2024 (89 FR 47688) and took effect Aug. 2, 2024.4 They apply to broker-dealers (including funding portals), investment companies, registered investment advisers and transfer agents. Larger entities had to comply by Dec. 3, 2025 and smaller entities by June 3, 2026; the SEC's release defines larger entities as, for example, investment advisers with $1.5 billion or more in assets under management and fund groups with net assets of $1 billion or more.4 As of Nov. 13, 2026 both dates have passed and no extension was found in the Federal Register.24 The amended rule requires:
- a written incident response program "reasonably designed to detect, respond to, and recover from" unauthorized access to or use of customer information;
- notice to affected individuals whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization, "as soon as practicable, but not later than 30 days" after the firm becomes aware of the incident, unless the firm determines after a reasonable investigation that the information has not been and is not reasonably likely to be used in a way that would result in "substantial harm or inconvenience";
- service provider oversight, including policies reasonably designed to ensure that service providers notify the firm "as soon as possible, but no later than 72 hours after becoming aware" of a breach in security affecting a customer information system they maintain; and
- written records documenting compliance.
Delay is allowed only if the U.S. Attorney General determines that notice "poses a substantial risk to national security or public safety" and tells the SEC in writing, for up to 30 days, extendable by 30 days and, "In extraordinary circumstances," a final 60.24
Banks: the 36-hour rule and customer notice
The Federal Reserve, the FDIC and the OCC published the Computer-Security Incident Notification rule on Nov. 23, 2021 (86 FR 66424), effective April 1, 2022 with compliance required by May 1, 2022.5 A banking organization must notify its primary federal regulator "as soon as possible and no later than 36 hours after the banking organization determines that a notification incident has occurred." A bank service provider must notify at least one bank-designated contact at each affected bank customer "as soon as possible" when it determines that an incident has materially disrupted or degraded, or is reasonably likely to disrupt or degrade, covered services "for four or more hours."11 This rule is about operational disruption, not personal data. Notice to customers whose information was taken comes from the banking agencies' 2005 Interagency Guidance on Response Programs, which expects a bank to notify affected customers when it determines that misuse of sensitive customer information has occurred or is reasonably possible, and from state law (which Idaho's 28-51-106(2) lets a bank satisfy by following its regulator's procedures). The NCUA's Appendix B, which mirrors the bank guidance for credit unions, says that if misuse "has occurred or is reasonably possible," the institution "should notify the affected member as soon as possible."4225
Credit unions: the 72-hour rule and Appendix B
Since Sept. 1, 2023, every federally insured credit union must notify the NCUA "as soon as possible but no later than 72 hours after" it reasonably believes it has experienced a reportable cyber incident, or within 72 hours of being notified by a third party, whichever is sooner.4243 Member notice is guided by Appendix B to Part 748, which defines "sensitive member information" as a member's name, address or telephone number together with a Social Security number, driver's license number, account number, card number, or a PIN or password that would permit access to the account, and expects credit unions to notify the NCUA regional director "as soon as possible" when they become aware of unauthorized access to sensitive member information.42 On Dec. 11, 2025 the NCUA Board proposed removing Appendix B from the Code of Federal Regulations and republishing it as guidance (90 FR 57397; comments closed Feb. 9, 2026). As of the eCFR text current to Nov. 4, 2026, Appendix B is still in the CFR.4442
Public companies: Form 8-K Item 1.05
A public company that determines a cybersecurity incident is material must file a Form 8-K under Item 1.05 "within four business days of determining an incident was material," with a delay only if the U.S. Attorney General determines that disclosure would pose a substantial risk to national security or public safety. The rule was adopted July 26, 2023 and published Aug. 4, 2023 (88 FR 51896).6 The SEC's adopting release says "Item 1.05 is not a voluntary disclosure," and SEC staff, quoting that line in May 2024, encouraged companies to disclose incidents not yet determined to be material, if at all, under another item such as 8.01.645 In January 2026 the SEC chairman announced a review of Regulation S-K and requested comment, and several business groups urged the SEC to rescind Item 1.05; as of Nov. 13, 2026 no proposal to change it appears in the Federal Register, so the rule remains in effect.46 An 8-K is a disclosure to investors, not a notice to the people whose data was taken, but it is public on EDGAR the day it is filed, so the 8-K and the consumer letters must tell the same story. Governance and disclosure are covered in lesson 4.
Other clocks in brief
- New York DFS Part 500. Entities licensed by the New York Department of Financial Services must notify the superintendent "in no event later than 72 hours after determining that a cybersecurity incident has occurred," and must report any extortion payment within 24 hours and explain it within 30 days.47
- Defense contractors. DFARS 252.204-7012 requires contractors to "rapidly report" cyber incidents affecting covered defense information, defined as within 72 hours of discovery, to the Department of Defense.48
- CIRCIA. The Cyber Incident Reporting for Critical Infrastructure Act of 2022 will require covered critical infrastructure entities to report covered cyber incidents to CISA within 72 hours and ransom payments within 24 hours, but only once CISA's final rule takes effect. CISA proposed the rule April 4, 2024; press reports said the final rule went to the White House Office of Information and Regulatory Affairs for review on Oct. 1, 2026. A search of the Federal Register on Nov. 13, 2026 found no final rule, so CIRCIA reporting is not yet mandatory.4950
- Outside the United States. The EU and UK General Data Protection Regulation requires a controller to notify its supervisory authority of a personal data breach "without undue delay and, where feasible, not later than 72 hours after having become aware of it" (Article 33), unless the breach is unlikely to result in a risk to people. See lesson 12.51
From discovery to the last letter: the notification process
The flow chart below is the process this lesson recommends for a regulated or large organization. It is original to this module and follows the structure of the statutes and rules cited; it is not a copy of any published figure. Lesson 10 covers the response work that runs alongside it.
Step 1: discovery and the clock log
Most deadlines run from discovery, and the rules define it broadly. Under HIPAA, a breach is treated as discovered on the first day it is known to the covered entity, "or, by exercising reasonable diligence would have been known," to any workforce member or agent other than the person who committed it.2 So the clock can start when a help desk technician sees something odd, not when the CISO is briefed. The first act of the notice lead should be to open a clock log: a simple dated record of when the organization first learned each fact, who learned it, and which deadlines it starts. Every later decision about timing will be measured against that log.
Step 2: the first hours
In the first hours, three notice duties can already be running: an Idaho public agency's 24-hour notice to the Attorney General (and, for state agencies, the 24-hour notice to ITS and the Office of Risk Management under ITA Standard S6010), a bank's 36-hour notice to its regulator, and the 72-hour clocks for credit unions, New York DFS licensees, defense contractors and service providers to SEC-registered firms.7291142474824 These early notices are usually short and say what is known so far. The organization's cyber insurance policy almost always requires prompt notice to the insurer as well, often through a hotline, and late notice to the insurer can cost coverage. Containment changes to production systems made in these hours should be planned, tested where possible and reversible, with a way back if they cause outages.
Step 3: the investigation the law requires
Idaho requires "a reasonable and prompt investigation to determine the likelihood that personal information has been or will be misused."7 The questions are always the same. Which systems were reached? What data was on them? Is there evidence data was copied out (acquired), or only that it could have been seen (accessed)? Was it encrypted, and was the key safe? Has the data appeared for sale or on a leak site? Forensic investigators answer the technical questions; the notice lead turns the answers into a decision under each law. When the honest answer is "we cannot tell," most regulators expect the organization to assume the worse case: the Safeguards Rule's presumption that access means acquisition and HIPAA's presumption of breach both point that way.32
Step 4: identifying the people and where they live
In a large breach this step takes the most time and causes most delays. The stolen material is often a pile of unstructured files: spreadsheets, scanned forms, email archives, database exports. Someone has to review them, find every personal data element, tie each one to a person, find each person's last known address, and decide which state they live in. Large organizations use data review vendors that run automated searches and then human review, much like document review in litigation. Three warnings from public cases. First, counts usually grow: Change Healthcare's HHS filing began with 500 as a placeholder and reached about 192.7 million people; Orrick, Herrington and Sutcliffe's count grew from about 153,000 to more than 638,000.3652 Second, the review deadline is the notice deadline, not an excuse for it; if the review will take weeks, notify the people already identified and send supplemental notices later. Third, keep the data map current before any breach (see lesson 7), because the organizations that know where their personal data lives can answer step 4 in days instead of months.
Step 5: applying each law, state by state
With the list in hand, the notice lead runs each person's state law against the facts, plus each federal rule that applies. The output is a notice matrix: one row per jurisdiction, with the number of residents, whether notice is required, the deadline, whether the attorney general or a state agency must be told, whether the credit bureaus must be told, any required content and any required credit monitoring. For a national breach, most organizations notify everyone on the earliest deadline with one letter that meets every state's content rules, because running separate schedules for 50 states invites mistakes. The matrix is also the record that shows a regulator, later, that each law was considered.
Step 6: preparing the notices
Prepare, in parallel: the master letter (plain language, the FTC model letter's headings, the dates of the breach and of discovery, the types of information, what the organization is doing, what people can do, and a toll-free number); state inserts; the attorney general and regulator filings; the HHS portal filing for HIPAA breaches of 500 or more; media notice where HIPAA requires it; a website notice; the call center script and frequently asked questions; and the credit monitoring enrollment codes.212 Every document must match. Reporters and plaintiffs will put the 8-K, the attorney general filing, the website notice and the letter side by side, and differences in dates or counts become the story.
Step 7: sending
Letters go by first-class mail unless the person agreed to electronic notice (Idaho allows electronic notice consistent with the federal E-SIGN Act).8 Attorney general filings go through each state's portal or by email or mail. A public company's 8-K, if one is required, goes on EDGAR within four business days of the materiality determination, which may come before or after the consumer notices.6 Time the release so that people hear first from the organization, not from a reporter who saw an attorney general posting.
Step 8: after the letters
Track returned mail and send substitute notice where the rules require it. Staff the call center for at least the period the rules require (HIPAA's substitute notice requires a toll-free number active for at least 90 days).2 When the count or the facts change, send supplemental notices and update the regulator filings; the Idaho Attorney General's list shows several organizations filing supplemental notices, and HHS updates its portal entries as counts change.1537 Then hold an after-action review and update the procedure.
Vendors, call centers and credit monitoring
A breach of more than a few thousand people is beyond what most organizations can mail and answer on their own. Large organizations put four kinds of vendors under contract before any breach, often through their cyber insurer's panel:
| Vendor | What it does | What to settle in advance |
|---|---|---|
| Forensic investigator | Finds how the intruder got in, what was reached and what left | Who hires it, who receives its report, how fast it can start, and whether the insurer approves it |
| Data review vendor | Searches the affected files and builds the list of people, data elements and addresses | Security of the review platform, accuracy checks, turnaround per 100,000 documents, and how it handles minors and deceased persons |
| Notice and mail vendor | Prints and mails letters, sends emails, runs address updates and tracks returns | Template approval steps, address standardization, state inserts, proof-of-mailing records, and daily mailing capacity |
| Call center | Answers questions from the public using an approved script | Script approval, escalation path for hard questions, languages offered, hours, and how long the line stays open |
| Credit monitoring or identity protection provider | Supplies enrollment codes and monitoring; restoration help for identity theft victims | Length of coverage (12 months is common; some states require it; Idaho's 2025 bill proposed 36, cut to 12 by amendment), enrollment deadlines, and minors' coverage |
Each of these vendors will receive personal information about the people affected, so each is itself a service provider under the same laws and should be under a contract with security terms, as lesson 8 describes. The call center script deserves special care. Callers ask whether they should freeze their credit (the script should explain free credit freezes and fraud alerts), whether their children are affected, whether the organization will pay for losses, and whether the attackers still have their data. Answers must match the letter. "We do not know yet" is an acceptable answer; an answer that later proves false is not.
Multi-state notice in practice
Three habits separate organizations that handle multi-state notice well from those that end up in attorney general settlements.
- Keep a living notice matrix. State laws change every year: California's 30-day rule took effect Jan. 1, 2026; Oklahoma's amendments on the same date; New York's 30-day rule in December 2024; Pennsylvania's attorney general and credit monitoring rules in September 2024; Texas's 30-day attorney general rule in September 2023.1613171219 Someone should own a table of every state's definition, trigger, deadline, regulator notice, credit bureau notice, content rules and safe harbors, reviewed at least once a year and before any notice goes out.
- Write to the strictest common standard. One plain-language letter with every element any state requires, sent on the earliest deadline, is easier to defend than 50 variations.
- Tell regulators the same story. Attorney general filings, the HHS portal, the FTC form, the SEC filing and the letter should match on dates, counts and the description of what happened, and say plainly when facts are still being confirmed.
Record keeping: proving you did it right
The organization carries the burden of proof under HIPAA, and in practice under every other law: a regulator asking about a breach two years later will want to see what was known and when, what was decided and why, and when each notice went out.2 Keep:
- the clock log, with dates and times of discovery and of each new key fact;
- the forensic findings relied on (or a summary of them), including the evidence about acquisition, encryption and keys;
- each risk assessment or no-notice decision, with the facts, the reasoning, the approver and the date (HIPAA's four-factor assessment; Idaho's misuse finding; Regulation S-P's substantial-harm finding);
- the notice matrix and the final list of people notified by state, with proof of mailing;
- copies of every notice, filing and media statement, and every supplemental notice;
- any law enforcement delay request, with the agency, the person, the date and the period; and
- the after-action review and changes made.
HIPAA requires covered entities to keep required documentation for six years from its creation or last effective date, and the amended Regulation S-P adds written records of compliance with its response program and notice duties.534 A large organization should set one retention period for all breach files at least as long as the longest rule that applies to it.
Sample: Breach Notification Procedure
The sample below is written for a regulated or large organization with residents of several states. It is designed to sit under the organization's Incident Response Plan (lesson 10) and its top-level Information Security Policy (lesson 4). For a HIPAA covered entity, it should be read with the HIPAA procedure in module 109; for an Idaho state agency, with ITA Policy P4590 and Standard S6010.
Sample only. Adapt it to your organization's risks, systems and laws, have qualified people review it, and do not treat it as a substitute for a risk assessment.
Follows: Idaho Code 28-51-104 to 28-51-107 (read Nov. 13, 2026); ITA Policy P4590 and Standard S6010; 45 CFR 164.400 to 164.414; 16 CFR 314.4(j); 16 CFR Part 318; 17 CFR 248.30; 12 CFR Part 53 and 12 CFR 748.1(c); the state laws in the organization's notice matrix; the FTC's Data Breach Response: A Guide for Business.
1. Purpose and scope
This procedure sets out how [Organization] decides whether a security incident requires notice to individuals, regulators, attorneys general, consumer reporting agencies, the media, business customers or investors, and how it gives that notice on time. It applies to all personal information, protected health information, customer information and other regulated data that [Organization] owns, licenses or maintains for others, in any form, and to all workforce members, contractors and service providers.
2. Roles
- Notice Lead: [title, for example Chief Privacy Officer]. Owns this procedure, the clock log and the notice matrix; drafts or approves every notice.
- Incident Commander: [title, for example CISO]. Runs the technical investigation under the Incident Response Plan and gives the Notice Lead written findings.
- Decision Group: [Chief Compliance Officer], [General Counsel's office], [Chief Communications Officer], [CISO], [business owner of the affected data]. Decides whether notice is required, approves content and timing.
- Executive Approver: [CEO or delegate]. Approves notices to more than [number] people, any public statement and any regulator filing; informs the board under [Board reporting policy].
- Disclosure Committee: [for public companies] decides materiality for Form 8-K Item 1.05.
3. Discovery and the clock log
3.1 Any workforce member who suspects that regulated data was lost, stolen, accessed or disclosed without authorization must report it at once to [help desk or security contact, phone and email].
3.2 Within [2] hours of a report that may involve regulated data, the Notice Lead opens a clock log recording the date and time of first knowledge, who knew, and each later key fact. Discovery is the earliest date any workforce member knew or, with reasonable diligence, would have known.
3.3 Within [4] hours, the Notice Lead checks the short clocks in Appendix A (for example: Idaho Attorney General within 24 hours if [Organization] is an Idaho public agency; [primary federal regulator] within 36 hours for a notification incident; [NCUA, NYDFS, DoD] within 72 hours; contract notice deadlines to business customers) and records each one as met, not applicable, or pending.
3.4 The Notice Lead notifies [cyber insurer] through [hotline] within [time required by the policy].
4. Investigation
4.1 The Incident Commander conducts, in good faith, a reasonable and prompt investigation to determine what systems and data were involved, whether data was acquired or only accessed, whether it was encrypted and whether the key was compromised, and the likelihood that personal information has been or will be misused.
4.2 Where the evidence cannot rule out acquisition, [Organization] treats the data as acquired.
4.3 The Incident Commander gives the Notice Lead written interim findings every [2] business days until the investigation closes.
5. The notice decision
5.1 For each jurisdiction and rule in the notice matrix, the Decision Group records whether notice is required, the deadline, and the reasons.
5.2 A decision not to notify is made only where the applicable law allows it (for example, a documented finding that misuse has not occurred and is not reasonably likely, or a HIPAA four-factor assessment showing a low probability of compromise), and is recorded with the facts, the reasoning, the approver and the date. The decision is revisited if new facts emerge.
5.3 Notice is not delayed to complete the investigation beyond what is needed to determine scope, identify individuals and restore systems. If the full list will take longer than [15] days, [Organization] notifies the individuals already identified and sends supplemental notices.
5.4 A law enforcement request to delay notice is accepted only if [in writing, or recorded with the agent's name, agency and date], and is re-confirmed every [30] days.
6. Content
6.1 Individual notices use the master template in Appendix B, in plain language, under the headings: What happened; What information was involved; What we are doing; What you can do; For more information. They state the date or date range of the breach and the date of discovery, the types of information, a toll-free number, and free credit freeze and fraud alert information, plus any state-specific content in the notice matrix.
6.2 Where Social Security numbers, driver's license or state ID numbers or financial account numbers were involved, [Organization] offers [12 / 24] months of free credit monitoring or identity protection, or longer where a state requires it.
6.3 All notices, filings, website statements and investor disclosures about the same incident must match on dates, counts and description. The Notice Lead keeps a single fact sheet that every document draws from.
7. Who receives notice
7.1 Individuals: by first-class mail to the last known address, or by email where the person has agreed to electronic notice, within the earliest applicable deadline.
7.2 Regulators and attorneys general: as listed in the notice matrix (for example, HHS for HIPAA breaches; the FTC within 30 days for Safeguards Rule notification events of 500 or more consumers; state attorneys general at each state's threshold).
7.3 Consumer reporting agencies: where a state requires it, and in any event where [Organization] recommends fraud alerts or freezes to a large number of people.
7.4 Media: where HIPAA requires it (more than 500 residents of a state) or where substitute notice is used.
7.5 Data owners: where [Organization] maintains data for another organization, notice to that owner immediately on discovery, and in no event later than [the contract deadline or 72 hours].
8. Vendors
[Organization] keeps contracts in place with a forensic firm, a data review vendor, a notice and mail vendor, a call center and a credit monitoring provider: [names]. Each contract includes security terms, confidentiality, and turnaround commitments. The Notice Lead approves all scripts and templates before use.
9. Records
The Notice Lead keeps the clock log, findings relied on, each notice decision, the notice matrix, the list of people notified by state with proof of mailing, copies of all notices and filings, any law enforcement delay requests and the after-action review for [6] years or the longest period any applicable rule requires.
10. Testing and review
This procedure is exercised at least [once a year] in a tabletop exercise that includes a multi-state notice decision, and the notice matrix is reviewed at least [once a year] and whenever a state in which [Organization] has customers or employees changes its law. Approved by [title] on [date]; next review [date].
Appendix A: notice matrix and clocks. Appendix B: master letter template. Appendix C: regulator and attorney general contact list. Appendix D: call center script and frequently asked questions.
Pictures, Numbers and Infographics
The key numbers in this lesson, each with its source and date.
| Number | What it is | Source |
|---|---|---|
| 50 + 4 | All 50 states, the District of Columbia, Guam, Puerto Rico and the U.S. Virgin Islands have breach notice laws (NCSL summary updated Jan. 17, 2022) | NCSL1 |
| 24 hours | Idaho public agency's deadline to notify the Idaho Attorney General after discovering a breach | Idaho Code 28-51-1057 |
| 5 business days | Idaho state agency's deadline to report a non-breach cybersecurity incident to the ITS security office through WebEOC | ITA Standard S601029 |
| $25,000 | Idaho's maximum fine per breach for intentionally failing to give notice | Idaho Code 28-51-10726 |
| $2,000 and 1 year | Maximum fine and county jail term for an Idaho government employee who intentionally discloses personal information not allowed by law | Idaho Code 28-51-1057 |
| $25,000 or 50,000 | Idaho substitute notice thresholds: cost of notice over $25,000, or more than 50,000 Idaho residents | Idaho Code 28-51-104(4)8 |
| 262 | Breach notices posted by the Idaho Attorney General from Jan. 1, 2021 to Nov. 9, 2026 (this lesson's count of the page, read Nov. 14, 2026) | Idaho Attorney General15 |
| 36 months; about $150 to $450 | Credit monitoring proposed in Idaho's 2025 Senate Bill 1066 as introduced (cut to 12 months by Senate amendment), and the per-victim cost estimates in the committee minutes and revised statement of purpose; the bill did not become law | Idaho Legislature313233 |
| 60 days | HIPAA outer limit for notice to individuals, media and (for 500 or more) HHS | 45 CFR 164.404 to 164.4082 |
| 663; about 242.9 million | HIPAA breach reports of 500 or more people in calendar year 2024, and people affected | HHS OCR report to Congress, CY 202435 |
| about 192.7 million | People affected by the Change Healthcare breach, as of July 31, 2025 | HHS OCR36 |
| 30 days; 500 consumers | FTC Safeguards Rule notice to the FTC (effective May 13, 2024) | 16 CFR 314.4(j)3 |
| 30 days; 72 hours | SEC Regulation S-P customer notice; service provider notice to the firm | 17 CFR 248.3024 |
| Dec. 3, 2025; June 3, 2026 | Regulation S-P compliance dates for larger and smaller entities | 89 FR 476884 |
| 36 hours; 4 hours | Bank notice to its federal regulator; disruption length that triggers a bank service provider's notice to its bank customers | 86 FR 66424; 12 CFR Part 53511 |
| 72 hours | Credit union notice to NCUA (effective Sept. 1, 2023) | 12 CFR 748.1(c)42 |
| 4 business days | Form 8-K Item 1.05 after a materiality determination | 88 FR 518966 |
| 30 calendar days; 15 days; 500 | California resident notice and attorney general notice (more than 500 residents), effective Jan. 1, 2026 | SB 446 (2025)16 |
| 60 days; 30 days; 250 | Texas resident notice; attorney general notice for 250 or more Texans (since Sept. 1, 2023) | SB 768 (2023)19 |
| 12 months | Free credit monitoring Pennsylvania requires after certain breaches (since Sept. 26, 2024) | Pennsylvania 2024 amendment12 |
Common mistakes
Each of these comes from a public enforcement record or court case.
Keeping it quiet
In November 2016 hackers emailed Uber's chief security officer, Joseph Sullivan, saying they had stolen user data and demanding money. The Justice Department's account of the trial says Uber paid them $100,000 in bitcoin in December 2016 and had them sign nondisclosure agreements falsely stating that no data had been taken, while Uber was under an FTC investigation of its data security; the breach involved records of about 57 million users and 600,000 driver's license numbers and was not disclosed until November 2017. A federal jury convicted Sullivan on Oct. 5, 2022 of obstructing an FTC proceeding and misprision of a felony.54 The lesson for executives: a decision not to notify is a legal decision with personal consequences, and it must be made through the written process, not by the security team alone.
Telling less than you know
On July 16, 2020, Blackbaud, a software company serving nonprofits, announced that a ransomware attacker had not accessed donor bank account information or Social Security numbers. According to the SEC, within days its technology and customer relations staff learned that the attacker had in fact accessed and taken that data, but they did not tell the senior managers responsible for disclosure, and the company's August 2020 quarterly report left the information out and described the risk as hypothetical. Blackbaud agreed on March 9, 2023 to pay a $3 million civil penalty without admitting or denying the findings.55 The fix is a disclosure control: any fact that changes what was told to the public goes to the Notice Lead and the disclosure committee the same day.
Missing the outer limit
Presence Health, an Illinois health system, discovered on Oct. 22, 2013 that paper operating room schedules for 836 patients were missing. It notified HHS 101 days after discovery, the patients 104 days after and the media 106 days after, well past HIPAA's 60-day limit. In January 2017 it agreed to pay $475,000 and adopt a two-year corrective action plan, the Office for Civil Rights' first settlement over untimely breach notice.56 A clock log and a named owner for each deadline prevent this.
Slow notice and data kept too long
In March 2023 the New York Attorney General announced a $200,000 settlement with the law firm Heidell, Pittoni, Murphy and Bach after an attack through an unpatched Microsoft Exchange server exposed data about 114,979 people, 61,438 of them New Yorkers; the intrusion began in November 2021 and notices began in May 2022, and the settlement requires the firm to delete data once there is no reasonable business or legal purpose to keep it.57 The settlement required better patching, encryption, logging and data minimization. Every record kept past its retention date is one more letter to send after a breach; see lesson 7.
A first count that is far too low
Orrick, Herrington and Sutcliffe first reported about 153,000 people affected by its 2023 breach; more than 638,000 eventually received notices, and a federal judge in San Francisco gave final approval to an $8 million class settlement in November 2024.52 Change Healthcare filed with HHS using 500 as a placeholder while it worked out a number that later reached about 192.7 million.36 Placeholders are allowed, but the first public statement should say the count is preliminary and expected to change.
Not treating unauthorized sharing as a breach
The FTC's first two Health Breach Notification Rule cases, against GoodRx ($1.5 million civil penalty) and Easy Healthcare, maker of the Premom app ($100,000), were not about hackers. They were about the companies' own disclosure of health information to advertising and analytics firms without users' authorization, and the FTC wrote that theory into the 2024 amendments.39 Organizations that use tracking tools on patient or customer web pages should review what those tools send.
An Idaho public agency waits for the investigation
The 24-hour duty in Idaho Code 28-51-105 runs from discovery of a breach, and ITA Standard S6010 says agencies must notify "Regardless of the determination of misuse."729 A county or school district that waits for a forensic report before calling the Attorney General has already missed the deadline. The public list shows many agencies filing promptly, including dozens of school districts within days of each other in January 2025.15
Questions people ask
Ransomware encrypted our servers, but the forensic firm found no data left the network. Do we have to notify?
It depends on the law. Under Idaho's statute, a breach requires "illegal acquisition," so an attack that only made data unavailable may not trigger notice if the investigation reliably shows nothing was taken.8 Under HIPAA, the Office for Civil Rights' position since its July 2016 ransomware fact sheet is that ransomware encryption of protected health information is a presumed breach unless the entity shows a low probability of compromise under the four factors.582 In other states that use "access," the answer may also differ. Most ransomware groups now steal data before encrypting it, so "nothing left" needs strong evidence, such as complete network logs, before anyone relies on it. Write down the reasoning either way.
We are an Idaho company. Do other states' laws really apply to us?
Yes, for their residents. Breach laws protect the residents of the state that passed them, and most apply to any business that owns or licenses their personal information, wherever it is located. If an Idaho employer has remote employees in Washington and Utah, a payroll breach brings in Washington's 30-day deadline and attorney general notice for more than 500 Washingtonians, and Utah's own rules.18
Our vendor was breached. Who sends the letters, and who pays?
The owner or licensee of the data has the duty to notify the people; the vendor has the duty to tell the owner immediately and cooperate.7 Who pays is a contract question. Good contracts say the vendor reimburses notice, call center and credit monitoring costs for breaches it causes, and sometimes let the owner have the vendor send letters in the owner's name, as HHS allowed for Change Healthcare.36 See lesson 8.
Can we wait until the investigation is finished before we notify anyone?
Not for long. Laws allow time to determine the scope and identify the people, but the clocks run from discovery, and some (Idaho agencies' 24-hour call, the bank 36-hour rule, the 72-hour rules) run before any investigation can finish. The better practice is to notify regulators early with what is known, notify the people already identified, and supplement.
Is email notice enough?
Sometimes. Idaho allows electronic notice that is consistent with the federal E-SIGN Act, which in practice means the person has agreed to receive notices electronically.8 HIPAA allows email only if the individual agreed to electronic notice.2 Email is also how many phishing scams imitate breach notices, so organizations that use it should say how people can confirm the message is genuine, for example by visiting a page on the organization's main website.
Will the public see our notice?
Assume so. HHS posts HIPAA breaches of 500 or more; the FTC has said it intends to put Safeguards Rule reports in a public database; California, Washington, Maine, Idaho and other attorneys general post notices; and an 8-K is public on filing.3741222320156
Do we have to offer credit monitoring in Idaho?
Not under Idaho law as of Nov. 13, 2026. The 2025 bill that would have required it did not pass.9 Other states, such as Pennsylvania, do require it in some cases, and it is common practice after any breach of Social Security numbers.1221
Hard questions
Should Congress replace the state laws with one federal breach law?
For one federal law: A national organization now tracks 54 jurisdictions' definitions, triggers, deadlines, regulator notices and content rules, which change every year. A single national standard would cut cost and confusion, let people get one consistent letter, and allow one regulator to see the whole picture. Against preemption: States have been the place where breach law improved: they added online credentials, biometrics and fixed deadlines long before any federal proposal. A federal law that preempts state law could set a weaker floor and stop states from responding to new risks, and state attorneys general are often the most active enforcers. What the evidence shows: Congress has considered national breach bills for two decades without passing one, and the FTC, when it amended the Safeguards Rule in 2023, declined to add a consumer notice duty because "all States have some form of consumer notification requirement."41 The practical system is state law plus federal sector rules, and that is unlikely to change soon.
Fixed deadlines, or "without unreasonable delay"?
For fixed days: Deadlines are easy to enforce and stop organizations from treating "reasonable" as "whenever the investigation ends." The trend is plain: California moved from "most expedient time possible" to 30 calendar days, and New York to 30 days.1617 For a flexible standard: Large breaches can take weeks just to identify who was affected; a hard 30-day line can force notices that are incomplete or wrong, followed by confusing corrections, and can push organizations to notify everyone in a database rather than the people actually affected. What the evidence shows: The public cases above show more harm from delay and concealment than from early, honest, supplemented notices. Fixed outer limits paired with permission to notify in stages fit that evidence best.
Should Idaho update its law?
For updating: Idaho's definition misses online credentials, medical and health insurance data and biometrics, all of which neighboring states cover; businesses need not tell the Attorney General, so the public list misses most private-sector breaches; and there is no fixed day count. S1066's sponsor described aligning Idaho with industry practice.32 Against, or for a narrower change: Committee members worried about costs to public agencies, estimated at about $450 per victim for 36 months of monitoring or about $150 for 12 months; many regulated businesses already follow federal procedures that Idaho's 28-51-106 recognizes; and Idaho organizations with out-of-state customers already meet stricter laws.323325 What the evidence shows: The cost concern is real for small agencies, but the gaps in coverage are also real: an Idahoan whose online banking password is stolen from an Idaho-only business has no right to notice under Idaho law today. A narrower bill (wider definition, Attorney General notice above a threshold, a fixed outer limit, monitoring only for Social Security number breaches) would answer most of the committee's concerns.
Do breach notices actually help the people who get them?
Yes: Notice lets people freeze credit, change passwords, watch accounts and file taxes early, and public notices create pressure on organizations to protect data in the first place. Not much: After years of letters, many people ignore them; credit monitoring detects some fraud only after it happens; and stolen data rarely expires. What the evidence shows: The most useful notices are specific about the data taken and the steps that match it (a freeze for Social Security numbers, a password change for credentials, a new card for card data). The FTC's model letter is built that way, and organizations should follow it.21
For reporters and advocates
What public records exist.
- The Idaho Attorney General's breach list. Every notice the office has received since Jan. 1, 2021, by organization and date, with 262 entries as of Nov. 14, 2026.15 The underlying notices are records of a public agency; ask for them under the Idaho Public Records Act (Idaho Code Title 74, Chapter 1). Expect redactions of personal information and possibly of security details.
- State agency WebEOC reports. State agencies report incidents and breaches to ITS through WebEOC under ITA Standard S6010.29 Ask ITS and the Office of Risk Management how many incident and breach reports agencies filed each year, and how many breaches led to notice. Some details may be withheld as security records; the counts should not be.
- Other states' lists. California posts sample notification letters; Washington posts the number of Washingtonians affected and the data types, and publishes annual data breach reports; Maine posts the filings it receives through its online service.222320 Idaho companies with national customers often appear there even when they did not file in Idaho.
- Federal records. The HHS breach portal (HIPAA breaches of 500 or more); the FTC's database of Safeguards Rule reports, if and when posted; SEC EDGAR for Form 8-K Item 1.05 and 8.01 filings and 10-K Item 1C; FTC, SEC and HHS enforcement orders; and court dockets on PACER and CourtListener for class actions that follow large breaches.37416
- Legislative records. Bill texts, statements of purpose and committee minutes for Idaho's 2025 S1066 are online at legislature.idaho.gov.313332
What to ask an organization after a breach. When did you first learn of it, and when did you decide notice was required? How many people, in which states, and is the count final? What data, exactly, and was it encrypted with the key safe? Which regulators and attorneys general have you notified, and on what dates? What are you offering affected people, and for how long? Have you notified everyone you hold data for, and have your vendors notified you of everything they know? For a public agency in Idaho: when did you notify the Attorney General, and did you meet the 24-hour requirement?
What to ask public officials. For legislators: should Idaho add online credentials, health data and biometrics to its definition, require businesses to notify the Attorney General above a threshold, or set a fixed outer deadline? For the Attorney General: how many notices does the office receive each year from businesses that file voluntarily, and has the office ever used its civil enforcement power under 28-51-107? For county commissioners, city councils and school boards: does our agency have written breach procedures under 28-51-106, and when were they last exercised?
Where to go next
- FTC, Data Breach Response: A Guide for Business: Free FTC guide with a model notice letter and step-by-step response advice for any business; the best free starting template for a breach notice.
- HHS Office for Civil Rights breach portal: Free public list of HIPAA breaches of 500 or more under investigation; use it to see who was breached, how many people and what type of attack.
- Idaho Attorney General, Security Breaches: Free public list of breach notices the office has received since 2021; the main record of public agency breaches in Idaho.
- California Attorney General, Search Data Security Breaches: Free searchable list with sample notification letters; useful for seeing how organizations word real notices.
- Washington Attorney General, Data Breach Notifications: Free directory with the number of residents affected and the data types, plus annual data breach reports; good for trend data.
- Idaho Technology Authority policies and standards: Free Idaho state IT policies, including P4590 and S6010 on incident and breach response; a model for any Idaho public agency or vendor.
- NIST SP 800-61 Revision 3, Incident Response Recommendations: Free NIST guide to incident response, which runs alongside the notice job; mapped to the Cybersecurity Framework 2.0.
Still being checked (5 items)
These points could not be fully confirmed against a primary source when this lesson was written and fact checked in November 2026. The text above states each one as uncertain.
- The exact text of Texas Business and Commerce Code 521.053 and 521.151 was not read in the primary statute; the Texas changes (30-day attorney general notice for 250 or more residents, 60-day resident notice, electronic form, effective Sept. 1, 2023) come from the Senate Research Center bill analysis of SB 768 and are stated as such.
- The California (SB 446), New York (2024 amendment to 899-aa), Pennsylvania (2024), Oklahoma (SB 626) and Washington (RCW 19.255.010 details beyond the timing) summaries rely on law firm summaries and, for Washington, the statute page; the full enacted statutory text of the 2024 and 2025 amendments was not read line by line.
- The count of 262 entries on the Idaho Attorney General's breach list, and the yearly and school-type breakdowns, are this lesson's own tally of the posted page as read Nov. 14, 2026; the office does not publish totals, and the list undercounts private-sector breaches because businesses may file voluntarily.
- Whether Idaho Technology Authority policies P4590 and S6010 bind local agencies (counties, cities, school districts) as well as state executive agencies was not confirmed from a primary source; the 24-hour Attorney General duty in 28-51-105 applies to all agencies regardless.
- CIRCIA's final rule status (reported sent to OMB on Oct. 1, 2026) rests on a law firm report; a Federal Register search on Nov. 13, 2026 found no published final rule, so CIRCIA reporting is stated as not yet mandatory.
Last verified November 14, 2026. General education, not legal, compliance, audit or other professional advice; rule versions and dates are stated in the text, and the sources used are listed in the Notes and Sources below. Check the regulator's current text before relying on any point.
Notes
- National Conference of State Legislatures, "Security Breach Notification Laws," summary updated Jan. 17, 2022, listing all 50 states, the District of Columbia, Guam, Puerto Rico and the Virgin Islands with statute citations; later amendments are not reflected (read Nov. 13, 2026). Read it online. ↩
- 45 CFR Part 164, Subpart D, Notification in the Case of Breach of Unsecured Protected Health Information, sections 164.400 to 164.414 (164.402 definitions and four-factor assessment; 164.404 individuals, content, methods and substitute notice; 164.406 media; 164.408 Secretary; 164.410 business associates; 164.412 law enforcement delay; 164.414 burden of proof), 74 FR 42767 (Aug. 24, 2009), as amended 78 FR 5695 (Jan. 25, 2013); eCFR text current to Nov. 10, 2026 (read Nov. 13, 2026). Read it online. ↩
- 16 CFR Part 314, Standards for Safeguarding Customer Information (FTC Safeguards Rule), including 314.2 (definition of notification event) and 314.4(j) (notice to the FTC within 30 days for 500 or more consumers; contents; law enforcement delay of public posting); eCFR text current to Nov. 10, 2026 (read Nov. 13, 2026). Read it online. ↩
- Securities and Exchange Commission, "Regulation S-P: Privacy of Consumer Financial Information and Safeguarding Customer Information," final rule, 89 FR 47688 (June 3, 2024), effective Aug. 2, 2024; compliance dates 18 months (larger entities) and 24 months (smaller entities) after publication; Table 3 defines larger entities; see also SEC press release 2024-58 (May 16, 2024) and the correction at 89 FR 53487 (June 27, 2024) (read Nov. 13, 2026). Read it online. ↩
- Office of the Comptroller of the Currency, Federal Reserve Board and FDIC, "Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers," final rule, 86 FR 66424 (Nov. 23, 2021), effective April 1, 2022, compliance date May 1, 2022 (read Nov. 13, 2026). Read it online. ↩
- Securities and Exchange Commission, "Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure," final rule, 88 FR 51896 (Aug. 4, 2023), adopted July 26, 2023 (Form 8-K Item 1.05 within four business days of determining an incident is material; national security or public safety delay; Regulation S-K Item 106) (read Nov. 13, 2026). Read it online. ↩
- Idaho Code 28-51-105, Disclosure of breach of security of computerized personal information by an agency, individual or a commercial entity, added 2006, ch. 258, sec. 1; amended 2014, ch. 97, sec. 13; current text posted by the Idaho Legislature (Idaho statutes are updated online each July 1 after the session) (read Nov. 13, 2026). Read it online. ↩
- Idaho Code 28-51-104, Definitions, added 2006, ch. 258, sec. 1; amended 2015, ch. 141, sec. 51; current text posted by the Idaho Legislature (read Nov. 13, 2026). Read it online. ↩
- Idaho Legislature, S1066 (2025) bill status page: introduced Feb. 7, 2025; reported out of committee to the 14th Order for amendment Feb. 14; amended in the Committee of the Whole March 4; passed the Senate 27-6-2 March 10; House Business Committee do-pass recommendation March 17; placed on General Orders March 19 and retained there through April 4, 2025, the last recorded action; not enacted (read Nov. 14, 2026). Read it online. ↩
- Idaho Legislature, 2026 session laws list (chapter number, bill, subject, signature and effective dates); no chapter amends Idaho Code Title 28, Chapter 51 (this lesson's review of the list) (read Nov. 13, 2026). Read it online. ↩
- 12 CFR Part 53, Computer-Security Incident Notification (OCC), including 53.2 (definition of notification incident), 53.3 (notice within 36 hours) and 53.4 (bank service provider notice for disruptions of four or more hours); the Federal Reserve and FDIC rules are at 12 CFR Part 225, Subpart N and 12 CFR Part 304, Subpart C; eCFR text current to Nov. 10, 2026 (read Nov. 13, 2026). Read it online. ↩
- BakerHostetler, "Pennsylvania Makes Significant Changes to Its Data Breach Notification Law" (2024), summarizing the amendment to the Breach of Personal Information Notification Act signed June 28, 2024 and effective Sept. 26, 2024 (attorney general notice for more than 500 residents; 12 months of credit monitoring; new data elements); secondary summary of the statute (read Nov. 13, 2026). Read it online. ↩
- Covington and Burling, Inside Privacy, "Oklahoma Substantially Amends Its Data Breach Notification Statute" (2025), summarizing Senate Bill 626, effective Jan. 1, 2026 (biometric data; attorney general notice for 500 or more residents, 1,000 for credit bureaus, within 60 days after individual notice; reasonable safeguards and penalties); secondary summary of the statute (read Nov. 13, 2026). Read it online. ↩
- U.S. Department of Health and Human Services, "Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals" (read Nov. 13, 2026). Read it online. ↩
- Idaho Office of the Attorney General, Consumer Protection Division, "Security Breaches" (statement of the 24-hour duty for public agencies; commercial entities "may notify" but are not required to; list of notices received since Jan. 1, 2021; 262 entries counted for this lesson, by notification year: 2021, 37; 2022, 28; 2023, 34; 2024, 25; 2025, 94; 2026 through Nov. 9, 44) (read Nov. 14, 2026). Read it online. ↩
- Norton Rose Fulbright, Data Protection Report, "California Tightens Data Breach Notification Timelines, Imposes 30-Day Notice Requirement" (Nov. 5, 2025), describing SB 446 amending Cal. Civ. Code 1798.82, effective Jan. 1, 2026 (30 calendar days from discovery; attorney general notice for more than 500 residents within 15 calendar days after individual notice; 30 days for owners after a vendor's notice); secondary summary of the statute (read Nov. 13, 2026). Read it online. ↩
- Covington and Burling, Inside Privacy, "New York Adopts Amendment to the State Data Breach Notification Law" (January 2025), describing the amendment to N.Y. General Business Law 899-aa signed Dec. 24, 2024 and effective immediately (30 days from discovery; notice to the Department of Financial Services added); secondary summary of the statute (read Nov. 13, 2026). Read it online. ↩
- Revised Code of Washington 19.255.010, Disclosure, notice (30 calendar days; attorney general notice for more than 500 Washington residents within 30 days; plain-language content requirements), Washington State Legislature (read Nov. 13, 2026). Read it online. ↩
- Texas Legislature, Senate Research Center bill analysis of S.B. 768, 88th Legislature (2023), enrolled version: attorney general notice for breaches involving at least 250 Texans moved from the 60th to the 30th day, on an electronic form; effective Sept. 1, 2023; the statement of intent describes a public listing of reported breaches (read Nov. 13, 2026). Read it online. ↩
- Office of the Maine Attorney General, "Data Security Breaches" (online reporting service for notices to the Attorney General) (read Nov. 13, 2026). Read it online. ↩
- Federal Trade Commission, Data Breach Response: A Guide for Business (guide dated August 2023; web page modified June 20, 2025), including the model "Notice of Data Breach" letter and the recommendation to consider at least a year of free credit monitoring (read Nov. 13, 2026). Read it online. ↩
- Office of the California Attorney General, "Search Data Security Breaches" (searchable list with sample notification letters and a downloadable CSV of the full list) (read Nov. 13, 2026). Read it online. ↩
- Washington State Office of the Attorney General, "Data Breach Notifications Directory" (date reported, organization, date of breach, number of Washingtonians affected, information compromised; annual Data Breach Reports) (read Nov. 13, 2026). Read it online. ↩
- 17 CFR 248.30, Procedures to safeguard customer information, including response programs, customer notification within 30 days, Attorney General delay, and service provider notice within 72 hours (Regulation S-P as amended 2024); eCFR text current to Nov. 10, 2026 (read Nov. 13, 2026). Read it online. ↩
- Idaho Code 28-51-106, Procedures deemed in compliance with security breach requirements, added 2006, ch. 258, sec. 1; current text posted by the Idaho Legislature (read Nov. 13, 2026). Read it online. ↩
- Idaho Code 28-51-107, Violations, added 2006, ch. 258, sec. 1; current text posted by the Idaho Legislature (read Nov. 13, 2026). Read it online. ↩
- Idaho Code 74-101, Definitions (Public Records Act), including "local agency," "public agency" and "state agency"; current text posted by the Idaho Legislature (read Nov. 13, 2026). Read it online. ↩
- Idaho Technology Authority, Enterprise Policy P4590, Cybersecurity Incident and Breach Response Management and Reporting (effective May 30, 2019; revised May 31, 2022; authority Idaho Code 67-831 to 67-833; 12-month review cycle) (read Nov. 13, 2026). Read it online. ↩
- Idaho Technology Authority, Enterprise Standard S6010, Cybersecurity Incident and Breach Response Management and Reporting (effective Feb. 19, 2019; revised June 18, 2019, April 20, 2021 and July 23, 2025), with the attached State of Idaho Incident Response Reporting Handbook, revision 1.03 (Oct. 16, 2020): breach notice to the Attorney General's office, the Office of Risk Management and ITS within 24 hours regardless of the determination of misuse; incident reports through WebEOC within five business days; VERIS; sample notice letter (read Nov. 13, 2026). Read it online. ↩
- Idaho Legislature, House Bill 35 (2025), "Relating to Information Technology Services and Cybersecurity" (multifactor identification; ITS cybersecurity duties), enacted as 2025 session law chapter 6, signed Feb. 24, 2025, effective July 1, 2025, per the 2025 session laws list (read Nov. 13, 2026). Read it online. ↩
- Idaho Legislature, Senate Bill 1066 (2025), Senate Commerce and Human Resources Committee, "Relating to Identity Theft" (amending Idaho Code 28-51-104, 28-51-105 and 28-51-106: personally identifiable information; added data elements; 36 months of credit monitoring), as printed (read Nov. 13, 2026). Read it online. ↩
- Idaho Senate Commerce and Human Resources Committee, minutes of Feb. 13, 2025 (S 1066 presented by Sen. Toews; cost questions; estimated $450 per victim for 36 months; motion to send to the 14th Order for possible amendment carried by voice vote) (read Nov. 13, 2026). Read it online. ↩
- Idaho Legislature, Statement of Purpose and Fiscal Note, RS32131 / S1066, revised March 7, 2025 (about $150 per victim for 12 months of credit monitoring); prepared by a proponent and not an expression of legislative intent (read Nov. 13, 2026). Read it online. ↩
- HHS, "Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules" (the Omnibus Rule), 78 FR 5566 (Jan. 25, 2013), effective March 26, 2013, replacing the 2009 harm standard with the presumption and four-factor assessment (read Nov. 13, 2026). Read it online. ↩
- HHS Office for Civil Rights, Annual Report to Congress on Breaches of Unsecured Protected Health Information for Calendar Year 2024 (663 reports of 500 or more affecting about 242,908,056 individuals; 74,299 reports of fewer than 500 affecting about 340,618) (read Nov. 13, 2026). Read it online. ↩
- HHS Office for Civil Rights, "Change Healthcare Cybersecurity Incident Frequently Asked Questions" (initial breach report July 19, 2024, listing 500, the minimum number for posting on the breach portal, while Change Healthcare determined the count; about 192.7 million people affected as of July 31, 2025; covered entities may delegate notification to Change Healthcare) (read Nov. 13, 2026). Read it online. ↩
- HHS Office for Civil Rights, Breach Portal, "Cases Currently Under Investigation" (breaches of 500 or more reported within the last 24 months) (read Nov. 13, 2026). Read it online. ↩
- SecurityWeek, "460k Impacted by Kootenai Health Ransomware Attack" (2024), reporting 464,088 people per the filing with the Maine Attorney General; press report (read Nov. 13, 2026). Read it online. ↩
- Federal Trade Commission, "Health Breach Notification Rule," final rule, 89 FR 47028 (May 30, 2024), effective July 29, 2024, citing the GoodRx ($1.5 million civil penalty) and Easy Healthcare (Premom, $100,000) actions (read Nov. 13, 2026). Read it online. ↩
- 16 CFR Part 318, Health Breach Notification Rule, including 318.2 (breach of security includes unauthorized disclosure), 318.4 (60 calendar days; FTC notice for 500 or more at the same time; annual log for fewer than 500) and 318.7 (civil penalties); eCFR text current to Nov. 10, 2026 (read Nov. 13, 2026). Read it online. ↩
- Federal Trade Commission, "Standards for Safeguarding Customer Information," final rule, 88 FR 77499 (Nov. 13, 2023), effective May 13, 2024 (the Commission "intends to enter notification event reports into a publicly available database"; no consumer notice requirement because all states have one) (read Nov. 13, 2026). Read it online. ↩
- 12 CFR Part 748, Security Program, Report of Suspected Crimes, Suspicious Transactions, Catastrophic Acts, Cyber Incidents, and Bank Secrecy Act Compliance (NCUA), including 748.1(c) (cyber incident notice within 72 hours) and Appendix B, Guidance on Response Programs for Unauthorized Access to Member Information and Member Notice; eCFR text current to Nov. 4, 2026 (read Nov. 13, 2026). Read it online. ↩
- National Credit Union Administration, "Cyber Incident Notification Requirements for Federally Insured Credit Unions," final rule, 88 FR 12811 (March 1, 2023), effective Sept. 1, 2023 (read Nov. 13, 2026). Read it online. ↩
- National Credit Union Administration, "Guidance on Response Programs for Unauthorized Access to Member Information and Member Notice," proposed rule, 90 FR 57397 (Dec. 11, 2025), proposing to remove Appendix B to Part 748 and publish it as guidance; comments due Feb. 9, 2026 (read Nov. 13, 2026). Read it online. ↩
- Erik Gerding, Director, SEC Division of Corporation Finance, "Disclosure of Cybersecurity Incidents Determined To Be Material and Other Cybersecurity Incidents" (May 21, 2024) (read Nov. 13, 2026). Read it online. ↩
- Statement by SEC Chairman Paul Atkins on reforming Regulation S-K (January 2026), as posted by the Harvard Law School Forum on Corporate Governance, Jan. 15, 2026; no proposal to amend Item 1.05 found in the Federal Register through Nov. 13, 2026 (read Nov. 13, 2026). Read it online. ↩
- 23 NYCRR 500.17, Notices to superintendent (72 hours after determining a cybersecurity incident; extortion payment notice within 24 hours and explanation within 30 days), Cornell Legal Information Institute copy of the New York regulation (read Nov. 13, 2026). Read it online. ↩
- Defense Federal Acquisition Regulation Supplement 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting ("rapidly report" means within 72 hours of discovery), Acquisition.gov (read Nov. 13, 2026). Read it online. ↩
- Cybersecurity and Infrastructure Security Agency, "Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) Reporting Requirements," proposed rule, 89 FR 23644 (April 4, 2024) (72-hour incident and 24-hour ransom payment reports); a Federal Register search on Nov. 13, 2026 found no final rule (read Nov. 13, 2026). Read it online. ↩
- Covington and Burling, Inside Privacy, "CISA Submits Final CIRCIA Rule for OMB Review" (October 2026), reporting submission to the Office of Information and Regulatory Affairs on Oct. 1, 2026; press report (read Nov. 13, 2026). Read it online. ↩
- Regulation (EU) 2016/679 (General Data Protection Regulation), Article 33, Notification of a personal data breach to the supervisory authority, EUR-Lex (read Nov. 13, 2026). Read it online. ↩
- ABA Journal, "Judge gives final OK to $8M settlement in Orrick data breach" (Nov. 12, 2024) (first report of about 153,000 people; more than 638,000 notified); press report (read Nov. 13, 2026). Read it online. ↩
- 45 CFR 164.530(j), Documentation (retain required documentation for six years from creation or last effective date), Cornell Legal Information Institute copy of the eCFR (read Nov. 13, 2026). Read it online. ↩
- U.S. Attorney's Office, Northern District of California, "Former Chief Security Officer Of Uber Convicted Of Federal Charges For Covering Up Data Breach Involving Millions Of Uber User Records" (Oct. 5, 2022) (read Nov. 13, 2026). Read it online. ↩
- Securities and Exchange Commission, press release 2023-48, "SEC Charges Software Company Blackbaud Inc. for Misleading Disclosures About Ransomware Attack That Impacted Charitable Donors" (March 9, 2023) ($3 million civil penalty) (read Nov. 13, 2026). Read it online. ↩
- HHS Office for Civil Rights, Resolution Agreement and Corrective Action Plan with Presence Health Network, announced Jan. 9, 2017 ($475,000; discovery Oct. 22, 2013; 836 individuals; notice to OCR 101 days, individuals 104 days and media 106 days after discovery) (read Nov. 13, 2026). Read it online. ↩
- Office of the New York State Attorney General, "Attorney General James Secures $200,000 from Law Firm for Failing to Protect New Yorkers' Personal Data" (March 27, 2023), on Heidell, Pittoni, Murphy and Bach LLP (114,979 people, 61,438 New Yorkers) (read Nov. 13, 2026). Read it online. ↩
- HHS Office for Civil Rights, Fact Sheet: Ransomware and HIPAA (July 11, 2016) (read Nov. 13, 2026). Read it online. ↩
- Idaho Legislature, Senate Amendment to S.B. No. 1066 (2025), moved by Sen. Toews (S1066A1): cuts credit monitoring from 36 to 12 months, deletes health insurance identifiers, adds a definition of encryption and excludes acquisition of data from sources other than systems maintained by the organization or its service provider; see also the engrossed bill S1066E1 (read Nov. 14, 2026). Read it online. ↩
- Hunton Andrews Kurth, Privacy and Cybersecurity Law Blog, "Pennsylvania Amends Breach Notification Law" (Nov. 14, 2022), describing Senate Bill 696, signed Nov. 3, 2022 and effective May 2, 2023, which added medical information, health insurance information, and a username or email address with a password or security question and answer; secondary summary of the statute (read Nov. 14, 2026). Read it online. ↩
- Maine Revised Statutes, Title 10, section 1348, Security breach notice requirements (good-faith, reasonable and prompt investigation; notice no more than 30 days after becoming aware of a breach and identifying its scope; no more than 7 business days after a law enforcement agency determines notice will not compromise a criminal investigation; consumer reporting agency notice above 1,000 persons), Maine Legislature (read Nov. 14, 2026). Read it online. ↩
Check yourself
1. How soon must an Idaho public agency notify the Idaho Attorney General after discovering a breach?
Idaho Code 28-51-105 requires an agency to notify the Attorney General's office within 24 hours of discovering a breach, and ITA Standard S6010 adds that this is required regardless of the determination of misuse.
2. Under Idaho Code 28-51-104, which data is protected only when it is not encrypted?
28-51-104(5) defines personal information as a name with a Social Security number, driver's license or Idaho ID number, or a financial account or card number with the code needed to use it, and only when not encrypted. Online credentials are not on Idaho's list.
3. What is the maximum penalty under Idaho Code 28-51-107 for intentionally failing to give required breach notice?
28-51-107 lets the primary regulator sue to enforce and sets a fine of not more than $25,000 per breach of the security of the system for an intentional failure to notify.
4. Under the HIPAA Breach Notification Rule, an impermissible use or disclosure of protected health information is:
45 CFR 164.402, as amended by the 2013 Omnibus Rule, presumes a breach unless the covered entity shows a low probability that the PHI was compromised based on at least four factors.
5. A non-bank financial institution under the FTC Safeguards Rule discovers a notification event affecting 700 consumers. What must it do?
16 CFR 314.4(j), effective May 13, 2024, requires notice to the FTC as soon as possible and no later than 30 days after discovery of a notification event involving at least 500 consumers.
6. Which statement about SEC Regulation S-P as amended in 2024 is correct?
17 CFR 248.30 requires covered firms to notify affected individuals as soon as practicable but no later than 30 days, and to ensure service providers notify the firm no later than 72 hours after becoming aware of a breach; compliance dates were Dec. 3, 2025 (larger) and June 3, 2026 (smaller).
7. When does the clock for most breach notice deadlines begin?
HIPAA treats a breach as discovered on the first day it is known, or with reasonable diligence would have been known, to any workforce member other than the person who caused it; most state clocks also run from discovery, not from the end of the investigation.
8. Which of these did Idaho's 2025 Senate Bill 1066 propose, and what happened to it?
S1066 as introduced would have widened the definition of personal information and required at least 36 months of credit monitoring (cut to 12 months by Senate amendment); it passed the Senate in March 2025 but was held on the House General Orders calendar and never became law, and the 2026 session made no change to Chapter 51.
9. An organization maintains personal information it does not own and discovers a breach affecting Idaho residents. Under Idaho Code 28-51-105(2), it must:
28-51-105(2) requires a service provider that maintains but does not own the data to notify and cooperate with the owner or licensee immediately following discovery if misuse has occurred or is reasonably likely; the owner then notifies the people.
10. How does Idaho Code 28-51-106 treat a regulated organization that follows its regulator's breach procedures?
28-51-106(2) deems an organization regulated by state or federal law to comply with 28-51-105 if it maintains and follows breach procedures under its primary or functional regulator; the safe harbor covers only Idaho's requirement, not other states' laws.
Terms in this lesson
- Breach of the security of the system (Idaho)
- Under Idaho Code 28-51-104, the illegal acquisition of unencrypted computerized data that materially compromises the security, confidentiality or integrity of personal information.
- Notification event
- The FTC Safeguards Rule's term for acquisition of unencrypted customer information without the authorization of the person it concerns; access is presumed to include acquisition unless evidence shows otherwise.
- Risk-of-harm trigger
- A rule that requires notice only when the breach is likely to cause harm. Idaho requires notice only if misuse has occurred or is reasonably likely; HIPAA instead presumes a breach and requires proof of a low probability of compromise.
- Encryption safe harbor
- A provision that takes properly encrypted data (with the key kept safe) out of the notice duty. Idaho's law reaches data only when it is not encrypted.
- Substitute notice
- A method of notice (email, website posting and statewide media in Idaho) allowed when direct notice is impractical, for example when the cost exceeds $25,000 or more than 50,000 Idaho residents are affected.
- Primary regulator (Idaho)
- Under 28-51-104(6), the federal or state agency that regulates an organization: its federal regulator, the Idaho Department of Finance, the Idaho Department of Insurance, or, for everyone else, the Idaho Attorney General.
- Owner or licensee vs. maintainer
- The distinction between the organization that owns or licenses data and must notify the people, and a service provider that only maintains data and must tell the owner.
- Clock log
- A dated record of when an organization first learned each fact about an incident and which deadlines each fact starts; the baseline a regulator uses to judge whether notice was timely.
- Notice matrix
- A table with one row per jurisdiction listing the number of residents, whether notice is required, the deadline, regulator and credit bureau thresholds, content rules and safe harbors.
- Form 8-K Item 1.05
- The SEC form a public company files within four business days of deciding a cybersecurity incident is material; a disclosure to investors, not a notice to the people whose data was taken.
- 36-hour rule
- The federal banking agencies' requirement that a banking organization notify its primary federal regulator within 36 hours of determining a notification incident has occurred.
- WebEOC
- Idaho's emergency management reporting system, through which state agencies report cybersecurity incidents and breaches to the ITS security office under ITA Standard S6010.
- Unsecured protected health information
- Under HIPAA, PHI that is not rendered unusable, unreadable or indecipherable through encryption or destruction meeting HHS guidance; only unsecured PHI triggers the breach notice duty.
- CIRCIA
- The Cyber Incident Reporting for Critical Infrastructure Act of 2022, which will require 72-hour incident and 24-hour ransom payment reports to CISA once the final rule takes effect; not yet mandatory as of Nov. 13, 2026.
Sources
- Idaho Code 28-51-104, Definitions (2026-11-13) checked 2026-11
- Idaho Code 28-51-105, Disclosure of breach (2026-11-13) checked 2026-11
- Idaho Code 28-51-106, Procedures deemed in compliance (2026-11-13) checked 2026-11
- Idaho Code 28-51-107, Violations (2026-11-13) checked 2026-11
- Idaho Technology Authority Standard S6010, Cybersecurity Incident and Breach Response (2026-11-13) checked 2026-11
- Idaho Attorney General, Security Breaches list (2026-11-13) checked 2026-11
- 45 CFR Part 164, Subpart D (HIPAA Breach Notification Rule) (2026-11-13) checked 2026-11
- 16 CFR 314.4(j), FTC Safeguards Rule notification duty (2026-11-13) checked 2026-11
- 16 CFR Part 318, FTC Health Breach Notification Rule (2026-11-13) checked 2026-11
- 17 CFR 248.30, Regulation S-P (as amended, 89 FR 47688) (2026-11-13) checked 2026-11
- 12 CFR Part 53, bank Computer-Security Incident Notification (86 FR 66424) (2026-11-13) checked 2026-11
- 12 CFR Part 748, NCUA cyber incident notification and Appendix B (2026-11-13) checked 2026-11
- SEC Form 8-K Item 1.05 final rule, 88 FR 51896 (2026-11-13) checked 2026-11
- NCSL, Security Breach Notification Laws (2026-11-13) checked 2026-11
- Idaho Legislature, Senate Bill 1066 (2025) (2026-11-13) checked 2026-11