Law / United States / North Dakota

North Dakota

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

  1. AI law 3
  2. Privacy law 1
  3. Scraping law 1
  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 2
  10. Reuse law

in forcenot yet in forceblocked by a courtproposedno longer in force

AI law3 instruments, 3 in force

Research summary (239 words)

North Dakota has no comprehensive AI-transparency, AI-risk, or AI-governance statute. Three 2025 enactments narrowly regulate specific uses of artificial intelligence by any person: House Bill 1167 created N.D. Cent. Code § 16.1-10-04.2, requiring a disclaimer on AI-generated political content that visually or audibly impersonates a human; House Bill 1351 amended N.D. Cent.

Code §§ 12.1-27.1-01 and 12.1-27.1-03.3 to add computer-generated images to the state's non-consensual intimate image ban, reaching AI-generated and altered deepfakes of an identifiable person; and House Bill 1429 amended the harassment and stalking statutes, N.D. Cent.

Code §§ 12.1-17-07 and 12.1-17-07.1, to define 'robot' as an artificial object or system that senses, processes, and acts using technology, including artificial intelligence and a remotely piloted aircraft, and to prohibit using one to engage in offensive conduct with no legitimate purpose or to track a person's movements as a form of stalking.

Senate Bill 2280, a 2025 health-insurance prior-authorization reform requiring adverse coverage determinations to be made by a licensed physician or pharmacist, contains no reference to artificial intelligence, an algorithm, or automated decision-making anywhere in its enacted text, so it adds no AI-specific duty despite sometimes being described as a prohibition on AI-only coverage denials. No law restricting a state government agency's own use of AI has been identified.

The legislative assembly maintains an interim Artificial Intelligence and Data Center Committee for the 2025-26 interim, evidencing active legislative attention to the subject beyond the enacted duties above.

AI prohibited practices

House Bill 1351 (2025), sexually expressive images including AI-generated or altered deepfakes

N.D. Cent. Code § 12.1-27.1-03.3official North Dakota Century Code, chapter 12.1-27.1 (ndlegis.gov)

In force since . Binds public and private bodies.

What this law does

House Bill 1351 amended the definition of 'sexually expressive image' at N.D. Cent. Code § 12.1-27.1-01(13) to cover a real, altered, or computer-generated photograph or visual representation exhibiting a nude or partially denuded human figure or sexual conduct, reaching an AI-generated or AI-altered deepfake alongside a real photograph.

Under the operative prohibition, § 12.1-27.1-03.3, a person is guilty of a class A misdemeanor for surreptitiously creating or willfully possessing such an image of an identifiable individual without that individual's written consent, or for distributing or publishing one with intent to cause emotional harm or humiliation, or after being told by the depicted individual or their parent or guardian that they do not consent; a person is guilty of a class B misdemeanor for acquiring and knowingly distributing such an image created without the subject's consent.

A depicted individual identifiable in the image and harmed by a violation committed for sexual arousal, gratification, humiliation, degradation, or monetary or commercial gain has a civil cause of action for the greater of actual and emotional-distress damages or statutory damages capped at ten thousand dollars per defendant, plus any monetary gain the defendant made, exemplary damages, and attorney fees.

House Bill 1351 passed both chambers with only one dissenting vote, was signed by the governor on , was filed with the secretary of state , and carried no emergency clause, so it took effect under North Dakota's default effective-date rule.

What it requires

House Bill 1429 (2025), harassment and stalking with a robot

N.D. Cent. Code §§ 12.1-17-07(2)(f), 12.1-17-07.1official North Dakota Century Code, chapter 12.1-17 (ndlegis.gov)

In force since . Binds public and private bodies.

What this law does

House Bill 1429 amended North Dakota's harassment and stalking statutes to define 'robot' as an artificial object or system that senses, processes, and acts using technology, including the associated elements, communication links, and artificial intelligence, a definition that also reaches a remotely piloted aircraft. Under N.D. Cent. Code § 12.1-17-07(2)(f), a person is guilty of harassment, a class B misdemeanor, for using a robot to engage in offensive conduct with no legitimate purpose.

