Law / United States / Northern Mariana Islands

Northern Mariana Islands

1 of 3 named instruments researched to a stage, across one of the ten areas of law we track: 1 in force. As of .

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

in forcenot yet in forceblocked by a courtproposedno longer in force

Privacy law1 instrument, 1 in force

Research summary (126 words)

The Northern Mariana Islands has no comprehensive personal-data protection statute, no dedicated biometric-privacy law, no data-subject-rights statute, and no breach-notification law; Title 6 (Crimes and Criminal Procedure) and Title 4 (Economic Resources) were both read for one and neither carries any such provision. Federal privacy statutes, covered in the national document, apply to the Commonwealth of their own force.

The Commonwealth's general Consumer Protection Act, 4 CMC §§ 5101-5123, prohibits unfair and deceptive trade practices and is the sole territorial mechanism reaching a business's misrepresentation about its own data-handling practices, the same role the Federal Trade Commission Act's Section 5 plays at the federal level in the absence of a comprehensive statute; it is enforced by the Attorney General's Consumer Counsel and by a private plaintiff.

Enforcement supervision

CNMI Consumer Protection Act, general applicability

4 CMC §§ 5101-5123Official Commonwealth Code text, CNMI Law Revision Commission

In force since . Binds private bodies.

What this law does

The Consumer Protection Act prohibits unfair methods of competition and unfair or deceptive acts or practices in the conduct of any trade or commerce, including passing off goods or services as another's, causing a likelihood of confusion as to affiliation or sponsorship, and representing that goods or services have characteristics they do not have.

It carries no personal-data-specific provision, but its general prohibition on deceptive representations is the Commonwealth's only current mechanism against a business that misrepresents its own data collection, use, or sharing practices, the role the Federal Trade Commission Act's Section 5 plays nationally absent a comprehensive federal statute. A consumer counsel designated within the Office of the Attorney General enforces the Act, and an aggrieved consumer may also sue directly.

What it requires

Where nothing was found5 areas 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.

AI law

The Northern Mariana Islands has not enacted a statute imposing an AI-transparency or output-labeling duty: a duty to disclose that content is AI-generated, to label or watermark synthetic output, or to disclose that a user is talking to a bot. No such bill has been located in the CNMI Legislature's public-law record.

The Commonwealth's general Consumer Protection Act, 4 CMC §§ 5101-5123, could reach an undisclosed bot or AI agent that misrepresents itself as human in a commercial dealing under its general prohibition on deceptive trade practices, the same backstop role the Federal Trade Commission Act's Section 5 plays federally, and it is catalogued for that reason under the privacy topic rather than here, since the duty it states attaches to deceptive commercial conduct generally rather than to an AI system as such.

As of .

Scraping law

The Northern Mariana Islands has no computer-misuse or computer-fraud statute of its own, so unauthorized access to a computer system is a matter for the federal Computer Fraud and Abuse Act, covered in the national document, rather than any territorial offense.

Title 6 (Crimes and Criminal Procedure) criminalizes identity theft (6 CMC §§ 1721-1722) and criminal electronic impersonation (6 CMC § 3116), but both are fraud and harassment offenses tied to impersonating a real person, not a computer-access or scraping-specific doctrine, and neither creates a database right, a terms-of-service rule, or a text-and-data-mining exception.

No Commonwealth court has addressed whether a browsewrap or clickwrap terms of service is enforceable against a scraper, no statute assigns legal weight to a robots.txt directive, and copyright protection over any content on a Commonwealth website arises solely under the federal Copyright Act, also covered in the national document.

As of .

Cybersecurity law

The Northern Mariana Islands has no statute setting security requirements a software product or connected device must meet to be placed on the market, no general duty running to an authority or a computer security incident response team (CSIRT) to report an exploited vulnerability or a security incident, and no cyber-resilience regime comparable to NIS2, DORA, or a sector-specific security model law binding an essential, important, critical, or financial entity was located in the sources read.

