Law / United States / Arizona

Arizona

13 of 15 named instruments researched to a stage, across five of the ten areas of law we track: 13 in force. As of .

When each starts9 of 13 carry a date, 4 do not. Earlier is before 2014.
Before 2014: 2 instruments (2 in force) earlier 2014: 0 instruments 2015: 0 instruments ’15 2016: 0 instruments 2017: 0 instruments 2018: 0 instruments 2019: 0 instruments 2020: 0 instruments ’20 2021: 0 instruments 2022: 1 instrument (1 in force) 2023: 0 instruments 2024: 2 instruments (2 in force) 2025: 3 instruments (3 in force) 2026: 1 instrument (1 in force) ’26 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 5
  2. Privacy law 1
  3. Scraping law 3
  4. Cybersecurity law 3
  5. Communications law not researched
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law 1
  10. Reuse law

AI law5 instruments, 5 in force

Research summary (450 words)

Arizona has no general-purpose AI-transparency or algorithmic-accountability statute of broad application. Five narrower measures are in force.

A.R.S. § 16-1023 creates a private declaratory and injunctive cause of action for any Arizona resident depicted in a non-consensual, undisclosed digital impersonation (a deepfake using deep generative AI methods), with an expedited preliminary-relief track for election candidates and other specified categories; enacted as an emergency measure effective , with the section applying fourteen days after that date.

A.R.S. § 16-1024, enacted eight days later in the same legislative session, separately requires a person distributing synthetic media depicting a candidate within ninety days of an election to disclose that the content was AI-generated, backed by a civil penalty under A.R.S. § 16-937(B), with exemptions for satire, parody, and interactive computer services.

A.R.S. § 20-3103, in force from under Laws 2025, chapter 165, bars a health care insurer from denying a claim on medical-necessity grounds without an individualized review by a medical director exercising independent judgment; the statute's own text and the Legislature's own fact sheet for the enacting bill describe this duty in technology-neutral terms and do not themselves use the term artificial intelligence, though contemporaneous news coverage of the bill's passage frames it as a response to insurers' use of AI and algorithmic tools in claims review.

Two 2025 amendments extend Title 13's sexual-offense definitions to reach AI-generated content: HB 2678 (2025 Ariz. Sess. Laws ch. 174) amends A.R.S. §§ 13-3551 and 13-705 so that a computer-generated or digitally altered image indistinguishable from an actual minor is treated the same as an image of a real child, exposing a person who produces, distributes, or possesses such a depiction to the class 2 felony liability Title 13, chapter 35.1 imposes for child exploitation, enhanced under § 13-705 where the depicted minor is under fifteen; and SB 1462 (2025 Ariz. Sess. Laws ch. 106) amends A.R.S. § 13-1425 to add a 'realistic pictorial representation' (an AI-generated or digitally altered image reasonably appearing to be an actual, non-consensual intimate depiction of a person) to the statute's unlawful-disclosure prohibition, though disclosing that kind of synthetic image is itself classified only as a class 1 misdemeanor, a lower tier than the class 5 or class 4 felony that applies to disclosure of a genuine image.

Outside these enacted measures, the Arizona Consumer Fraud Act, A.R.S. §§ 44-1521 to 44-1534, is a general deceptive-practices statute; it names no AI system and creates no AI-specific duty. The Arizona Department of Administration's Statewide Policy P2000 (rev. ) is an executive-branch policy, not a statute, governing state agencies' own use of generative AI tools; it binds no private person and creates no enforceable right.

AI prohibited practices

AI-generated and indistinguishable depictions included in child-exploitation definitions (HB 2678)

A.R.S. §§ 13-3551, 13-705; 2025 Ariz. Sess. Laws ch. 174 (HB 2678, 57th Leg., 1st Reg. Sess.)official Arizona Revised Statutes text, Arizona State Legislature website

In force since . Binds public and private bodies.

What this law does

Arizona's chapter on sexual exploitation of children defines 'visual depiction' to include an image created or modified by computer software, artificial intelligence, or other digital editing tools. It defines 'minor' to include a visual depiction that is 'indistinguishable' from an actual minor. 'Indistinguishable' means a visual depiction such that a person viewing it would reasonably conclude it is of an actual minor.

Commercial sexual exploitation of a minor under A.R.S. § 13-3552 is a class 2 felony. Sexual exploitation of a minor under A.R.S. § 13-3553 is also a class 2 felony. Where the depicted minor, including an indistinguishable AI-generated depiction, is under fifteen years of age, A.R.S. § 13-705 reclassifies the offense as a dangerous crime against children in the first degree.

