Law / Micronesia

FSM Cybersecurity Act 2025 (Bill), Critical Information Infrastructure Incident Reporting Clock

§ 412, Subchapter III, C.B. No. 24-14 (Cybersecurity Act 2025), proposed new Chapter 4, Title 21, FSM Code

A vulnerability and incident reporting rule binding public and private bodies.

Obligation class
Security

What it requires

  • It reaches you only where the Secretary of Justice has designated a computer, computer system, or computer data you own or operate as critical information infrastructure; see this jurisdiction's companion risk-management row for the designation criteria.
  • Notify the Secretary of Justice and the CERT-FSM of a significant cybersecurity incident affecting your critical information infrastructure or an interconnected system: an early warning within 24 hours of becoming aware of it, a fuller notification within 72 hours, and a final report within 30 days of that notification.NIST CSF 2.0RS.CO-02
  • For an ongoing significant cybersecurity incident, submit a progress report to the Secretary of Justice and the CERT-FSM within 30 days of the notification, and a final report within 30 days of the handling of the incident (Section 412(2)(d)).NIST CSF 2.0RS.CO-03
  • Establish mechanisms and processes to promptly detect a cybersecurity threat or incident affecting your critical information infrastructure.NIST CSF 2.0DE.CM-09

These lines are LexLint's reading of the law's text.

In the frameworks

NIST CSF 2.0
  • DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • RS.CO-02Internal and external stakeholders are notified of incidents
  • RS.CO-03Information is shared with designated internal and external stakeholders
CIS Controls
  • 3.10Encryption of sensitive data as it crosses networks.
  • 3.11Encryption of sensitive data where it is stored on servers and applications.
  • 6.8Access rights defined by job role, and kept up to date.
  • 7.1A documented, reviewed approach to finding and handling weaknesses.
FINOS AIGF
1 more
ENISA NIS2 guidance
  • 2.1Risk management framework
  • 3.1Incident handling policy
  • 4.1Business continuity and disaster recovery plan
  • 6.2Secure development life cycle
  • 6.5Security testing
  • 6.10Vulnerability handling and disclosure
2 more
  • 9.1Cryptography
  • 11.2Management of access rights

Our reading of where this law's duties sit in each framework, and in the NIST CSF 2.0, line by line beside each duty above. It never says that running a control meets the law. How we read a framework against the law

CIS Critical Security Controls® (CIS Controls®) v8.1 © Center for Internet Security, Inc. Safeguard numbers are used under a CIS Controls Supporter License; the one-line descriptions beside them are our own, not CIS text.

If you get it wrong

Criminal exposureYes

Private right of actionNo

Criminal exposure note

Section 412(4) makes a failure, without reasonable excuse, to comply with the incident-notification duty under section 412(1) an offense, liable on conviction to a fine not exceeding $10,000 or imprisonment for a term not exceeding one year or both.

Who enforces it

Enforcement body

Secretary of Justice, Department of Justice of the Federated States of Micronesia, and the CERT-FSM operated by the Department of Transportation, Communications and Infrastructure (DTCI)

Settledness

C.B. No. 24-14 was introduced on .

As of
Open questions
  • Will C.B. No. 24-14 be enacted, and if so, will its section 412 reporting clock be amended before passage?
  • How will the Secretary define what makes a cybersecurity incident significant enough to trigger the section 412(1) notification duty for a given owner?

What this law does

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

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Section 412(1) of the same bill, C.B. No. 24-14 (Cybersecurity Act 2025), would require the owner of critical information infrastructure to notify the Secretary of Justice and the CERT-FSM (the national Computer Emergency Response Team the bill would create) of a significant cybersecurity incident affecting its critical information infrastructure or an interconnected system. The owner must submit an early warning within twenty-four hours of becoming aware of the incident.

The owner must then submit a fuller incident notification within seventy-two hours. The owner must submit a final report not later than thirty days after that notification, and, for an ongoing incident, a progress report on the same thirty-day clock. Section 412(3) would separately require the owner to establish mechanisms and processes for promptly detecting a cybersecurity threat or incident affecting its critical information infrastructure.

A failure to comply with the reporting duty is a criminal offense carrying a fine of up to $10,000 or imprisonment of up to one year or both. The bill was introduced in the Congress of the Federated States of Micronesia on .

When LexLint raises it

When your app profile says your app runs an essential service.

Back to the example  ·  Lint your app

Page updated .