Under N.D. Cent. Code § 12.1-17-07.1, unauthorized tracking of a person's movements or location through a robot, or a course of conduct that includes an act conducted with a robot in the person's direct control, can constitute stalking, a class A misdemeanor, or a class C felony where the person has a qualifying prior conviction or violates a protective order with notice.

House Bill 1429 passed both chambers without a dissenting vote, was signed by the governor , and was filed with the secretary of state , without an emergency clause. The North Dakota Legislative Council's own report on the effective dates of 2025 legislation states that House Bill 1429 took effect .

What it requires

AI transparency

House Bill 1167 (2025), AI-generated political content disclosure

N.D. Cent. Code § 16.1-10-04.2official North Dakota Century Code, chapter 16.1-10 (ndlegis.gov)

In force since . Binds public and private bodies.

What this law does

Any action taken for a political purpose, including communication or advertising in support of or opposition to a candidate, political committee, or political party, or for promoting passage or defeat of an initiated or referred measure, that contains images, graphics, video, audio, text, or other digital content created in whole or in part with artificial intelligence to visually or audibly impersonate a human, must prominently state the disclaimer 'THIS CONTENT GENERATED BY ARTIFICIAL INTELLIGENCE.'

The duty does not apply to content that solely uses artificial intelligence for text generation, grammar correction, spelling checks, stylistic editing, or otherwise enhancing existing content without creating a new impersonation of a human's likeness or voice.

Artificial intelligence is defined as a machine-based system capable of creating images, graphics, video, audio, text, or other digital content based on human-defined objectives or data patterns, excluding systems explicitly programmed only to assist with grammar, spelling, or word suggestions.

House Bill 1167 passed both chambers without a dissenting vote and was filed with the secretary of state , without an emergency clause, so it took effect under North Dakota's default effective-date rule for legislation filed before that date.

What it requires

Privacy law1 instrument, 1 in force

Research summary (222 words)

North Dakota has no comprehensive consumer personal-data-protection statute and takes a purely sectoral approach. Its breach notification duty, N.D. Cent.

Code ch. 51-30, requires notice to affected residents without unreasonable delay and, for a breach exceeding 250 individuals, to the Attorney General, but its ten-item personal information definition (a Social Security number, a driver's license or identification card number, a financial account number, a date of birth, a mother's maiden name, medical or health insurance information, an employer-assigned identification number, or a digitized signature) does not include biometric data at all, a confirmed absence rather than an unread gap.

The only North Dakota statute using the term biometric data is a criminal identity-theft prohibition, N.D. Cent. Code Sec. 12.1-23-11, which criminalizes a thief's unauthorized use of it and imposes no duty on a private-sector data handler.

Enforcement of the breach statute runs to the Attorney General under chapter 51-15, North Dakota's unlawful-practices chapter, because a violation of chapter 51-30 is deemed a violation of chapter 51-15; whether that deeming clause also opens chapter 51-15's own private civil-action provision, which arms a claim against a person who acquired moneys or property by means of the unlawful practice, to an individual harmed by a bare notification failure is genuinely unresolved on the text, and no North Dakota case law construing the combination was found.

Breach notification

Notice of Security Breach for Personal Information

N.D. Cent. Code ch. 51-30official North Dakota statute text, North Dakota Century Code chapter 51-30

In force. Binds public and private bodies.

What this law does

Any person that owns or licenses computerized data including personal information must disclose a breach of the security system to any affected North Dakota resident, and separately to the Attorney General for a breach exceeding 250 individuals, in the most expedient time possible and without unreasonable delay; the chapter sets no numeric consumer-notification deadline and does not itself define or limit person to a private actor.

Personal information is a name combined with a Social Security number, a driver's or nondriver identification card number, a financial account number, a date of birth, a mother's maiden name, medical or health insurance information, an employer-assigned identification number, or a digitized signature, and excludes publicly available government-records information; biometric data is not among the ten enumerated categories, and this chapter does not reach it at all.