A first offense of commercial sexual exploitation of a minor under that reclassification carries a sentencing range of thirteen to twenty-seven years. A first offense of sexual exploitation of a minor under that reclassification carries a sentencing range of ten to twenty-four years. This measure was enacted as House Bill 2678 and approved by the Governor on , as 2025 Arizona Session Laws chapter 174, which carries no effective-date section or emergency clause of its own.

The Arizona Legislature's own General Effective Dates page states the 2025 First Regular Session's general effective date as .

What it requires

Unlawful disclosure extended to AI-generated 'realistic pictorial representation' intimate images (SB 1462)

A.R.S. § 13-1425; 2025 Ariz. Sess. Laws ch. 106 (SB 1462, 57th Leg., 1st Reg. Sess.)official Arizona Revised Statutes text, Arizona State Legislature website

In force since . Binds public and private bodies.

What this law does

Arizona's unlawful-disclosure-of-intimate-images statute defines a 'realistic pictorial representation' as an image created or modified to reasonably appear to be an actual image of an identifiable person depicted in a state of nudity or engaged in specific sexual activities that did not actually occur.

Intentionally disclosing an identifiable person's realistic pictorial representation, where the person has a reasonable expectation of privacy and the disclosure is made with intent to harm, harass, intimidate, threaten, or coerce them, is a class 1 misdemeanor. That is a lower tier than the class 5 felony, or class 4 felony if disclosed by electronic means, that applies to disclosure of a genuine, non-synthetic image.

This measure was enacted as Senate Bill 1462 and approved by the Governor on , as 2025 Arizona Session Laws chapter 106, which carries no effective-date section or emergency clause of its own. The Arizona Legislature's own General Effective Dates page states the 2025 First Regular Session's general effective date as .

What it requires

AI sector rules

Denial of claims; individualized review requirement

A.R.S. § 20-3103official Arizona Revised Statutes text, Arizona State Legislature website

In force since . Binds private bodies.

What this law does

Before a health care insurer may deny a claim submitted by a provider on the basis of medical necessity, a medical director must individually review the denial, exercise independent medical judgment, and may not rely solely on recommendations from any other source.

The section's own text and the Arizona Senate's fact sheet for the enacting bill, HB 2175 (2025), state this duty in technology-neutral terms; neither document uses the term artificial intelligence, though contemporaneous news coverage of the bill's passage describes it as a response to insurers' use of AI and algorithm-based tools to automate medical-necessity and prior-authorization denials.

Enacted in 2025 as Laws 2025, chapter 165 (HB 2175), approved by the Governor on , with the act itself providing that it is effective from and after .

What it requires

AI transparency

Deepfakes; candidate disclosure requirement and civil penalty

A.R.S. § 16-1024official Arizona Revised Statutes text, Arizona State Legislature website

In force since . Binds public and private bodies.

What this law does

Within ninety days before an election at which a candidate appears on the ballot, a creator, meaning any person who uses artificial intelligence or other digital technology to generate synthetic media, other than a provider of the underlying technology, may not create and distribute a deceptive and fraudulent deepfake of that candidate, meaning synthetic media the creator knows is false and intends to injure the candidate's reputation and that is intentionally calculated to mislead a reasonable person, unless the media carries a clear and conspicuous disclosure that it includes content generated by artificial intelligence.

Satire, parody, and an interactive computer service as defined in 47 U.S.C. § 230 are exempt. A creator who fails to make the required disclosure is liable for the civil penalty prescribed by A.R.S. § 16-937(B) for each day the undisclosed deepfake is distributed. Enacted as chapter 199 of the 2024 session laws, this section was approved by the Governor on .

Unlike its companion section 16-1023, it carries a severability clause rather than an emergency clause, so it took effect on the legislative session's general effective date rather than immediately on signature. The Arizona Legislature's own General Effective Dates page states that day, for the 2024 Second Regular Session, as .

What it requires

Digital impersonation of a candidate or other person (civil action)

A.R.S. § 16-1023official Arizona Revised Statutes text, Arizona State Legislature website

In force since . Binds public and private bodies.

What this law does

A candidate for public office or political party office, or any citizen of Arizona, may bring an action for digital impersonation, defined as synthetic media digitally manipulated or generated using deep generative methods and artificial intelligence techniques to convincingly replace or simulate a person's likeness or voice, created with intent to deceive, that a reasonable viewer or listener would believe is an authentic depiction, and that is not commentary, parody, satire, criticism, or artistic expression.

Liability turns on non-disclosure: a plaintiff must show the digital impersonation was published without the publisher reasonably conveying that it was a digital impersonation or that its authenticity was disputed, or that this would not be obvious to a reasonable person.

