As the calendar year draws to a close, local governments face the seasonal surge of phishing, ransomware, and DDoS attacks. Municipal and county employees are planing for the holidays, and cybercriminals are planning too. They're scanning for unpatched systems, dormant accounts, and anything they can exploit.
The steps you take now can prevent weeks of disruption later.
The Pattern of Attack
Year after year, cyberattacks spike during the final quarter:
That's because during holidays, vacations can disperse management and reduce IT coverage. But a single compromised account can knock out payment systems or permit portals and compromise communications and payroll systems.
It's important to remove as many data security gaps as you can in advance.
Cybercriminals target counties and municipalities for three concrete reasons. First, they can redirect payroll, submit fake invoices, manipulate vendor payments, and access personal information. A breach of your finance, accounts payable, or property information systems makes it easy for attackers to have direct access to money or information markets on the dark web.
Second, they know that when municipalities can't deliver services, access court records, or process payments, the disruption creates enormous pressure to pay ransoms quickly. Service outages are visible and urgent in ways that attacks on private companies may not be.
Third, utilities, traffic control systems, and public safety networks run on digital infrastructure that municipalities control. Breaching these systems doesn't just disrupt city services; it can threaten public safety and give attackers more leverage for extortion.
1. Build Your Incident Response Plan
Create a written plan that identifies critical systems, defines who has off-hours decision authority, and includes decision-making rules. For example: "If one non-critical system is compromised, the incident commander may act. If multiple critical systems are affected, contact the city manager, town manager, or county administrator."
Assign a primary incident commander and a backup. Run a 2-3 hour tabletop exercise in early November with IT, finance, communications, legal, and leadership. Walk through a realistic scenario: ransomware spreads to your permitting system. Who calls whom? Who talks to media? Which systems get isolated first?
Document gaps and address them before a real incident.
2. Deploy Continuous Monitoring
Most ransomware goes undetected for days. Continuous monitoring catches attacks early.
3. Vet Software Vendors
Require role-based access controls (RBAC) for all software and SOC 2 Type II compliance from all cloud software vendors. Role-based access controls constrain the information any user account can access, which also limits what a hacker can beach. SOC 2 Type II compliance means an independent auditor has verified that your software provider's security controls are well-designed and operate consistently over time. Also ask:
If a vendor can't meet your preferred standards, document the gap and implement compensating controls like network segmentation. This limits which systems that vendor can access, so a breach there doesn't spread to your entire network.
4. Patch Critical Systems
Dedicate a focused sprint in early December to patch operating systems, databases, email systems, and file-sharing apps. Schedule during low-traffic periods and notify residents. Test patches in a non-production environment first. Have a rollback plan.
Document what you patch and what you defer. Log everything. If you're under-resourced, consider hiring a contractor for a few days. It's less expensive than a breach.
5. Train Staff on Holiday Phishing
Generic security training often doesn't work. The best practice is to show staff real examples: fake delivery notices, bogus invoices, credential-reset scams. Keep sessions short (10-15 minutes) and role-specific.
Follow up with a phishing test email. Many email providers include built-in phishing simulation tools, or affordable third-party services offer free trials. Track who clicks and who reports it. Use results to target additional training.
Off-Hours Decision Authority
Before holidays, establish clear authority for decisions when leadership is unavailable. Document:
Test this during your tabletop exercise.
Resident Communication
Prepare message templates now for common scenarios. When a crisis occurs, you can adapt these templates quickly rather than starting from scratch.
Assess monitoring options and evaluate vendor security compliance.
If you can only do one thing, create your incident response plan. It's the foundation for everything else.
Further Reading
• CISA State and Local Cybersecurity Grant Program: https://www.cisa.gov/slcgp