Enforcement runs to the Attorney General, who may use all the powers and remedies of chapter 51-15, North Dakota's unlawful-practices chapter, because a violation of this chapter is deemed a violation of chapter 51-15.

Whether that deeming clause makes chapter 51-15's own private-claim provision, Sec. 51-15-09, available to an individual for a bare notification failure is unresolved: that provision arms a claim specifically against a person who acquired any moneys or property by means of the unlawful practice, language that fits a fraud that took money more naturally than a business's mere failure to notify of someone else's breach, and no North Dakota case law construing this combination was found; secondary characterizations of chapter 51-30 disagree with each other on this point, and that disagreement is not resolved here.

The provisions this entry describes came into force on different days.

What it requires

Scraping law1 instrument, 1 in force

Research summary (129 words)

North Dakota's computer misuse statute diverges from a bare Computer Fraud and Abuse Act (CFAA)-style authorization test by splitting the offense in two: a felony 'computer fraud' requiring intent to defraud or deceive, and a separate, broader misdemeanor 'computer crime' that reaches intentional access in excess of authorization or without authorization at all, with no fraud, malice, or deception element required, plus a private civil right of action for the affected computer's owner or lessee.

This is closer to a bare authorization test than Virginia's malicious-intent-or-deceptive-means standard, and no North Dakota case law applying it to an automated public-page collection fact pattern was found. Copyright, text-and-data-mining, database rights, and terms-of-service enforceability are federal and common-law only; North Dakota adds nothing beyond that framework, and robots.txt carries no independent legal weight under North Dakota law.

Computer misuse

Computer fraud and computer crime

N.D. Cent. Code § 12.1-06.1-08official statute text, North Dakota Century Code chapter 12.1-06.1 (ndlegis.gov)

In force. Binds public and private bodies.

What this law does

A person commits computer fraud, a class C felony, by gaining or attempting to gain access to, altering, damaging, modifying, copying, disclosing, taking possession of, or destroying a computer, computer system, or computer network, without authorization, with the intent to defraud, deceive, prevent authorized use of, or control property or services by false or fraudulent pretenses, representations, or promises.

A person separately commits computer crime, a class A misdemeanor, by intentionally and either in excess of authorization given or without authorization gaining or attempting to gain access to, altering, damaging, modifying, copying, disclosing, taking possession of, introducing a computer contaminant into, destroying, or preventing the authorized use of a computer, computer system, computer network, or any software, program, or data within one; this misdemeanor tier carries no fraud, malice, or deception element, so intentional access in excess of or without authorization is itself enough, closer to a bare authorization test than the malicious-intent-or-deceptive-means standard some neighboring states use.

Subsection 3 gives the owner or lessee of the affected computer, system, or network a civil action for damages, restitution, and attorney's fees. The current codification of this section traces to House Bill 1038, chapter 164 of the 1987 North Dakota Session Laws, which amended and reenacted the section and carried no emergency clause.

The Century Code carries no history note stating the day this section came into force, and no record of the enacting session's general effective date has been located.

What it requires

Cybersecurity law3 instruments, 3 in force

Research summary (566 words)

North Dakota has not enacted a standalone product-security statute or a general reasonable-security baseline statute reaching a private-sector operator; its security duties are the insurance data security chapter's program and notice duties and the incident disclosure duty of chapter 54-59.1 on executive branch agencies and political subdivisions, each filed as a row of its own. N.D. Cent.

Code ch. 51-30, Notice of Security Breach for Personal Information, requires disclosure of a breach to affected residents and, above 250 individuals, to the Attorney General, but its seven sections are entirely about the notice duty itself and impose no safeguards, information-security-program, or reasonable-security obligation; it is North Dakota's privacy-topic breach-notification row rather than a security one. N.D. Cent.

Code Sec. 12.1-06.1-08, the computer fraud and computer crime section of the racketeering chapter, is an offense against a computer, computer system, or computer network committed by an intruder gaining unauthorized or excess-of-authorization access, so it binds the person doing the accessing and belongs to the scraping topic's computer-misuse family rather than this one. North Dakota's Insurance Data Security Law, N.D. Cent.