The sole remedy is preliminary and permanent declaratory relief unless the plaintiff also proves an additional element, such as a pending election within one hundred eighty days for a candidate-plaintiff, a sexual or criminal-act depiction, or reasonably expected personal, financial, or reputational harm, in which case injunctive relief and damages are also available.

An interactive computer service is not liable under this section merely for publishing content supplied by another information content provider. Enacted as chapter 193 of the 2024 session laws and approved by the Governor as an emergency measure on , operative immediately, the section states that it applies fourteen days after its effective date.

What it requires

Privacy law1 instrument, 1 in force

Research summary (162 words)

Arizona has no comprehensive personal-data privacy law. The one 2026 attempt at an omnibus consumer privacy act, SB 1815, was held in committee and received no floor vote in either chamber, and does not qualify as a marquee proposal under this topic's source-quality rules.

Arizona's operative privacy statute is a security-breach notification law, A.R.S. sections 18-551 to 18-552, which requires notice to affected residents within 45 days of a breach determination and, above a 1,000-resident threshold, notice to the Attorney General, the state Department of Homeland Security, and the largest nationwide consumer reporting agencies.

Biometric data generated to authenticate access to an online account is one of nine specified data elements the statute treats as personal information for breach purposes, but the Act creates no capture-consent, retention, or destruction duty for biometric data, no data-subject rights of any kind, and no private right of action; enforcement runs exclusively through the Attorney General as an unlawful practice under the Arizona Consumer Fraud Act.

Breach notification

Arizona data breach notification law

A.R.S. secs. 18-551 to 18-552official Arizona Revised Statutes text, Arizona State Legislature website

In force. Binds public and private bodies.

What this law does

Arizona's breach-notification statute requires a person that conducts business in the state and owns or licenses unencrypted and unredacted computerized personal information of an Arizona resident to notify the affected individuals within 45 days after determining that a security system breach occurred.

The duty runs to any 'person' that conducts business in the state, a term A.R.S. sec. 18-551(6) defines to include a government or governmental subdivision or agency alongside a natural person or business entity, except the department of public safety, a county sheriff's department, a municipal police department, a prosecution agency and a court, so the duty is not private-sector-only.

If the breach affects more than 1,000 individuals, the person must also notify the three largest nationwide consumer reporting agencies, the Arizona Attorney General, and the director of the Arizona Department of Homeland Security. Notice may be delayed for an active law enforcement investigation, and no notice is required at all if a reasonable investigation determines there is no substantial risk of economic loss. Gramm-Leach-Bliley Act (GLBA)- and Health Insurance Portability and Accountability Act (HIPAA)-regulated entities are exempt.

The statute creates no lawful-basis, purpose-limitation, or data-subject-rights framework for ordinary processing; it governs breach response only. The provisions this entry describes came into force on different days.

What it requires

Scraping law3 instruments, 3 in force

Research summary (206 words)

Arizona's computer-crime scheme, A.R.S. §§ 13-2316 to 13-2316.02, departs from a narrow malicious-intent-only test in the opposite direction from a peer state such as Virginia: alongside intent-based paragraphs for fraud, damage, or disruption, section 13-2316(A)(8) separately criminalizes knowingly accessing a computer, computer system, network, software, program, or data without authority or in excess of authorization, with no further intent element required, making bare unauthorized access a class 6 felony standing on its own.

Nothing in the statute's text carves out ordinary, non-disruptive automated access to a publicly available page. Two companion sections reach trafficking in access devices (credentials) and disclosing a specific system's own confidential security information. Arizona has no comprehensive consumer privacy statute reaching scraped public personal data at the state level; its only enacted privacy measure is a security-breach notification law, covered under the privacy topic, not restated here.

Terms-of-service enforceability rests on ordinary Arizona contract law, with no statutory modification located. Copyright, text-and-data-mining, database rights, unfair competition, and robots.txt's legal weight raise only the federal and common-law questions the national document already covers; Arizona adds no state-specific statute on any of them.

No reported Arizona case applying section 13-2316 or its companion sections to an automated web-scraping or bulk-data-collection fact pattern was located.

Computer misuse

