Government bodies are regulated by a different set of cyber rules from the private sector, and those rules sit in statutes, functional standards, management memos and directives that rarely reference each other. A US federal agency answers to FISMA, OMB memoranda and CISA directives; a UK department to the GovS 007 functional standard and the Government Cyber Action Plan; an EU ministry to its national NIS2 transposition, where central government is in scope by default. This map puts those regimes side by side: who each one covers, what it demands, how incidents must be reported and who enforces it, with links to the detailed NHI Mgmt Group guides rather than repeating them. It is written for public sector CISOs, compliance leads and the suppliers who sell into government. Status as of 14 November 2026, checked on the official sources listed below; several instruments were being revised when this page was checked, so confirm current versions before relying on them.
Key takeaways
- Each jurisdiction uses a different lever. The US relies on statute (FISMA) plus OMB memoranda and CISA directives, the UK on functional standards and central plans, and the EU on a directive transposed into national law.
- EU central government is in NIS2 by default. Article 2(2)(f) brings central government public administration entities into scope, regional entities after a risk-based assessment, and Article 2(5) lets Member States add local government.
- Fines on public bodies are a national choice. NIS2 Article 34(7) leaves it to each Member State whether and to what extent fines can be imposed on public administration entities, so supervision powers matter more than penalties.
- US deadlines come from memos, not the statute. FISMA sets the framework and a seven day congressional notification for major incidents; most dated technical requirements (logging, software security, post-quantum migration) arrive through OMB memoranda.
- Suppliers inherit the obligations. FedRAMP for US federal cloud, contract clauses flowing from GovS 007 in the UK and NIS2 supply chain measures in the EU all reach vendors through procurement.
Regulations and frameworks at a glance
| Instrument | Jurisdiction and type | Who it covers | Status as checked | Detail guide |
|---|---|---|---|---|
| Federal Information Security Modernization Act of 2014 (FISMA), 44 U.S.C. 3551 and following | US, statute | Federal agencies and systems operated on their behalf, including by contractors | In force | FISMA Guide |
| OMB memoranda (for example M-26-05, M-26-14, M-26-15) | US, executive policy | Federal agencies | M-26-05 issued 23 January 2026, M-26-14 on 22 May 2026, M-26-15 on 24 June 2026 | OMB M-22-09 Federal Zero Trust Strategy Guide, OMB M-21-31 Logging Maturity Guide |
| CISA Binding Operational Directives (BODs) and Emergency Directives (EDs) | US, mandatory directives | Federal civilian executive branch agencies; not national security systems or certain Department of Defense and Intelligence Community systems | Rolling; check CISA for the current list | CISA KEV Catalogue Guide |
| FedRAMP, 44 U.S.C. 3607 to 3616 (FedRAMP Authorization Act) | US, statute and programme | Cloud products and services processing unclassified federal information | In force; Rev5 and FedRAMP 20x paths both active | FedRAMP Guide, FedRAMP vs FISMA |
| Government Functional Standard GovS 007: Security | UK, functional standard | Government organisations that adopt the functional standards | Version 2.0, 13 September 2021 | UK Government Functional Standard GovS 007 Security Guide |
| Government Cyber Action Plan | UK, government plan | Government organisations of all kinds | Published 6 January 2026; supersedes the Government Cyber Security Strategy 2022 to 2030 for current detail | Central Government Cybersecurity Programme Guide |
| NCSC Cyber Assessment Framework (CAF) | UK, assessment framework | NIS regulated sectors, critical national infrastructure and government | Version 4.0 listed by the NCSC | NCSC Cyber Assessment Framework (CAF) Guide |
| NIS2 Directive (EU) 2022/2555, public administration | EU, directive transposed nationally | Central government entities; regional entities after risk assessment; local government where a Member State chooses | Transposition deadline 17 October 2024, application from 18 October 2024; national status varies | NIS2 Directive Guide |
| Regulation (EU, Euratom) 2023/2841 | EU, regulation | Union institutions, bodies, offices and agencies | In force since 7 January 2024 | Central Government Cybersecurity Programme Guide |
Scope: which public bodies are covered
United States
FISMA places the duty on agency heads: 44 U.S.C. 3554 requires protections "commensurate with the risk and magnitude of the harm" for agency information and systems, including systems operated by contractors on the agency's behalf. CISA's directives page states that federal agencies are required to comply with DHS-developed directives, and that the directives do not apply to statutorily defined national security systems or to certain Department of Defense and Intelligence Community systems. State, local, tribal and territorial governments are outside FISMA; many use state cloud schemes covered in the StateRAMP / GovRAMP Guide and the practices in the Cybersecurity for Local Government Guide.
United Kingdom
UK central government security is set by policy rather than a single statute. GovS 007 is one of the government functional standards, which GOV.UK describes as a suite intended to promote consistent and coherent working within government organisations, with mandatory and advisory elements. The Government Cyber Action Plan, published by DSIT on 6 January 2026, sets expectations for "government organisations of all kinds" through measurable objectives and outcomes. Assessment against the NCSC CAF is how departments evidence their position; the Central Government Cybersecurity Programme Guide explains the assurance cycle. The separate UK Cyber Security and Resilience Bill Guide covers the reform of the NIS Regulations for regulated sectors.
European Union
NIS2 Article 2(2)(f) covers public administration entities "of central government as defined by a Member State in accordance with national law", and regional entities that, following a risk-based assessment, provide services whose disruption could have a significant impact on critical societal or economic activities. Article 2(5) lets Member States extend the directive to "public administration entities at local level" and to education institutions. Article 2(7) excludes public administration entities that carry out their activities in the areas of national security, public security, defence or law enforcement. Because the definition of central government is left to national law, the list of in-scope bodies differs by country: check the national guide, for example the Belgium NIS2 Implementation Guide or Denmark NIS2 Implementation. EU institutions themselves fall under Regulation 2023/2841 instead.
Key obligations mapped across regimes
The table maps common control areas to the instrument that creates the obligation in each jurisdiction. It shows where the requirement comes from, not its full content: follow the links for detail.
| Obligation area | United States (federal) | United Kingdom (central government) | EU Member State public administration |
|---|---|---|---|
| Security programme and accountability | FISMA 44 U.S.C. 3554(a) and (b): agency-wide programme, senior agency information security officer, CIO delegation | GovS 007 governance and accountable roles | NIS2 Article 20: management bodies approve and oversee cybersecurity risk-management measures |
| Risk-management measures | FISMA programme elements, NIST standards under the NIST Risk Management Framework (SP 800-37) Guide and NIST SP 800-53 Guide | CAF objectives: managing security risk, protecting against cyber attack, detecting events, minimising impact | NIS2 Article 21 measures, as transposed |
| Control testing | 44 U.S.C. 3554(b)(5): testing at a risk-based frequency, no less than annually | CAF self-assessment and independent review | Supervision by the competent authority, including audits and scans (Article 32 for essential entities) |
| Logging and visibility | OMB M-26-14 (22 May 2026) on agency logging and network visibility | CAF objective C, detecting cyber security events | NIS2 Article 21 incident handling measures |
| Software and supply chain | OMB M-26-05 (23 January 2026), risk-based software and hardware security; FedRAMP for cloud | GovS 007 supplier and contract security requirements | NIS2 Article 21 supply chain security measure |
| Cryptography transition | OMB M-26-15 (24 June 2026) on migration to post-quantum cryptography; see the Post-Quantum Cryptography Deadlines Tracker | NCSC migration guidance (advisory) | National guidance under NIS2 Article 21 cryptography measure |
| Annual reporting | 44 U.S.C. 3554(c): annual report to OMB, DHS, congressional committees and the Comptroller General | Departmental assurance returns to the centre | National registration and supervision regime |
Incident reporting clocks
| Regime | Trigger | Clock | Recipient |
|---|---|---|---|
| FISMA, 44 U.S.C. 3554(b)(7)(C)(iii)(III) | Reasonable basis to conclude a major incident has occurred | Not later than 7 days, with updates as information emerges | Specified congressional committees, alongside notification to the federal incident centre under section 3556 |
| NIS2 Article 23(4), as transposed | Significant incident | Early warning within 24 hours, incident notification within 72 hours, final report within one month of the notification | National CSIRT or competent authority |
| UK central government | Incident under departmental policy | Set by government policy and the NCSC incident process rather than statute | NCSC and the government security function |
For the full multi-sector picture, including private sector rules a public body may also meet as an operator, see the Cyber Incident Reporting Requirements Map.
Enforcement and oversight
- United States: oversight is by OMB, CISA (directives), Inspectors General through the annual independent evaluation under 44 U.S.C. 3555, Congress through reporting, and GAO. There are no fines on agencies; consequences are budgetary, reputational and through oversight hearings.
- United Kingdom: compliance with functional standards and the action plan is driven through the government security function, departmental accounting officers and central assurance, not a regulator with penalty powers.
- European Union: NIS2 Article 34(4) sets maximum fines for essential entities of at least EUR 10 000 000 or 2% of worldwide annual turnover, whichever is higher, and Article 34(5) at least EUR 7 000 000 or 1.4% for important entities. Article 34(7) lets each Member State decide whether and to what extent fines apply to public administration entities, without prejudice to supervisory powers under Articles 32 and 33.
What it means for suppliers to government
- US federal cloud: the FedRAMP statute establishes the programme within GSA as a standardised, reusable approach to security assessment and authorisation for cloud products processing unclassified federal information. The Code notes that the section is repealed five years after 23 December 2022, so watch for reauthorisation. The FedRAMP site listed 559 certified services, 39 under FedRAMP 20x, when checked; see FedRAMP 20x.
- Contractor-operated systems: FISMA covers systems operated by contractors on behalf of an agency, so agency controls and reporting flow into contracts.
- UK: GovS 007 obligations reach suppliers through contracts and supplier assurance; compare schemes in Government Cloud Authorisation Schemes Compared.
- EU: public administration entities must manage supply chain security under their national NIS2 measures and pass requirements into tenders.
Where identity fits
Every regime above expects strong authentication and control of privileged and service access, and auditors increasingly ask about machine credentials: API keys used by integration platforms, service accounts on shared government platforms and workload identities in cloud tenancies. US agencies working to the federal zero trust strategy should treat non-human identities as part of the identity pillar; see the OMB M-22-09 Federal Zero Trust Strategy Guide and the AI Security in Government and Public Sector guide for agent identities.
Compliance steps
- Confirm which regimes apply. Record the legal basis for each body: federal agency, UK department or arm's length body, EU central, regional or local entity, and any sector role (for example a public water utility) that adds critical infrastructure rules from the Critical Infrastructure Regulation Map.
- Check national transposition. For EU bodies, read the national NIS2 law for the definition of central government and whether fines apply.
- Build one obligations register. Use the mapping table as columns; record each requirement, source, owner and evidence once and reuse it.
- Align incident procedures to the shortest clock. Design to the NIS2 24 hour early warning where it applies, and to the FISMA major incident process in US agencies.
- Push requirements to suppliers. Put the authorisation scheme, reporting duty and right to audit into contracts.
- Track changes. Review OMB memoranda, CISA directives, GOV.UK functional standards and national NIS2 laws on a fixed cycle.
Common failure patterns
- Assuming "public sector" means out of scope. EU central government is in NIS2 by default; only the Article 2(7) areas are excluded.
- Relying on superseded documents. The UK strategy page now points to the Government Cyber Action Plan, and US memos rescind earlier ones; registers citing old versions fail audit.
- Treating no fines as no consequence. Supervisory powers, Inspector General findings and congressional reporting carry real weight.
- Forgetting contractor systems. FISMA covers systems run on an agency's behalf; leaving them out of inventories is a frequent finding.
- Single clock incident plans. A plan built only for a seven day or 72 hour clock misses the shorter early warning.
Practitioner checklist
- Legal basis and applicable regimes recorded for each organisation in scope.
- National NIS2 transposition read for definitions, registration and penalty rules (EU).
- Current versions confirmed for GovS 007, the Government Cyber Action Plan and the CAF (UK).
- Current OMB memoranda and CISA directives listed with owners and due dates (US).
- Single obligations register with evidence per requirement.
- Incident procedure tested against the shortest applicable reporting clock.
- Supplier contracts carry authorisation, reporting and audit clauses.
- Machine identities and service accounts included in identity controls and audits.
Standards and references
- US Code: 44 U.S.C. 3554, Federal agency responsibilities
- US Code: 44 U.S.C. 3608, Federal Risk and Authorization Management Program
- OMB: Memoranda
- CISA: Cybersecurity Directives
- GOV.UK: Government Functional Standard GovS 007, Security
- GOV.UK: Government Cyber Action Plan
- NCSC: Cyber Assessment Framework
- EUR-Lex: Directive (EU) 2022/2555 (NIS2 Directive)
- EUR-Lex: Regulation (EU, Euratom) 2023/2841
- FedRAMP: Official site
This guide summarises public sector cyber security regulation in the US, UK and EU for security practitioners and is not legal advice; confirm obligations with your legal and compliance teams and the primary texts. Related NHI Mgmt Group resources: Central Government Cybersecurity Programme Guide · Global Cybersecurity Regulatory Map · FISMA Guide · Cybersecurity for Local Government Guide