Code ch. 26.1-02.2 (amended by S.L. 2025, ch. 280), is a genuine security-shaped duty: a licensee must develop, implement, and maintain a written information security program, investigate a cybersecurity event, and notify the insurance commissioner within three business days of a qualifying event, with a further consumer-notice cross-reference to chapter 51-30. It binds only an insurance "licensee," and its rows are flagged for an insurer. N.D. Cent.

Code ch. 54-59, Information Technology Department, imposes cybersecurity-strategy duties that run only to state agencies, the university system, counties, cities, school districts, and other political subdivisions, with no provision reaching a private business. N.D. Cent.

Code Sec. 57-39.2-04.17's "enhanced security" language (video surveillance, pass codes, key cards, or biometric scans) is one physical-building eligibility criterion for a qualified data center's sales and use tax exemption, not a legal duty on an operator. N.D. Cent.

Code ch. 51-22, Data Processing Information Confidentiality, prohibits a business entity that charges a fee for data processing services from disclosing a customer's record without written consent; that duty attaches to the data itself rather than to a product's or system's security posture, so it is privacy-shaped and not filed here. Title 6, Banks and Banking, names no chapter titled cybersecurity or information security, and its customer-information chapter, N.D. Cent.

Code ch. 6-08.1, is a nondisclosure and government-access regime with no safeguards or information-security-program duty; whether the remainder of Title 6 or the Department of Financial Institutions' own administrative rules set a banking-sector safeguards duty comparable to the federal Safeguards Rule is not confirmed either way. Whether the 69th Legislative Assembly's September 2026 special session has introduced a security-related bill is not addressed here.

North Dakota's Insurance Data Security Law requires a licensee to develop, implement, and maintain a comprehensive written information security program based on its risk assessment, under chapter 26.1-02.2 of the North Dakota Century Code. North Dakota's Insurance Data Security Law requires a licensee to notify the insurance commissioner as promptly as possible, and no later than three business days from a determination that a cybersecurity event has occurred, where its conditions are met.

An executive branch state agency or a political subdivision of North Dakota must disclose an identified or suspected cybersecurity incident to the information technology department in the most expedient time possible, under chapter 54-59.1 of the North Dakota Century Code.

Sector security regimes

Insurance Data Security Law, information security program

N.D. Cent. Code § 26.1-02.2-03Official text of North Dakota Century Code chapter 26.1-02.2 and section 26.1-01-03.3

In force since . Binds private bodies.

What this law does

Each licensee must develop, implement, and maintain a comprehensive written information security program based on its risk assessment that contains administrative, technical, and physical safeguards for the protection of nonpublic information and the licensee's information system.

A licensee is any person licensed, authorized to operate, registered, or required to be licensed, authorized, or registered under the insurance laws of North Dakota, other than a purchasing group or a risk retention group chartered and licensed in another state or a licensee acting as an assuming insurer domiciled in another state or jurisdiction.

A licensee must establish a written incident response plan designed to promptly respond to, and recover from, any cybersecurity event that compromises the confidentiality, integrity, or availability of nonpublic information in its possession. An insurer domiciled in North Dakota must submit annually to the commissioner a written statement, by April fifteenth, certifying that the insurer complies with the information security program section.

A licensee with less than five million dollars in gross revenue or less than ten million dollars in year-end assets is exempt from subsections 2 through 10 of the information security program section. A licensee that is subject to, governed by, and compliant with the federal health privacy, security, and breach notification rules and maintains nonpublic information in the same manner as protected health information is deemed to comply with the information security program section.

A licensee that violates the chapter may be penalized in accordance with section 26.1-01-03.3 of the North Dakota Century Code. A person who violates title 26.1 is subject, after hearing by the commissioner, to payment of an administrative monetary fine of up to ten thousand dollars for each violation, unless otherwise provided by law.