Computer tampering (Arizona's computer-misuse statute)

A.R.S. § 13-2316official Arizona Revised Statutes text, Arizona State Legislature website

In force. Binds public and private bodies.

What this law does

Subsection A makes it computer tampering for a person, acting without authority or in excess of authorization of use, to do any of eight listed things: paragraphs 1 through 5 require an added mental state such as intent to defraud, knowing alteration or destruction of data, or reckless disruption, but paragraph 8 separately criminalizes knowingly accessing any computer, computer system, network, software, program, or data at all, with no further intent element beyond knowledge and lack of authority, a bare unauthorized-access offense that is a class 6 felony on its own.

Paragraph 6 criminalizes preventing a user from exiting a site or connected location in order to compel the user's device to keep communicating with or displaying the service, and a violation of that paragraph is also an unlawful practice under the Arizona Consumer Fraud Act, enforceable by the Attorney General in addition to any criminal prosecution.

Paragraph 7 reaches knowingly obtaining confidential or non-public information by accessing a computer operated by the state, a political subdivision, a health care provider, or a clinical laboratory. The codified text carries no history note, and no day on which the section came into force has been located.

What it requires

Unauthorized release of proprietary or confidential computer security information

A.R.S. § 13-2316.02official Arizona Revised Statutes text, Arizona State Legislature website

In force. Binds public and private bodies.

What this law does

Makes it unlawful to communicate, release, or publish proprietary or confidential computer security information, security-related measures, algorithms, or encryption devices relating to a particular computer, system, or network, without the authorization of that system's owner or operator.

Exemptions cover releasing a security warning or defect information that is not specific to a particular owner's or operator's system, sharing security information among a system's own authorized users, notifying an owner or operator of a perceived threat, and research, development, or testing of security measures that is likewise not specific to a particular owner's or operator's system.

A scraper or security researcher who discovers and publishes a vulnerability specific to one operator's own system, rather than a generic product defect, is not exempted merely because the underlying access was otherwise lawful. The codified text carries no history note, and no day on which the section came into force has been located.

What it requires

Unlawful possession of an access device

A.R.S. § 13-2316.01official Arizona Revised Statutes text, Arizona State Legislature website

In force. Binds public and private bodies.

What this law does

Makes it unlawful to knowingly possess, traffic in, publish, or control an access device, a credential or similar means of reaching an account or system, without the consent of its issuer, owner, or authorized user and with intent to use or distribute it; possessing five or more such devices without consent may itself support an inference of that intent.

This reaches obtaining or trading in login credentials or similar access devices used to reach data behind a login wall, rather than the act of automated collection itself. The codified text carries no history note, and no day on which the section came into force has been located.

What it requires

Cybersecurity law3 instruments, 3 in force

Research summary (719 words)

Arizona's private-sector security-topic footprint is narrow: one enacted state statute imposes a genuine disposal duty on paper records, no enacted state law sets market-entry security requirements for a connected device or software product, no state law creates a general private-sector duty to report a vulnerability or a security incident to an authority (A.R.S. 41-4282 binds state budget units and their contractors and is filed as a row of its own), and the one sector regime located, the insurer security program rule, is filed as a row of its own.

A.R.S. section 44-7601 (Title 44, Trade and Commerce, Chapter 33), in effect by at least 2005 (the earliest year for which a copy of this section could be located; the current statute text carries no enactment-date annotation of its own), requires an 'entity,' defined broadly to include a corporation, unincorporated association, sole proprietorship, partnership, trust, and a government, governmental subdivision or agency, to redact or destroy a paper record or document before discarding or disposing of it if the record or document combines an individual's first and last name, or first initial and last name, with a Social Security number, a credit, charge or debit card number, a retirement account number, a savings, checking or securities entitlement account number, or a driver license or nonoperating identification license number; the duty reaches paper records and documents only, states no parallel duty over electronic data, and exempts an entity already regulated under the Gramm-Leach-Bliley Act, Health Insurance Portability and Accountability Act (HIPAA), or the federal Fair Credit Reporting Act.

Arizona's Administrative Code, Title 20, Chapter 6, Article 21 (R20-6-2101 through R20-6-2104, adopted in 2004 under the older NAIC Standards for Safeguarding Customer Information model, distinct from and narrower than the newer NAIC Insurance Data Security Model Law), requires a 'licensee,' an insurance institution, insurance producer, or insurance support organization, to implement a comprehensive written customer information security program with administrative, technical and physical safeguards appropriate to the licensee's size and complexity; it carries no duty to report a cybersecurity event to the Insurance Commissioner or to affected consumers, unlike a jurisdiction that has adopted the newer NAIC model law, and it is filed as a row of its own.

A.R.S. section 15-1046(C)(1) requires an 'operator' of an internet website, online service, online application or mobile application used primarily for school purposes and marketed for school purposes to implement and maintain reasonable security procedures and practices appropriate to the nature of covered student information; that duty is one subsection of Arizona's comprehensive student-data-privacy statute, whose other subsections restrict targeted advertising, profiling and the sale of student data and impose deletion and privacy-policy-notice duties, so the security clause belongs to the privacy topic in the same way the General Data Protection Regulation's Article 32 and the Texas Data Privacy and Security Act's section 541.101(a)(2) do, and it is not yet researched under either topic; it is named here rather than duplicated as a security-topic row.

A.R.S. section 13-2316.02, which makes it a felony to communicate, release or publish proprietary or confidential computer security information about a particular computer, computer system or network without its owner's or operator's authorization, binds any person who releases such information about another's system rather than the system's own operator or manufacturer, so it sits with the state's computer-tampering chapter (A.R.S. section 13-2316 and its offense-by-an-intruder siblings) in the scraping topic's computer-misuse family rather than here.

No enacted Arizona statute was located that sets security requirements a connected device or software product must meet before or after it reaches the market, comparable to California's or Oregon's connected-device statutes or the Cyber Resilience Act, or that creates a general private-sector duty to report an exploited vulnerability or a security incident to a state authority; both are researched absences rather than gaps in coverage.

A.R.S. section 44-7601 is enforced by a county attorney in the county where records were wrongfully discarded or disposed, or by the Attorney General, with a civil penalty per violation arising from one incident that rises with each violation (up to $500 for a first violation, $1,000 for a second, and $5,000 for a third or subsequent violation) and no private right of action; no published enforcement record for it is confirmed in the primary text consulted here.

Arizona's breach-notification duty, A.R.S. section 18-552, is already this jurisdiction's privacy row rather than repeated here.

Sector security regimes

Customer information security program of an insurance licensee

Ariz. Admin. Code R20-6-2102 and R20-6-2103Arizona Administrative Code

archived copyRead from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived 2024. Publisher's page: https://apps.azsos.gov/public_services/Title_20/20-06.pdf

In force since . Binds private bodies.

What this law does

A licensee must implement a comprehensive written customer information security program that includes administrative, technical, and physical safeguards for the protection of customer information. The safeguards must be appropriate to the size and complexity of the licensee and the nature and scope of its activities.

The program must be designed to ensure the security and confidentiality of customer information, protect against anticipated threats or hazards to its security or integrity, and protect against unauthorized access to or use of it. A licensee is an insurance institution, insurance producer, or insurance support organization.

Customer information is nonpublic personal information and privileged information about a customer, in paper, electronic or other form, maintained by or on behalf of an insurance institution, insurance producer, or insurance support organization. Section R20-6-2104 lists non-exclusive illustrations of how a licensee may implement those requirements. Article 21 was made by final rulemaking effective .

What it requires

Security baseline statutes

Discarding and disposing of records containing personal identifying information

A.R.S. sec. 44-7601Official statute text, Arizona Revised Statutes, Arizona State Legislature

In force since . Binds public and private bodies.

What this law does

An 'entity' may not knowingly discard or dispose of a paper record or document that combines an individual's first and last name, or first initial and last name, with a Social Security number, a credit, charge or debit card number, a retirement account number, a savings, checking or securities entitlement account number, or a driver license or nonoperating identification license number, without first redacting that information or destroying the record or document.

'Entity' is defined broadly to include a corporation, unincorporated association, sole proprietorship, partnership, trust, or a government, governmental subdivision or agency. The duty applies to paper records and documents only. It does not reach an entity already regulated under the Gramm-Leach-Bliley Act, Health Insurance Portability and Accountability Act (HIPAA), or the federal Fair Credit Reporting Act. An entity that maintains and follows its own consistent disposal procedures is deemed compliant.

A county attorney or the Attorney General may enforce the section, and a civil penalty applies per violation arising out of one incident, rising from up to $500 for a first violation to up to $5,000 for a third or subsequent violation.

What it requires

Vulnerability and incident reporting

Security incident reporting by state budget units and their contractors to the statewide information security and privacy office

A.R.S. sec. 41-4282Official text of Arizona Revised Statutes section 41-4282, Arizona Legislature

In force since . Binds public and private bodies.

What this law does

Each budget unit and its contractors must identify and report security incidents to the statewide information security and privacy office immediately on discovery and deploy mitigation strategies as directed. The statewide information security and privacy office is established in the Arizona department of homeland security.

The office may temporarily suspend operation of information infrastructure to isolate the source of, or stop the spread of, an information security system breach or other similar incident. A budget unit and the department of administration, as applicable, must comply with directives to temporarily discontinue or suspend operations of information infrastructure.

The statewide office is to establish a state security operations center for central detection, reporting and response efforts for security incidents and breaches across the state. In chapter 1 of title 18, a budget unit means a department, commission, board, institution or other agency of the state receiving, expending or disbursing state funds or incurring obligations of the state. Section 41-4282 was added by Laws 2022, chapter 50 (Senate Bill 1598).

Laws 2022, chapter 50 was approved by the Governor on . The Arizona Legislature gives as the general effective date for laws of the 2022 Second Regular Session.

What it requires

Age gating law1 instrument, 1 in force

Research summary (39 words)

Arizona requires commercial websites and apps where more than one third of content is sexual material harmful to minors to verify that users are 18 or older, effective September 2025, after Governor Hobbs vetoed a similar bill in 2024.

Adult content age verification (AV)

HB2112, internet pornography, minors, age verification

Ariz. Rev. Stat. Title 18, Chapter 7 (§ 18-701 et seq.)official Arizona Revised Statutes text (A.R.S. § 18-701), Arizona Legislature

In force since . Binds private bodies.

What this law does

Requires a commercial entity that knowingly publishes sexual material harmful to minors on a website whose share of such material meets the applicability criteria, to use a reasonable age verification method, such as government issued identification or transactional data, to confirm a visitor is 18 or older, without retaining identifying information.

What it requires

Where nothing was found1 area of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

Reuse law

Arizona has no press-publisher neighbouring right and no mandatory platform-to-publisher bargaining code. No Arizona bill comparable to California's since-failed Journalism Preservation Act was located, and no reported Arizona case recognizes a hot-news misappropriation doctrine or otherwise addresses whether a hyperlink, or a framed or inline display, is a communication to the public.

Copyright over news content published in Arizona, including the copyrightability of headlines and snippets, the availability of a fair-use defense, and any text-and-data-mining exception, arises solely under the federal Copyright Act, already covered in the national document; Arizona has enacted no state intellectual-property statute reaching news aggregation and no machine-readable text-and-data-mining opt-out of its own.

As of .

Case law

  • No current case law for Arizona AI law
  • No current case law for Arizona privacy law
  • No current case law for Arizona scraping law
  • No current case law for Arizona cybersecurity law
  • No current case law for Arizona communications law
  • No current case law for Arizona content moderation law
  • No current case law for Arizona product and AI liability law
  • No current case law for Arizona digital accessibility law
  • No current case law for Arizona age gating law
  • No current case law for Arizona reuse law

Reporting clocks that run here18 instruments

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Arizona comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

1 hour
Incident notificationsecurity law
4 hours
Incident notificationsecurity law
8 hours
Incident notificationsecurity law
36 hours
72 hours
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
4 business days
Incident notificationsecurity law
5 business days
Incident notificationsecurity law
7 business days
Breach notificationprivacy law
30 days
Incident notificationsecurity law
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
45 days
Breach notificationprivacy law
60 days
Breach notificationprivacy law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Arizona

45 days

Arizona data breach notification law

A.R.S. secs. 18-551 to 18-552privacy law, in force

The sentences the clocks are read from

Notify each affected Arizona resident of a breach of system security involving their personal information within 45 days after determining the breach occurred.

Notify the Arizona Attorney General and the director of the Arizona Department of Homeland Security, in writing, within 45 days after determining the breach occurred, and the three largest nationwide consumer reporting agencies, if the breach requires notification of more than 1,000 individuals (A.R.S. 18-552(B)).

Where a law enforcement agency has delayed the notifications, make them within 45 days after the agency tells you that they no longer compromise its investigation (A.R.S. 18-552(D)).

The law of the United States, which applies in Arizona

1 hour4 hours8 hours24 hours

NRC cyber security event notifications by nuclear power plant licensees

NRC cyber security event notifications, 10 CFR 73.77security law, in force since

The sentences the clocks are read from

Notify the NRC Headquarters Operations Center via the Emergency Notification System within one hour after discovery of a cyberattack that adversely impacted safety-related or important-to-safety functions, security functions, or emergency preparedness functions (including offsite communications), or that compromised support systems and equipment resulting in adverse impacts to those functions.

Also notify within one hour after discovery of a cyberattack that adversely impacted the safety, security, and emergency preparedness functions performed by digital assets described in 10 CFR 73.77(a)(1)(ii).

Notify the NRC Headquarters Operations Center within four hours after discovery of a cyberattack that could have caused such an adverse impact, after discovery of a suspected or actual cyberattack initiated by personnel with physical or electronic access to the systems in scope, or after notifying a local, State, or other Federal agency of an event related to your cyber security program that does not otherwise require notification.

Notify the NRC Headquarters Operations Center within eight hours after receipt or collection of information regarding observed behavior, activities, or statements that may indicate intelligence gathering or pre-operational planning related to a cyberattack against the systems in scope.

Use the site corrective action program to record vulnerabilities, weaknesses, failures and deficiencies in your cyber security program, and the notifications you make, within twenty-four hours of their discovery.

24 hours72 hours

Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA)

