Councils, counties and municipalities run statutory services that cannot simply stop, on estates built over decades, with small security teams and budgets set years in advance, and ransomware crews know it. A single compromised account can take out benefits payments, housing repairs, planning portals, social care case files and emergency dispatch at the same time, and recovery is often measured in months rather than days. This guide covers what makes local government different from a typical enterprise, the threats that actually hit councils, the regulation and assurance regimes in the UK, EU and US, and the controls that give the most protection per pound spent. It is written for council and municipal IT and security leads, Senior Information Risk Owners, auditors and the suppliers that run services on their behalf.
Key takeaways
- Service continuity is the real asset. Councils hold sensitive personal data, but the harm that lands hardest is losing statutory services such as social care, housing, revenues and benefits for weeks; plan and test for that first.
- Old accounts and old systems are the usual way in. The ICO found that the 2020 attack on Hackney Council started from a dormant account with an insecure password, combined with patching that did not cover every device.
- Assurance regimes are converging on the CAF. England's Cyber Assessment Framework for local government adapts the NCSC CAF, while EU local bodies may fall under NIS2 where a member state has chosen to include them.
- Suppliers hold the keys to many services. Line-of-business systems are often hosted and supported by a handful of vendors with standing remote access, so third-party access control is a priority control, not a procurement formality.
- Free national support is underused. CISA, the NCSC and sector bodies offer free scanning, threat sharing, assessments and incident support that a small council team could not build alone.
Why local government is different
Local government security looks like enterprise security with four extra constraints. Each one changes which controls come first.
- Breadth of services: a single district or county may run hundreds of distinct services, from waste collection rounds to safeguarding case management, each with its own line-of-business application, database and often its own supplier. Asset inventories are rarely complete.
- Statutory duty to keep going: services such as adult and children's social care, homelessness support and electoral registration have legal deadlines. Paper fallback must exist and must have been rehearsed, because "we will restore from backup in a week" is not acceptable for a child protection referral.
- Long-lived technology: procurement cycles, capital budgets and bespoke integrations keep systems in service long after vendor support ends. Unsupported servers, legacy file shares and old service accounts accumulate.
- Shared and federated estates: councils share services with neighbouring authorities, police, health bodies and schools, and connect to national networks and portals. Trust relationships cross organisational boundaries that the council does not fully control.
- Public scrutiny: incidents are reported in local press and examined by elected members and regulators, and data protection regulators can and do issue public reprimands.
Threats that actually hit councils
The threat picture is dominated by financially motivated crime rather than espionage, although councils that host critical infrastructure or election functions also attract state interest. The table maps the common scenarios to ATT&CK techniques and the controls that break them.
| Threat scenario | Typical entry and impact | ATT&CK technique | Priority controls |
|---|---|---|---|
| Ransomware with data theft | Encryption of file servers and line-of-business systems, deletion of backups, publication of resident data | T1486 Data Encrypted for Impact, T1490 Inhibit System Recovery | Immutable or offline backups, tiered admin, EDR on every server, tested restore |
| Dormant or default accounts | Old staff, test or supplier accounts with weak passwords still able to log on | T1078 Valid Accounts, T1078.003 Local Accounts | Joiner, mover, leaver process tied to HR; quarterly dormant account sweep; LAPS for local admin |
| Exposed remote access and edge devices | VPN, Citrix or remote desktop gateways without MFA or with unpatched flaws | T1133 External Remote Services, T1190 Exploit Public-Facing Application | MFA on every external entry point, KEV-driven patching for edge devices |
| Phishing and business email compromise | Credential theft from staff and councillors, fraudulent supplier bank detail changes | T1566 Phishing, T1657 Financial Theft | Phishing-resistant MFA for admins and finance, call-back verification for bank detail changes |
| Supplier compromise | Attacker reaches the council through a managed service provider or hosted application support channel | T1078 Valid Accounts (via third party), T1133 External Remote Services | Brokered, time-limited supplier access with session logging; contractual incident notification |
| Hybrid identity takeover | Theft of directory synchronisation credentials to move from on-premises AD into the cloud tenant | T1078 Valid Accounts | Treat sync servers as tier 0, separate cloud-only admin accounts, MFA on all admins |
The hybrid identity row is not theoretical. Microsoft reported that the Storm-0501 group targeted US government, transportation and law enforcement organisations, exploiting known edge flaws such as CVE-2022-47966 (Zoho ManageEngine) and CVE-2023-4966 (Citrix NetScaler), then stealing Entra Connect Sync credentials to reach the cloud. See the Storm-0501 Hybrid Cloud Attacks 2024 breach analysis. Both CVEs are in the CISA Known Exploited Vulnerabilities catalog with known ransomware use.
Regulation and assurance regimes
Councils are rarely regulated by a single cyber law. Obligations come from data protection law, national assurance schemes, network connection conditions and, in the EU, NIS2 where member states have chosen to apply it locally. Confirm the current position in your own jurisdiction, because several of these regimes have changed recently.
| Jurisdiction | Regime | What it asks of local bodies | Status notes |
|---|---|---|---|
| England | Cyber Assessment Framework (CAF) for local government | Adapted by MHCLG from the NCSC CAF. Five stages: understand the CAF, prepare and set scope, complete a self-assessment including architecture maps, obtain an independent assurance review, then deliver an improvement plan | Guidance hosted on security.gov.uk (updated October 2026). Check with MHCLG whether participation is expected of your authority |
| UK | UK GDPR and Data Protection Act 2018 | Appropriate technical and organisational security (Article 32), breach notification to the ICO within 72 hours where required | The ICO publishes reprimands against public bodies rather than fines in many cases, but findings are public |
| UK | Public Services Network (PSN) connection and Cyber Essentials | Connection conditions for councils using PSN services; Cyber Essentials as a baseline for suppliers and many internal estates | See the Cyber Essentials Guide |
| EU | NIS2 Directive (EU) 2022/2555 | Central and regional public administration entities are in scope; member states may extend it to local level. Risk management measures and reporting: early warning within 24 hours, incident notification within 72 hours, final report within one month | Coverage of municipalities differs by member state transposition. See the NIS2 Directive Guide |
| United States | State and Local Cybersecurity Grant Program (SLCGP) | Grant funding tied to state cybersecurity plans, with local pass-through | Funded at $1 billion under the 2021 infrastructure law; it lapsed in September 2025 and was temporarily extended in the November 2025 funding deal, with longer-term reauthorisation still before Congress at that time. Check current status before planning on it |
| United States | State breach notification and state cyber laws | Notification of residents and, in some states, mandatory incident reporting by local entities to a state agency | Varies by state; several states also restrict ransom payments by public bodies |
For the underlying framework, see the NCSC CAF Guide. The CAF's outcome-based structure means a self-assessment can honestly record "not achieved" against an outcome, which is more useful to an improvement plan than a checkbox score.
Priority controls for councils
With small teams, sequence matters more than coverage. The ICO's recommendations after the Hackney reprimand are a good minimum: multi-factor authentication on external connections, logging and monitoring, acting on endpoint protection alerts, strong unique passwords for privileged, admin and service accounts, and applying critical patches within 14 days where possible. Build out from there.
Identity and access
- MFA everywhere external: VPN, remote desktop gateways, webmail, Microsoft 365 or Google Workspace, supplier portals and councillor access. Admins and finance staff move to phishing-resistant methods first. See the Phishing-Resistant MFA Guide.
- Leaver and dormant account hygiene: connect HR leaver events to account disablement within one working day, and run a monthly report of accounts with no logon in 90 days, including test, training and supplier accounts.
- Tiered administration: separate admin accounts from daily accounts, keep domain controllers, directory sync servers and backup consoles in tier 0, and remove standing domain admin rights from supplier accounts.
Vulnerability and estate management
- KEV first: patch internet-facing devices listed in the CISA KEV catalog within days, ahead of routine cycles. See the Patch Management Guide.
- Unsupported systems register: list every end-of-support system, the service it supports, compensating controls (segmentation, no internet access, application allow-listing) and a funded exit date.
- Use national scanning: US local bodies can use CISA's free services, including Cyber Resilience Reviews, Automated Indicator Sharing and malware analysis; UK councils can use NCSC Active Cyber Defence services where eligible.
Backup and recovery
- Protect the backups from the domain: in Hackney the attackers deleted around 10% of backups. Use immutable storage, separate credentials not joined to the production domain, and MFA on the backup console. See the Backup Security and Immutable Backup Guide.
- Restore by service, not by server: define recovery order by statutory service (social care, homelessness, revenues and benefits, payroll) and test a full service restore at least annually.
Suppliers, shared services and hosted applications
Most council line-of-business systems, for revenues and benefits, social care, planning, housing and libraries, come from a small market of specialist suppliers. Many are hosted by the supplier or supported over persistent remote access. That concentration means one supplier incident can affect dozens of authorities at once, and one poorly controlled support channel can bypass every control above.
| Supplier pattern | Risk | Control |
|---|---|---|
| Vendor support over always-on VPN or remote tool | Shared supplier credentials, no MFA, unlogged sessions | Brokered access, named individual accounts, MFA, session recording, access enabled per ticket |
| Supplier-hosted case management | Council data held outside its own controls and backups | Contract clauses for incident notification, backup and restore testing evidence, data export on demand |
| Shared service with another authority | Trust relationships and shared admin accounts across organisations | Documented responsibility matrix, separate admin identities per organisation, joint incident plan |
| Integrations and data feeds to national systems | Long-lived API keys and service accounts no one owns | Service account inventory with named owner, credential rotation, alerting on unusual use |
See the Third-Party Access Guide and the Third-Party Risk Management Guide for contract and access patterns.
Where identity fits
Every incident pattern above runs through an account: a dormant user, a supplier login, a directory sync service, an integration key. Councils typically hold thousands of service accounts and scheduled tasks created by suppliers over many years, often with domain admin rights because that was the quickest way to make an installation work. Building an inventory with owners, removing interactive logon from service accounts and moving to group managed service accounts where possible removes a large share of attack paths. See the Local Government Identity Security Guide, the Service Account Security Guide and the Public Sector Identity Security Guide.
Implementation roadmap
A phased plan for a council with a small security function. Each phase has a test and a rollback.
- Months 0 to 3, close the doors: enforce MFA on every external entry point, starting with admins and remote access; run the first dormant account sweep (disable rather than delete, so an account can be re-enabled quickly if a hidden dependency breaks a service); confirm KEV-listed edge devices are patched. Test with a pilot group of IT staff before wider rollout; roll back MFA policies per group if a service fails.
- Months 3 to 6, protect recovery: separate backup credentials from the domain, enable immutability, and perform a test restore of one statutory service end to end. Write the paper fallback for the top five services and rehearse it with service managers.
- Months 6 to 9, supplier access: inventory every supplier connection, move them to brokered, logged access, and add incident notification clauses at the next contract renewal. Pilot with one supplier first and keep the old route disabled, not removed, for two weeks.
- Months 9 to 12, assurance and detection: complete the CAF self-assessment (England) or NIS2 gap analysis (EU), deploy EDR to every server, centralise logs from identity, VPN, email and backup systems, and run a tabletop exercise with senior leaders and elected members.
- Year 2, harden and measure: tiered administration, retirement of unsupported systems from the register, phishing-resistant MFA for all staff, and quarterly reporting of the metrics below to the audit committee.
Decision guidance: small district versus large unitary or city
| Decision | Small council or municipality | Large county, unitary or city |
|---|---|---|
| Security operations | Managed detection and response service, or shared SOC with neighbouring authorities | In-house SOC or hybrid, with 24x7 cover for critical services |
| Identity platform | Use what the existing cloud suite provides; focus on MFA and leaver process | Dedicated identity governance and privileged access tooling |
| Assurance | CAF or Cyber Essentials baseline, independent review shared across a regional partnership | Full CAF independent assurance review, internal audit cycle, penetration testing per major change |
| Backup | Immutable cloud backup service with separate credentials | Isolated recovery environment with clean-room rebuild capability |
| Threat intelligence | National feeds (CISA AIS, sector ISACs, regional warning points) | National feeds plus own detection engineering |
The trade-off is usually between building capability and buying it. Small authorities get more from shared services and regional partnerships than from tools they cannot staff; large authorities should avoid buying overlapping platforms before the basics in the roadmap are done.
Detection and measurement
Log sources to prioritise: identity provider sign-ins and MFA events, VPN and remote gateway logs, privileged group changes in Active Directory, backup console actions (especially deletions and retention changes), email rule changes and EDR alerts. Alert on backup deletion, new mailbox forwarding rules, logons by accounts flagged as dormant and supplier sessions outside an approved window.
- MFA coverage: percentage of external entry points and of privileged accounts with MFA enforced (target 100%).
- Dormant accounts: number of enabled accounts with no logon in 90 days, tracked monthly (target trending to zero).
- Critical patch time: median days to patch KEV-listed vulnerabilities on internet-facing systems (target under 14 days, in line with the ICO's recommendation).
- Restore confidence: number of statutory services with a successful full restore test in the last 12 months.
- Supplier access: percentage of supplier connections that are brokered, individually named and logged.
- Unsupported systems: count of end-of-support systems without a funded exit date.
Framework mapping
| Control area | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 |
|---|---|---|
| Asset and service inventory | ID.AM-01 | CA-7 Continuous Monitoring (supporting) |
| Account lifecycle and MFA | PR.AA-03 | AC-2 Account Management, IA-2 Identification and Authentication |
| Patching | ID.RA-01 | SI-2 Flaw Remediation |
| Backups | PR.DS-11, RC.RP-03 | CP-9 System Backup |
| Supplier risk | GV.SC-07 | SR-6 Supplier Assessments and Reviews |
| Incident response with third parties | RS.MA-01 | IR-4 Incident Handling |
Common failure patterns
- Dormant accounts left enabled: the ICO found that Hackney's attackers used a dormant account with an insecure password that was still connected to council servers; around 440,000 files were encrypted and some services were disrupted until 2022.
- Patching that misses devices: a patch process that covers managed laptops but not appliances, test servers or supplier-managed boxes leaves the edge exposed.
- Backups on the same domain: backup consoles joined to the production directory let attackers delete or encrypt recovery points before triggering ransomware.
- Supplier access nobody owns: always-on vendor connections with shared credentials survive contract changes and staff turnover.
- Hybrid identity treated as plumbing: directory sync servers with weak protection let attackers move from on-premises compromise to the cloud tenant, as in the Storm-0501 campaigns.
- No rehearsed paper fallback: service teams discover during an incident that they cannot run statutory processes without the system, and recovery priorities are set by whoever shouts loudest.
Lessons from incidents
The Hackney case shows the cost profile of a council incident: the ICO reported that at least 280,000 residents and staff were affected, 9,605 records were exfiltrated, and the encrypted data included special category information such as health, ethnicity and religious belief. The ICO chose a reprimand rather than a fine, but its findings centred on basics: an unaddressed dormant account and incomplete patching. The Storm-0501 activity shows the same basics, edge vulnerabilities and weak account protection, being used to move from on-premises networks into cloud tenants of public bodies.
Practitioner checklist
- Enforce MFA on every external entry point and every privileged account, with phishing-resistant methods for admins.
- Link HR leaver events to same-day account disablement and run a monthly dormant account report.
- Patch KEV-listed vulnerabilities on internet-facing systems within 14 days at most, faster for edge devices.
- Separate backup credentials from the production domain, enable immutability and alert on deletions.
- Test a full restore of at least one statutory service each year and rehearse paper fallback for the top five services.
- Inventory supplier connections and service accounts, each with a named owner, and move supplier access to brokered, logged sessions.
- Treat directory sync, domain controllers and backup consoles as tier 0 assets.
- Complete the CAF self-assessment or NIS2 gap analysis and fund the improvement plan.
- Register for free national services: CISA offerings in the US, NCSC services in the UK, and the relevant ISAC or warning point.
- Report the six metrics above to the audit committee each quarter.
Standards and references
- UK Government Security: Cyber Assessment Framework (CAF) for local government
- EUR-Lex: Directive (EU) 2022/2555 (NIS2)
- CISA: State, Local, Tribal and Territorial Government
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev. 5
- CISA: Known Exploited Vulnerabilities Catalog
- ICO: ICO reprimands London Borough of Hackney following cyber attack
- Nextgov/FCW: Government funding deal reups cyber grant program
Related NHI Mgmt Group resources: Local Government Identity Security Guide · Public Sector Identity Security Guide · Ransomware Prevention Guide · Cybersecurity for Smart Cities Guide · Cybersecurity for Schools Guide. This guide summarises regulatory regimes that apply to local government and is not legal advice.