Unlike Guam and the United States Virgin Islands, the Commonwealth also has no security-breach notification statute of any kind: an exact-phrase site search for "notification of breach" returned zero results across every collection the Commonwealth Law Revision Commission indexes, a keyword search for "security breach" returned sixteen Commonwealth Code hits that are all Uniform Commercial Code secured-transactions provisions using "security" in its collateral sense, and a search for "cybersecurity" returned zero Commonwealth Code hits at all; this is consistent with the jurisdiction's own privacy-topic finding, already filed, that the Commonwealth has no comprehensive personal-data statute and no breach-notification law.

Title 6's identity theft chapter, 6 CMC §§ 1721-1726 (Crimes Against the Person), criminalizes a person's own fraudulent use of another's personal identifying information and gives the victim a civil remedy against the thief; it is an offense committed by an intruder against a victim, the shape this topic's own seam rule assigns to the scraping topic rather than this one, and it is already filed there as a fraud and impersonation offense carrying no computer-access or scraping-specific doctrine of its own.

The Commonwealth Utilities Corporation Act's Duties section, 4 CMC § 8122, which covers CUC's supervision, construction, maintenance, rate-setting, and privatization authority over its electric, water, and sewer divisions, was read in full for this visit specifically to check for a cybersecurity duty on the Commonwealth's own critical-infrastructure operator and contains no match for "cyber" or "security" anywhere in its text; a broader code search for "critical infrastructure" returned eleven Commonwealth Code hits, all appropriations, land-compensation, and emergency-management provisions unrelated to a cyber-resilience regime.

The Investment Incentive Act of 2000's Qualifying Certificate program, 4 CMC § 50202, was also read in full: its eligibility list names fourteen priority business activities, including "internet related businesses and/or businesses engaged in internet commerce" and "manufacturing or processing of high technology products," alongside activities as varied as golf courses and dinner theaters, and none of the fourteen carries a cybersecurity, data-security, or vulnerability-handling condition, the same no-security-content finding already reached for Guam's parallel Qualifying Certificate program.

The Commonwealth's general Consumer Protection Act, 4 CMC § 5105, was read in full and lists thirty-four categories of unfair or deceptive trade practice; none of them addresses a business's own data-security or safeguards practices, and a code-wide search for "reasonable security" returned only Uniform Commercial Code secured-transactions provisions, so the Act carries no baseline security-programme duty of the kind NY SHIELD's GBL 899-bb or MA 201 CMR 17.00 impose.

As of .

Age gating law

The Northern Mariana Islands has not enacted an age-gating law in any of the four tracked families: no adult-content age-verification law, no social-media minor-access law, no app-store age-verification law, and no design code.

Title 6 (Crimes and Criminal Procedure) Division 1, Part 1, Chapter 3 (Sexual Offenses) criminalizes sexual abuse of a minor and once carried a dedicated Child Pornography Act, Article 2 of that chapter, repealed by Public Law 12-82 and folded into the chapter's general provisions; none of this is an age-verification or age-gating duty on a covered service, so it is not catalogued as an instrument here.

No bill requiring age verification for adult content, restricting minors' access to social media, or establishing an age-appropriate design code has been located in the CNMI Legislature's public-law record.

As of .

Reuse law

The Northern Mariana Islands has no press-publisher neighbouring right, no mandatory platform-to-publisher bargaining code, no hot-news or misappropriation doctrine, and no statute or reported case on whether a hyperlink, or a framed or inline display of one, is a communication to the public.

The Commonwealth Code contains no territorial copyright statute at all: copyright over news content published in the Commonwealth arises solely under the federal Copyright Act and its fair-use exception, both covered in the national document, and the Commonwealth has enacted no machine-readable text-and-data-mining opt-out of its own.

As of .

Case law

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

Reporting clocks that run here16 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 the Northern Mariana Islands 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
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 the United States, which applies in the Northern Mariana Islands

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.