6 U.S.C. 681-681g (CIRCIA)security law, enacted, not yet in force

The sentences the clocks are read from

Once the final rule takes effect, report a covered cyber incident to the Agency not later than 72 hours after your organization reasonably believes that the covered cyber incident has occurred.

Once the final rule takes effect, report a ransom payment to the Agency not later than 24 hours after your organization makes the payment, even where the underlying ransomware attack is not itself a covered cyber incident.

Once the final rule takes effect, promptly submit an update to a previously submitted covered cyber incident report whenever substantial new or different information becomes available or a ransom payment is later made, continuing until your organization notifies the Agency that the incident has concluded and been fully mitigated and resolved, and preserve data relevant to the incident or payment under the procedures the final rule establishes.

24 hours5 business days30 days

SEC Regulation SCI: notification of SCI events to the Commission and to members

SEC Regulation SCI SCI event notices, 17 CFR 242.1002(b) and (c)security law, in force since

The sentences the clocks are read from

Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, begin appropriate corrective action and notify the Commission of the SCI event immediately.

Within 24 hours of that conclusion, submit a written notification to the Commission, made on a good faith, best efforts basis, that describes the SCI event and the systems affected and, to the extent available, your assessment of the market participants potentially affected, the potential impact on the market, and the steps you have taken, are taking or plan to take.