Under the original Act, a licensee had to implement subsections 1, 2, 3, 4, 5, 8, and 9 of the information security program section no later than , and subsections 6 and 7 no later than . Chapter 280 of the Session Laws of 2025 repealed the section that set those implementation dates.

What it requires

Vulnerability and incident reporting

Cybersecurity Incident Reporting Requirements, disclosure of a cybersecurity incident to the Information Technology Department

N.D. Cent. Code ch. 54-59.1Official text of North Dakota Century Code chapter 54-59.1, North Dakota Legislative Branch, and of House Bill 1314 (2021)

In force. Binds government bodies.

What this law does

An entity must disclose to the information technology department an identified or suspected cybersecurity incident that affects the confidentiality, integrity, or availability of information systems, data, or services. The disclosure must be made in the most expedient time possible and without unreasonable delay. An entity is an executive branch state agency or a political subdivision within the state.

Until a cybersecurity incident is resolved, an entity must disclose clarifying details to the department, including the number of potentially exposed records, the type of records, its mitigation and remediation efforts, and the expected impact of the incident. The legislative and judicial branches may disclose cybersecurity incidents to the department but are not required to.

The department must establish and make known the methods an entity must use to securely disclose cybersecurity incidents to the department. The department must report all disclosed cybersecurity incidents to the legislative management, including the status of each incident and any response or remediation.

What it requires

Insurance Data Security Law, investigation and notification of a cybersecurity event

N.D. Cent. Code §§ 26.1-02.2-04, 26.1-02.2-05Official text of North Dakota Century Code chapter 26.1-02.2 and section 26.1-01-03.3

In force. Binds private bodies.

What this law does

A licensee that learns a cybersecurity event has or may have occurred must conduct a prompt investigation, or have an outside vendor or service provider designated to act on its behalf conduct one. A licensee must notify the commissioner as promptly as possible, but no later than three business days from a determination that a cybersecurity event has occurred, if either of the two sets of conditions in the notification section is met.

The first set of conditions is met where North Dakota is the licensee's state of domicile, in the case of an insurer, or its home state, in the case of a producer, and the event triggers notification to a consumer residing in the state under chapter 51-30 or has a reasonable likelihood of harming any material part of the normal operations of the licensee.

The second set of conditions is met where the licensee reasonably believes the nonpublic information involved is of two hundred fifty or more consumers residing in the state and the event requires notice to a government body or supervisory body under state or federal law or has a reasonable likelihood of materially harming a consumer or any part of the licensee's normal operations.

The licensee must provide the notice in electronic form as directed by the commissioner and must update and supplement the initial and any subsequent notifications regarding material changes. An assuming insurer must notify its affected ceding insurers and the commissioner of its state of domicile within three business days of making the determination that a cybersecurity event has occurred.

The chapter establishes the exclusive state standards applicable to licensees for data security, the investigation of a cybersecurity event, and notification to the commissioner. Senate Bill 2088 of the 69th Legislative Assembly amended and reenacted the notification section. A licensee that violates the chapter may be penalized in accordance with section 26.1-01-03.3 of the North Dakota Century Code.

A person who violates title 26.1 is subject, after hearing by the commissioner, to payment of an administrative monetary fine of up to ten thousand dollars for each violation, unless otherwise provided by law.

What it requires

Age gating law2 instruments, 2 in force

Research summary (136 words)

North Dakota enacted a pair of companion adult content age verification laws in 2025, House Bill 1561 and Senate Bill 2380, both effective . Each adds a near-identical section to chapter 51-07 of the Century Code requiring commercial entities whose websites contain more than one third sexual material harmful to minors to verify that visitors are 18 or older, bars retention of identifying information, and is enforced solely through private civil suits.

SB 2380 was introduced as a device, operating system, and app store age-signal mandate, an approach the adult industry's trade group publicly supported, but that mandate was stripped before passage; the enrolled law parallels HB 1561 and expressly shields internet service providers, search engines, cloud providers, and app stores. No social media minor-access, app store, or design code law has been enacted.