If the SCI event is resolved and the investigation closed within 30 calendar days, submit a final written notification within five business days after resolution. If not, submit an interim written notification within 30 calendar days after the event, and a final one within five business days after resolution and closure.

36 hours

Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers

12 CFR Part 53 (OCC); 12 CFR Part 225, Subpart N (Federal Reserve Board); 12 CFR Part 304, Subpart C (FDIC)security law, in force since

The sentences the clocks are read from

If your organization is a banking organization, notify your primary federal banking regulator, the OCC, the Federal Reserve Board, or the FDIC, whichever supervises it, about a notification incident, as soon as possible and no later than 36 hours after your organization determines that a notification incident has occurred.

A notification incident is the subset of computer-security incidents that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, your ability to serve customers, a business line, or an operation whose failure would threaten the financial stability of the United States, so a computer-security incident that falls short of that threshold does not by itself start this clock.

If your organization is a bank service provider, notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible after your organization determines that it has experienced a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that banking organization for a period of four hours or more.

This duty carries a standard, as soon as possible, rather than a fixed number of hours to notify by, and that disruption threshold is what engages the duty rather than a period to notify within.

72 hours30 days

Artificial Intelligence Risk Management and Security Act of 2026

S. 5576, 119th Congressfrontier-model AI law, proposed

The sentence the clocks are read from

If you are a developer or provider of a frontier AI model, or an operator of critical infrastructure that uses an AI model to manage industrial control systems or other operational technologies, report any confirmed AI safety incident or AI security incident within 30 days of confirmation, and within 72 hours if the incident poses an imminent threat to national security, critical infrastructure or public safety.

72 hours

NCUA Cyber Incident Notification Requirements for Federally Insured Credit Unions

NCUA Cyber Incident Notification Requirements, 12 CFR 748.1(c)security law, in force since

The sentences the clocks are read from

If your organization is a federally insured credit union, notify the NCUA-designated point of contact of a reportable cyber incident by email, telephone, or another method the NCUA prescribes, so that the NCUA receives the notification as soon as possible and no later than 72 hours after your organization reasonably believes it has experienced a reportable cyber incident.

Where the reportable cyber incident is a disruption of business operations or unauthorized access to sensitive data facilitated through, or caused by, a compromise of a credit union service organization, cloud service provider, or other third-party data hosting provider, or by a supply chain compromise, the NCUA must receive the notification within 72 hours of your organization being notified by the third party if that is sooner.

72 hours30 days

Regulation S-P: incident response program and customer breach notice

17 CFR 248.30(a)(3) to (a)(5)privacy law, in force since

The sentences the clocks are read from

Send the notice as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred, delaying it only for the period the United States Attorney General specifies where the Attorney General determines that notice poses a substantial risk to national security or public safety (17 CFR 248.30(a)(4)(iii)).