Adult content age verification (AV)

HB 1561, age verification for sexual material harmful to minors

2025 H.B. 1561 (new section of N.D. Cent. Code ch. 51-07; the codified section, N.D. Cent. Code § 51-07-32, carries the text of 2025 S.B. 2380)official enrolled bill text

In force since . Binds private bodies.

What this law does

Commercial entities that knowingly publish or distribute sexual material harmful to minors on a website where more than one third of the content meets that definition must perform reasonable age verification, such as a digitized identification card or a commercial verification system using a government ID or transactional data.

A commercial entity or third party performing verification may not retain identifying information after access is granted, and enforcement is through private civil suits only.

What it requires

SB 2380, age verification for sexual material harmful to minors (companion to HB 1561)

N.D. Cent. Code § 51-07-32 (created by 2025 S.B. 2380)official enrolled bill text

In force since . Binds private bodies.

What this law does

Substantially identical to companion bill HB 1561: commercial entities that knowingly publish or distribute sexual material harmful to minors on a website where more than one third of the content meets that definition must verify visitors are 18 or older using a digitized identification card or a commercial age verification system relying on government-issued identification, a commercially available age and identity database, or transactional data, and may not retain identifying information after access is granted.

As introduced, the bill would have required device makers, operating systems, and app stores to determine user age and transmit age signals, but the enrolled law dropped that mandate entirely and instead expressly provides that internet service providers, search engines, cloud providers, and application stores are not liable solely for providing access to third-party content. Enforcement is through private civil suits only.

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

North Dakota has enacted no press-publisher neighbouring right, no mandatory platform-to-publisher bargaining code, and no text-and-data-mining opt-out statute, and no North Dakota case recognizing a hot-news misappropriation doctrine was located.

A full-text search of the North Dakota Century Code for journalism, newspaper, publisher, and news aggregation surfaced only unrelated provisions: Title 51's unlawful sales and advertising practices chapters (ch. 51-12, ch. 51-15) exempt a newspaper or broadcast publisher from liability for an advertisement it did not know was false, deceptive, or misleading, and a securities-law venue provision (Title 10) treats a newspaper's predominantly out-of-state circulation as not constituting an offer made within the state; neither bears on snippet reproduction, linking, framing, or a publisher's compensation.

Snippet reproduction, linking and framing, database rights, and any text-and-data-mining exception rest on federal copyright law alone, with no North Dakota statute or located case law adding to or diverging from that federal baseline.

As of .

Case law

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

Reporting clocks that run here19 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 North Dakota 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
3 business days
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
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 North Dakota

3 business days

Insurance Data Security Law, investigation and notification of a cybersecurity event

N.D. Cent. Code §§ 26.1-02.2-04, 26.1-02.2-05security law, in force

The sentences the clocks are read from

Notify the commissioner as promptly as possible, and no later than three business days from your determination that a cybersecurity event has occurred, where the event triggers notification to a consumer residing in North Dakota under chapter 51-30 or has a reasonable likelihood of harming any material part of your normal operations.

Notify the commissioner within the same three business days where you reasonably believe the nonpublic information involved is of two hundred fifty or more consumers residing in North Dakota and the event requires notice to any government body, self-regulatory agency, or other supervisory body under state or federal law, or has a reasonable likelihood of materially harming a consumer residing in North Dakota or any part of your normal operations.

If you are an assuming insurer, notify your affected ceding insurers and the commissioner of your state of domicile within three business days of making the determination that a cybersecurity event has occurred, or within three business days of receiving notice from your third-party service provider.

without unreasonable delay

Cybersecurity Incident Reporting Requirements, disclosure of a cybersecurity incident to the Information Technology Department

N.D. Cent. Code ch. 54-59.1security law, in force

The sentence the clocks are read from

Disclose to the information technology department an identified or suspected cybersecurity incident that affects the confidentiality, integrity, or availability of information systems, data, or services, in the most expedient time possible and without unreasonable delay.

The law of the United States, which applies in North Dakota

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.