Maintain written policies and procedures reasonably designed to require oversight, including through due diligence and monitoring, of service providers, including that a service provider notify you as soon as possible, and no later than 72 hours, after becoming aware of a breach in security resulting in unauthorized access to a customer information system it maintains (17 CFR 248.30(a)(5)(i)).

72 hours

SEC Regulation S-P: service provider oversight and 72-hour breach notice to the covered institution

SEC Regulation S-P service provider oversight and notice, 17 CFR 248.30(a)(5)security law, in force

The sentence the clocks are read from

Make those policies and procedures reasonably designed to ensure that each service provider takes appropriate measures to protect against unauthorized access to or use of customer information, and to notify you as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system the service provider maintains.

4 business days

SEC Cybersecurity Risk Management, Governance, and Incident Disclosure (Regulation S-K Item 106; Form 8-K Item 1.05)

17 CFR 229.106; 17 CFR 249.308 (Form 8-K Item 1.05)security law, in force since

The sentences the clocks are read from

If your organization is an Securities and Exchange Commission (SEC) reporting company, determine, without unreasonable delay after you discover a cybersecurity incident, whether the incident is material, and if it is, file a Form 8-K under Item 1.05 within four business days after you make that determination.

If the information called for in Item 1.05 is not determined or is unavailable when you file, state that in the filing and file an amendment to the Form 8-K within four business days after you determine it or it becomes available.

7 business days30 days

FCC CPNI breach notification rule

47 CFR 64.2011privacy law, in force

The sentences the clocks are read from

After you reasonably determine that a breach of your customers' CPNI has occurred, electronically notify the United States Secret Service and the Federal Bureau of Investigation through the central reporting facility as soon as practicable, and in no event later than seven business days (47 CFR 64.2011(b)).

Do not notify customers or disclose the breach where the relevant investigating agency directs you in writing not to, for an initial period of up to 30 days that the agency may extend (47 CFR 64.2011(b)(3)).

60 days

FTC Health Breach Notification Rule

16 CFR Part 318privacy law, in force since

The sentences the clocks are read from

If you are a vendor of personal health records (an entity that offers or maintains an electronic record of health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual) or a PHR related entity, notify each affected individual who is a citizen or resident of the United States, in plain language and without unreasonable delay, no later than 60 calendar days after you discover a breach of security of unsecured PHR identifiable health information.

Notify prominent media outlets serving a State or jurisdiction, without unreasonable delay and in no case later than 60 calendar days after you discover the breach, when the unsecured PHR identifiable health information of 500 or more of its residents is, or is reasonably believed to have been, acquired during the breach.

If you are a third party service provider, notify the official designated in a written contract by the vendor of personal health records or PHR related entity you serve (or else a senior official of that vendor or entity), without unreasonable delay and in no case later than 60 calendar days after you discover the breach; identify each customer of that vendor or entity whose unsecured PHR identifiable health information has been, or is reasonably believed to have been, acquired during the breach; and obtain acknowledgment that the notice was received.

60 days

HIPAA Breach Notification Rule

45 CFR Part 164, Subpart D (Sections 164.400-164.414)privacy law, in force since

The sentences the clocks are read from

Notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information.

For a breach of unsecured protected health information involving more than 500 residents of a State or jurisdiction, notify prominent media outlets serving that State or jurisdiction without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

If you are a business associate, notify the covered entity of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

promptly

CFTC system safeguards: prompt notice to Commission staff of cyber security incidents and targeted threats

CFTC system safeguards notices, 17 CFR 39.18(g), 38.1051(e) and 37.1401(e)security law, in force since

The sentences the clocks are read from

If your organization is a derivatives clearing organization, notify staff of the Division of Clearing and Risk promptly of any hardware or software malfunction, security incident, or targeted threat that materially impairs, or creates a significant likelihood of material impairment of, automated system operation, reliability, security, or capacity, and of any activation of your business continuity and disaster recovery plan.

If your organization is a designated contract market, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and significant systems malfunctions and activations of your business continuity-disaster recovery plan.

If your organization is a swap execution facility, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and material system malfunctions and activations of your business continuity-disaster recovery plan.

immediately

Coast Guard Cybersecurity in the Marine Transportation System: reportable cyber incidents

Coast Guard reportable cyber incident reporting, 33 CFR 101.620(b)(7) and 101.615security law, in force since

The sentence the clocks are read from

Evidence of sabotage, subversive activity, or an actual or threatened cyber incident involving or endangering any vessel, harbor, port, or waterfront facility must be reported immediately to the Federal Bureau of Investigation, the Cybersecurity and Infrastructure Security Agency (for any cyber incident), and the Captain of the Port, or to their respective representatives.

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.