Tag: technology

Emerging Tech & AI Public Works & Infrastructure (DPW)

What Municipal Leaders Need to Know About Today’s Cyber Threats to Water Systems

Post author By Elisabeth Dubois
Post date August 14, 2026
No Comments on What Municipal Leaders Need to Know About Today’s Cyber Threats to Water Systems

For most residents, turning on the faucet is one of the most routine actions of the day. They expect clean water to come out. They expect toilets to flush, wastewater to be treated, fire hydrants to work, and the systems supporting their community to operate quietly in the background.

Behind that reliability, however, is an increasingly complex network of pumps, sensors, programmable logic controllers (PLCs), supervisory control and data acquisition (SCADA) systems, computers, communications equipment, vendors, and employees. As water and wastewater operations have become more connected, they have also become more exposed to cyber threats.

That threat is no longer theoretical.

In July 2026, the Cybersecurity and Infrastructure Security Agency (CISA), the FBI, the Environmental Protection Agency (EPA), and other government partners issued an updated warning regarding Iran-affiliated cyber actors targeting U.S. critical infrastructure. Federal agencies specifically highlighted exploitation of PLCs across multiple sectors, including U.S. water and wastewater facilities.

EPA has also warned more broadly that cyberattacks against public water systems are increasing.

For municipal leaders, the lesson should be clear: cybersecurity at a water or wastewater facility is no longer simply an IT issue. It is an operational resilience, public safety, financial, and governance issue.

Why Water Systems Are Attractive Targets

Water and wastewater utilities present a particularly challenging cybersecurity environment. Many municipalities operate systems that combine modern technology with equipment installed years—or sometimes decades—ago. Operational technology may have been designed primarily for reliability and longevity rather than today’s cybersecurity environment.

At the same time, remote connectivity has become increasingly common. Employees, contractors, integrators, and vendors may need remote access to equipment. Internet-connected human-machine interfaces (HMIs), PLCs, SCADA environments, and other operational systems can create pathways into infrastructure when they are improperly configured or inadequately protected.

The threat actors themselves vary. A municipality may face ransomware criminals seeking money, hacktivists looking for attention, opportunistic attackers scanning the internet for exposed devices, or sophisticated actors associated with foreign governments.

The motivation may be different, but the result can be the same: disruption of an essential public service.

EPA’s cybersecurity incident guidance warns that incidents can interfere with treatment, distribution, and conveyance processes; compromise industrial control systems; expose sensitive information; damage components; and disrupt a utility’s ability to provide safe water and wastewater services.

Cybersecurity Has to Reach the Operational Technology Environment

One of the most important conversations municipal leaders should have with their water departments is simple:

What equipment in our water or wastewater operations can be accessed remotely—and who can access it?

The answer may surprise you.

Municipalities should identify every internet-facing or remotely accessible operational technology asset, including HMIs, PLCs, SCADA systems, engineering workstations, remote monitoring equipment, vendor connections, and communications devices.

Then determine whether that connectivity is actually necessary.

Federal guidance recommends restricting internet access to process-control systems unless absolutely necessary, separating operational/process-control traffic from business networks, identifying all methods of remote access, eliminating unnecessary remote connectivity, and tightly restricting whatever access must remain.

This is especially important because attackers do not necessarily need to develop an elaborate attack specifically for a small municipality. Poorly secured internet-connected equipment can provide an opportunity.

In other words, being small does not necessarily make a municipality invisible.

Seven Actions Municipalities Can Take Now

Municipal cybersecurity can quickly become overwhelming, particularly for smaller communities with limited staff and budgets. Rather than trying to solve everything at once, municipal leaders can begin with several practical actions.

1. Know what you have.
Create and maintain an inventory of critical IT and operational technology. Identify PLCs, SCADA servers, HMIs, engineering workstations, remote-access systems, network equipment, computers, software, and communications systems supporting water operations. Document who owns, maintains, and has access to each critical system. CISA has emphasized asset inventories as a foundation for protecting operational technology.

2. Identify and reduce internet exposure.
Determine which devices and systems are accessible from the public internet. If internet connectivity is unnecessary, remove it. Where remote access is operationally necessary, restrict it and protect it appropriately. Reducing exposure to the public-facing internet is the first action highlighted in the federal government’s Top Cyber Actions for Securing Water Systems.

3. Separate IT from OT.
The computer used for email and administrative work should not have unrestricted access to systems controlling pumps, valves, treatment processes, or chemical operations. Network segmentation and firewalls can help prevent a compromise of the municipality’s business network from becoming an operational emergency.

4. Review remote and vendor access.
Municipalities frequently depend upon outside vendors to maintain specialized equipment. That relationship does not eliminate the municipality’s responsibility for understanding how vendors connect to its environment. Ask who has remote access, how accounts are authenticated, whether access is continuously available or enabled only when needed, and how access is removed when an employee or contractor leaves.

5. Prepare to operate manually.
Technology can fail due to cyberattacks, equipment failures, communication outages, or other emergencies. Public works personnel should know how critical operations will continue if SCADA or other automated systems become unavailable. Procedures should be documented, accessible offline, and periodically exercised.

6. Develop and exercise a cyber incident response plan.
Do not wait until an attack occurs to decide who calls the mayor, supervisor, emergency management, law enforcement, regulators, IT provider, cyber insurer, or outside incident-response firm. EPA now provides a customizable Cybersecurity Incident Response Plan specifically for drinking water and wastewater systems. The agency recommends that utilities develop, practice, and regularly update these plans.

7. Assess the system—and turn the findings into a budget.
An assessment sitting on a shelf does not reduce risk. Identify vulnerabilities, prioritize them based on operational consequences, assign responsibility, set deadlines, and determine the required funding. EPA offers both self-assessment resources and a program through which water systems can receive cybersecurity assessments and risk-mitigation assistance.

Questions Elected Officials Should Be Asking

Elected officials do not need to become SCADA engineers or cybersecurity specialists. They do, however, have a responsibility to ask appropriate governance questions.

At an upcoming board or council meeting, consider asking:

Do we have a current inventory of our water and wastewater IT and operational technology?
Are any PLCs, HMIs, SCADA components, cameras, or other control devices directly accessible from the internet?
Who can remotely access our water systems—including outside vendors?
Is multifactor authentication required for remote access where technically feasible?
Are our administrative IT systems appropriately separated from operational technology?
When were our critical systems last assessed for cybersecurity vulnerabilities?
Do we maintain secure backups, and have we tested our ability to restore them?
Can operators safely maintain essential operations if SCADA or network connectivity becomes unavailable?
Do we have a written cyber incident response plan?
Has that plan actually been exercised with municipal leadership, public works, IT, emergency management, and other key partners?
Who has authority to make critical decisions during an incident?
Who must be notified if an incident occurs?
What cybersecurity improvements need to be included in the next municipal budget or capital plan?

If municipal leadership cannot readily answer those questions, that is not necessarily evidence that the municipality has failed. It is evidence that a conversation needs to begin.

Put Cybersecurity Into the Emergency Response Plan

Cybersecurity should not exist in isolation from emergency management.

A cyberattack against a water facility could simultaneously become a public works emergency, a public health issue, a communications challenge, a financial event, and a political crisis.

That means the emergency response plan should account for scenarios such as loss of SCADA visibility, manipulation of control systems, loss of communications, compromised employee credentials, ransomware, inability to process customer payments, loss of access to operational data, or suspicious changes to treatment processes.

EPA provides “rip and run” Incident Action Checklists designed specifically to help water and wastewater utilities prepare for, respond to, and recover from cybersecurity incidents.

For community water systems serving more than 3,300 people, federal law also requires risk and resilience assessments and emergency response planning under Section 1433 of the Safe Drinking Water Act, as amended by America’s Water Infrastructure Act. Those emergency plans must incorporate the findings of the system’s risk and resilience assessment and address physical security and cybersecurity.

But compliance should be the starting point—not the finish line.

Cybersecurity Is Also a Budget Conversation

One of the greatest mistakes municipal governments can make is identifying cybersecurity deficiencies without creating a realistic path to correct them.

Public works departments cannot implement improvements without resources.

If an assessment identifies obsolete equipment, unsupported operating systems, insecure remote access, inadequate network segmentation, insufficient backups, or a need for monitoring, those findings should be incorporated into the municipality’s operational and capital planning.

Not everything has to happen in one budget year. Prioritize improvements according to their potential consequences.

Ask: If this system were compromised tomorrow, what could affect our ability to safely provide water or wastewater services?

Start there.

Preparedness Matters More Than Perfection

No municipality can eliminate cyber risk completely.

The objective is resilience.

Can you detect something unusual? Can you isolate affected equipment? Can operators continue critical functions? Can you communicate with the public? Can you quickly reach the right external resources? Can you restore systems safely? And can municipal leaders make informed decisions under pressure?

Those capabilities can dramatically change the outcome of an incident.

Municipal water and wastewater systems are among the most important pieces of infrastructure local government operates. Protecting them requires cooperation between public works, IT professionals, vendors, emergency management, municipal administrators, elected officials, insurers, state partners, and federal agencies.

Cybersecurity cannot belong exclusively to the IT department or the water superintendent.

It has to become part of how the entire municipality thinks about continuity and public safety.

The next cyber incident affecting the water sector may target a large metropolitan utility—or it may begin with an exposed device at a small community water plant.

Municipal leaders cannot control who attempts to attack their systems.

They can control how difficult they make those systems to compromise—and how prepared their community will be if an attacker succeeds.

Resources for Municipal Water and Wastewater Leaders

EPA maintains cybersecurity planning, assessment, incident response, and emergency planning resources specifically for drinking water and wastewater systems.

EPA Cybersecurity for the Water Sector

EPA Cybersecurity Planning and Top Cyber Actions

EPA Risk and Resilience Assessment and Emergency Response Planning Resources

EPA Incident Action Checklists for Water Utilities

CISA’s July 2026 Advisory on Threats to U.S. Water and Wastewater Facilities

Tags cybersecurity, governance, local-government, security, technology, water, water-threat, water-treatment

Governance & Funding Public Safety (Police, Fire, EMS)

CJIS 6.0: Governance for Law Enforcement Leaders

Post author By Elisabeth Dubois
Post date June 23, 2026
No Comments on CJIS 6.0: Governance for Law Enforcement Leaders

Imagine waking up to a 3:00 AM phone call that instantly makes your blood run cold. It isn’t an officer-involved shooting or a pileup on the interstate—it’s worse. The dispatcher on the line tells you the entire Computer-Aided Dispatch (CAD) system has gone black. Out on the streets, officers are suddenly flying blind, unable to run plates, verify active warrants, or know if the suspect they are pulling over is armed and dangerous. Back at the station, every computer screen goes dark and snaps back on with a terrifying message: hackers have locked down all your files. They are demanding a $1 million ransom in 24 hours, or they will leak the home addresses of your officers, names of your undercover informants, and domestic abuse victims onto the dark web.

For generations, a police chief’s job description was clear-cut: fight crime, protect the community, build public trust, and make sure officers make it home safe at the end of their shift. Today, that entire landscape has been fundamentally altered. In a post-George Floyd era marked by intense public scrutiny, systemic staffing shortages, and heightened anti-police sentiment, the pressure on law enforcement executives is at an all-time high.

While protecting lives on the street remains the top priority, managing these compounding real-world challenges means that ignoring digital threats is no longer just a blind spot—it is a recipe for disaster. Modern chiefs and sheriffs can no longer act solely as tactical commanders; they must realize they are now the gatekeepers of massive, highly sensitive digital networks where a single breach can instantly shatter fragile community trust and compromise the physical safety of their personnel.

With the rollout of the FBI’s Criminal Justice Information Services (CJIS) Security Policy Version 6.0 (slated for full enforcement by October 1, 2027), cybersecurity is no longer an “IT issue” that can be blindly delegated. It is now a critical operational risk. If an agency fails to comply, the consequences are devastating: the FBI can completely cut off their access to vital criminal databases, freeze their federal grants, and strip away key agency partnerships. Beyond the administrative fallout, non-compliance invites catastrophic data breaches, ruined investigations, and massive civil or criminal liabilities for leadership.

Why Law Enforcement is a Prime Target

Law enforcement agencies are no longer just accidental targets caught in broad cyber nets—they are being intentionally hunted. To a sophisticated hacker, a police department is a digital goldmine. The networks maintained by local and state agencies house a concentrated treasure trove of highly sensitive, unredacted data: Social Security numbers, biometric records, active warrants, open homicide files, and the true identities of confidential informants.

Cybercriminals have realized that weaponizing this specific information against public safety infrastructure yields immense leverage. If a bank gets hacked, money is lost; if a police department gets hacked, lives are immediately put in jeopardy. This extreme pressure makes law enforcement agencies highly attractive targets for extortion.

The Critical Risks to the Command

When leadership treats cybersecurity as a secondary priority, they open the door to three devastating structural risks:

Total Operational Paralysis

Cyber criminals deliberately strike police departments because they know law enforcement cannot afford a single minute of downtime. When hackers successfully breach a network, they move fast—state and local government sectors face an overwhelming 98% data encryption rate during successful ransomware attacks.

If your Records Management System (RMS) or CAD system is suddenly locked behind an unbreakable encryption key, your agency plunges into the dark ages. Dispatchers are forced to use pen and paper, response times plummet, and officers on the street lose the ability to pull up critical hazards before entering a scene.

The Expanding Attack Surface

The modern patrol officer is a walking network of connected technology. Between the mobile data terminal (MDT) bolted into the cruiser, body-worn cameras, department-issued smartphones, automated license plate readers (ALPRs), and field tablets, the “attack surface” of a single precinct has exploded exponentially.

Every single one of these endpoints is a potential doorway into your core server room. Cybercriminals don’t need to crack your central firewall if they can exploit an unpatched vulnerability on a single officer’s tablet. Across all sectors, unpatched software vulnerabilities remain the number-one gateway for attackers, triggering 32% of all successful ransomware breaches.

Double Extortion and the Collapse of Trust

The playbook for modern cybercrime has evolved past simple data locking. Today, groups practice “double extortion.” First, they quietly clone and steal (exfiltrate) your entire database; only then do they deploy the ransomware to lock your screens.

For a police chief, this is the ultimate nightmare. Even if you manage to restore your systems from backups without paying a dime, the hackers still hold your data hostage. They will threaten to publish unredacted active wiretaps, sealed juvenile records, or undercover officer identities on public forums.

Worse yet, in today’s highly charged social climate, cybercriminals are actively weaponizing officers’ home addresses, internal affairs files, and disciplinary records. Dumping this information online doesn’t just destroy morale—it puts officers and their families directly in the crossfire. In a post-George Floyd era marked by intense scrutiny and heightened anti-police sentiment, a data leak of personal addresses transforms a digital breach into a terrifying physical threat, exposing an officer’s spouse and children to targeted harassment or worse. The moment that data hits the internet, ongoing criminal prosecutions are permanently compromised, informant networks evaporate, and decades of hard-earned community trust vanish overnight.

The CJIS Shift: Beyond the Checklist

Historically, many agencies treated CJIS compliance as a “point-in-time” chore—filling out a questionnaire, checking a few boxes, and putting it away until the next audit.

CJIS 6.0 completely dismantles that lazy approach. The FBI has overhauled and mapped the entire policy directly to the National Institute of Standards and Technology (NIST) SP 800-53 Moderate Baseline. This alignment forces a complete cultural pivot away from periodic “annual checkups” and straight toward continuous risk management and continuous governance.

Under this framework, law enforcement leaders must command four critical pillars of modern compliance:

Stronger Identity and Access Controls: Security parameters have advanced beyond simple password enforcement. Agencies must now verify exactly who an employee is before granting access, manage accounts tightly from their first day to their last, and have the power to instantly lock down a user’s account the second suspicious activity is detected.
Expanded Auditing and Evidence: The days of simply telling an auditor “yes, our systems are safe” are over. Under CJIS 6.0, you have to prove it. Agencies must show digital receipts, logs, and actual system data to demonstrate that security rules are actively running, regularly checked, and updated when threats change.
Formalized Leadership Governance: True security isn’t achieved by just making an IT technician watch a compliance video. The new rules place the responsibility squarely on leadership. Chiefs and sheriffs must explicitly define who is responsible for what, actively oversee security operations, and sign off on the department’s digital safety strategy.
Continuous Risk Tracking: Instead of checking for security gaps once every few years before an audit, departments must now maintain a rolling, real-time list of their digital vulnerabilities. You are required to create an active game plan that tracks exactly how and when you will fix security flaws, showing constant progress over time.

To achieve this baseline, chiefs and sheriffs must urgently enforce three non-negotiable operational requirements:

1. Phishing-Resistant Multi-Factor Authentication (MFA)

The days of relying on simple passwords or easily intercepted text-message codes are officially over. The new rules mandate a much tougher form of multi-factor authentication (MFA) whenever anyone accesses sensitive criminal justice data, especially from a cruiser or a remote location. To keep things moving fast for officers in the field without cutting corners on security, departments are switching to fingerprint scanning, smart cards, or physical USB security keys (like FIDO2 tokens). These tools cannot be bypassed by hackers trying to trick an officer or spam their phone with login approvals.

2. Maximum-Strength Data Encryption (FIPS 140-3 Encryption)

Information flying through the air over cellular networks or public Wi-Fi is incredibly easy for bad actors to intercept. To stop this, the updated rules require agencies to completely phase out older, weaker security methods. Any data moving outside the secure walls of your station must be scrambled using the government’s latest gold standard of protection: FIPS 140-3 encryption. Think of it as an uncrackable digital armored car for your data while it travels from the street to your servers.

3. Isolated Network Segmentation and Physical Security

Great digital firewalls mean nothing if someone can physically walk right up to your computers or if a hacker can slip in through a weak link on the municipality’s network. First, the new policy requires departments to completely separate police data from general municipal data (like the water department or village/town/city/county traffic). If a hacker hits the municipal hall, a digital wall prevents them from jumping over to your police records. Second, the physical rules are strictly enforced: server rooms must be locked down, entryways monitored by cameras 24/7, and any outside technician or contractor stepping inside must clear a full fingerprint-backed background check.

The High Cost of Non-Compliance

For a police chief, ignoring these requirements carries severe operational and political penalties:

Risk Category	Immediate Impact	Long-Term Consequence
Sanctions & Disconnection	The FBI or state CJIS systems agency can cut off access to NCIC (National Crime Information Center) and Nlets.	Officers are left blind during roadside stops, unable to run plates, check warrants, or verify firearms.
Financial Extortion	Ransomware recovery costs average hundreds of thousands of dollars in remediation, even if the ransom is paid	Local tax dollars are diverted from community policing and equipment into emergency IT restoration.
Legal Liabilities	Exposure of sensitive data (like officer records or domestic abuse victim info) triggers devastating civil lawsuits.	Decades of built-up community trust vanish overnight under the weight of negligence headlines.

Why Leadership Cannot Simply “Outsource” the Problem

It is common for municipal leaders and police chiefs to pass the buck, saying, “I have a great IT director,” or “We hire a trusted tech vendor to handle all of that.”

While the actual technical work belongs to the tech experts, the ultimate accountability rests squarely on the shoulders of agency leadership. Under CJIS 6.0, the rules explicitly state that chiefs and sheriffs must personally own their agency’s cybersecurity strategy. You must be able to prove to auditors that you are actively tracking your department’s digital risks and making measurable progress to fix them.

When a compliance audit fails, or a catastrophic data breach occurs, the public, the media, and the municipal board aren’t going to call the network administrator to the podium for answers—they are going to demand answers from the Chief.

An Action Plan for Law Enforcement Leaders

Steering an agency through this high-risk digital landscape requires more than just acknowledging the threat; it demands an active, disciplined strategy from the top down. Chiefs and sheriffs can use the following roadmap to protect their networks, shield their personnel, and maintain absolute CJIS compliance:

Map Your Agency’s Total Data Footprint:

Phase 1: The Critical Prerequisite.

You cannot protect what you do not know exists. Leadership must order a comprehensive audit to document exactly how sensitive criminal justice data enters, moves through, and leaves the department. Track every single destination—whether that data lives on a cruiser’s mobile data terminal, a cloud-based records system, a detective’s field tablet, or a desktop at the main precinct. If data is flowing through an unmapped channel, it is an open invitation for a breach.

2. Enforce Leadership-Led Tech Briefings:

Phase 2: Monthly Mandate.

Stop treating the IT department or your third-party technology vendor like an isolated island. Establish a recurring monthly briefing to actively review your security posture. Avoid asking vague, passive questions like “Are we safe?” Tech teams will usually say yes. Instead, ask targeted, specific questions that demand proof:

“Can we pull up audit-ready evidence of our MFA compliance right now?”
“When was our last critical software patch cycle completed?”
“Do we have any unpatched vulnerabilities older than 30 days?”

3. Instill a Culture of Security Awareness:

Phase 3: Continuous Operation.

The most advanced firewall in the world can be bypassed by a single employee clicking a bad link. Security is a continuous human obligation, not a yearly classroom chore. Ensure that every single employee, dispatcher, records clerk, and outside contractor undergoes a comprehensive fingerprint-based background check and completes CJIS security awareness training within six months of their hire date. Follow this up with engaging, mandatory annual refreshers and regular, unannounced internal phishing tests to keep the entire command sharp.

4. Operationalize Your Incident Response:

Phase 4: High-Priority Planning

When a cyberattack hits, confusion is your greatest enemy. Do not wait for a crisis to figure out your chain of command. Implement a formalized, written Cyber Incident Response Plan that explicitly outlines who does what when systems go dark. Under CJIS regulations, certain data breaches must be reported to state and federal authorities within a strict window of discovery. Regularly run tabletop exercises with your leadership team so everyone knows how to isolate systems, notify authorities, and keep emergency operations moving without panic.

The Bottom Line: Cybersecurity is no longer an administrative footnote. It is a foundational element of public safety. A department’s frontline defense is determined just as much by its firewall configurations and access privileges as it is by the tactical gear in its cruisers. Leading an agency requires protecting the data of the citizens who trust you—and the officers who rely on it to come home safe.

Tags chiefsofpolice, cybersecurity, governance, law-enforcement, local-government, police, technology

Governance & Funding

Cybersecurity Budgets Shouldn’t Be a Black Box

Post author By Donald Hester
Post date June 12, 2026
No Comments on Cybersecurity Budgets Shouldn’t Be a Black Box

When local officials review the annual budget, they routinely make decisions involving millions of taxpayer dollars. They debate staffing levels, infrastructure projects, pension obligations, public safety priorities, and capital improvements. These decisions often involve weighing competing priorities and determining how much risk the organization is willing to accept. Then they arrive at the cybersecurity budget.

Too often, what they see is a single line item buried somewhere within Information Technology.

Cybersecurity: $1,500,000

What exactly does that mean?

Is the organization investing in prevention or merely reacting to incidents? Are critical systems adequately protected? Are emergency response capabilities sufficient? Is the municipality able to recover quickly from a ransomware attack? Most importantly, how can elected officials determine whether the proposed expenditures align with the organization’s cyber risk tolerance? The honest answer is that they often cannot.

This creates a significant governance challenge. Local officials have a fiduciary duty to protect public assets, ensure continuity of services, and maintain public trust. In today’s digital environment, that responsibility includes cybersecurity. As the Local Government Officials Guide to Cybersecurity notes, cybersecurity is no longer simply an IT issue—it is a strategic, enterprise-level risk that requires leadership engagement.

Yet many governing bodies are expected to approve cybersecurity budgets without a meaningful way to understand how those expenditures reduce organizational risk.

The result is predictable. Some organizations underinvest because decision-makers cannot see the connection between spending and risk reduction. Others overspend in areas that may not represent their greatest vulnerabilities. Still others make decisions reactively, increasing funding only after experiencing a major incident. There is a better approach.

Using NIST CSF 2.0 as a Budget Framework

The National Institute of Standards and Technology (NIST) Cybersecurity Framework 2.0 provides a practical structure that helps local governments translate cybersecurity spending into governance language. Its six core functions are not technical product categories; they are high-level objectives for cyber resilience. Rather than debating specific technologies, cybersecurity activities can be organized around six conceptually straightforward objectives:

Govern
Identify
Protect
Detect
Respond
Recover

These functions provide a common language that bridges the gap between technical professionals and governing bodies.

Most elected officials do not need to understand the differences between endpoint detection platforms, security information and event management tools, or intrusion prevention systems. However, they do understand questions such as:

Are we effectively detecting cyberattacks?
Can we respond quickly enough to minimize damage?
Do we have the ability to recover critical services after a disruption?
Are we investing appropriately in governance and risk management?

Those are governance discussions.

Connecting Spending to Risk

Imagine that, alongside the proposed budget, the governing body received a cybersecurity assessment aligned with the NIST Cybersecurity Framework. The assessment might indicate that the organization demonstrates relatively strong capabilities in Protect and Recover, moderate maturity in Govern and Identify, but significant gaps in Detect and Respond. Suddenly, the conversation changes.

Instead of asking, “Why do you need another cybersecurity tool?” officials can ask:

“Our assessment shows that our ability to detect malicious activity is weak. How does this proposed investment improve that capability?”

The discussion shifts from technology purchases to risk management. Current expenditures, proposed expenditures, and assessment results can all be aligned under the six NIST functions. Decision-makers gain visibility into where resources are being allocated and whether those investments address areas of greatest concern. This allows governing bodies to exercise one of their most important responsibilities: setting organizational risk appetite.

Defining Risk Appetite

No organization can eliminate cyber risk entirely. Just as local governments accept certain financial, operational, and legal risks in pursuit of their mission, they must also determine what level of cyber risk they are willing to tolerate.

That determination belongs to leadership. Technical staff can explain vulnerabilities and recommend mitigation strategies. Auditors and assessors can provide independent evaluations of current capabilities. However, elected officials ultimately decide whether the residual risk is acceptable based on community priorities, available resources, and competing obligations.

The challenge is that these decisions require understandable information. A single cybersecurity line item does not provide that information. A budget structured around the six NIST objectives does.

From Technical Details to Governance Discussions

Consider two different budget presentations. The first includes line items for firewalls, endpoint detection software, log management platforms, and threat intelligence subscriptions. Typically in a single line item, like the one above. The second shows:

NIST Function	Risk Rating	Current Spending	Proposed Spending
Govern	Moderate	$75,000	$100,000
Identify	Moderate	$125,000	$150,000
Protect	Low	$500,000	$525,000
Detect	High	$150,000	$325,000
Respond	High	$100,000	$250,000
Recover	Moderate	$200,000	$225,000

Which presentation is more useful to a city council member, county supervisor, or special district board? The answer is obvious. The second presentation enables leaders to understand where risks exist, how resources are being allocated, and whether proposed expenditures align with the organization’s stated risk tolerance. It elevates cybersecurity from an operational discussion to a strategic one.

Building Better Governance

The NIST Cybersecurity Framework was never intended to be just a technical resource. It provides a structure for understanding and managing cybersecurity risk across the enterprise. By aligning cybersecurity expenditures with the six NIST CSF 2.0 functions, local governments can transform budget discussions into meaningful governance conversations.

Officials gain the ability to:

See how cybersecurity investments address material risks.
Understand the relationship between spending and organizational resilience.
Prioritize funding based on independent assessments.
Establish and communicate risk appetite.
Exercise effective oversight without becoming technical experts.

In short, they gain the information necessary to fulfill their fiduciary responsibilities. Cybersecurity should never be a black box. Local government leaders deserve clear, actionable information that helps them govern wisely, steward public resources responsibly, and strengthen the resilience of the communities they serve. If cybersecurity is truly an enterprise risk, as we increasingly recognize it to be, then our budgets should reflect that reality.

Perhaps it is time to stop asking, “How much are we spending on cybersecurity?” And instead begin asking, “What risks are we reducing, and are we investing where it matters most?”

Help is on the Way

The Local Government Cybersecurity Alliance (LGCA) is currently developing a whitepaper that explores this concept in greater depth, providing practical guidance for local governments seeking to align cybersecurity budgets with the NIST Cybersecurity Framework 2.0. The goal is to equip elected officials, executives, finance officers, and cybersecurity leaders with a common language for discussing cyber risk, prioritizing investments, and making informed, risk-based decisions. By connecting assessment results to budget allocations, local governments can move beyond viewing cybersecurity as a technical expense and begin managing it as the enterprise risk it truly is. We believe this approach has the potential to transform cybersecurity budgeting from an opaque line item into a transparent governance tool that strengthens resilience, accountability, and public trust.

Tags budgeting, budgets, cyber-security, cybersecurity, governance, local-government, security, technology

Governance & Funding

Why “Silent Cyber” Should Alarm Local Government

Post author By Elisabeth Dubois
Post date June 9, 2026
No Comments on Why “Silent Cyber” Should Alarm Local Government

The phrase “cyber risk” often conjures images of corporate data breaches or national espionage. But for municipalities, counties, and local agencies, the threat is far more immediate and complex—especially when considering Silent Cyber.

As local governments digitize records, automate critical infrastructure, and manage massive databases of sensitive resident information, they become prime targets for attackers. However, a major risk lurks not just in the network, but in the fine print of your existing insurance policies.

What is Silent Cyber for a Municipality?

Silent Cyber, or non-affirmative cyber risk, is the danger that a major cyber event—like a ransomware attack or a system breach—could trigger unexpected and massive claims under your municipality’s traditional insurance policies, such as:

General Liability
Commercial Property
Public Officials & Law Enforcement Liability

These policies were not originally written to address digital threats. They are “silent” on the issue, meaning they neither explicitly cover nor explicitly exclude losses caused by a cyber incident. This ambiguity can lead to an unexpected loss for the insurer (if they have to pay a claim they didn’t price for) or a crippling coverage gap for the municipality (if the claim is denied).

Real-World Scenarios for Local Government

For a city or town, a cyber attack is not just about stolen data; it’s about the disruption of essential public services.

Policy Type	Cyber-Triggered Event	Potential Silent Cyber Loss
Property/Equipment	Ransomware infects the Industrial Control System (ICS) managing the water treatment plant, causing mechanical failure and physical damage to pumps.	Physical damage to equipment and extended business interruption/loss of utility service income, covered under a policy not priced for cyber risk.
General Liability	A malicious hack causes the municipal traffic light control system to fail catastrophically, leading to a major vehicle collision and subsequent bodily injury claims.	Third-party bodily injury and property damage liability claims caused by the digital disruption of physical infrastructure.
D&O Liability	A major data breach exposes resident tax and voter records, leading to a class-action lawsuit and an investigation into the Town Board/City Council for failure to maintain adequate security protocols.	Litigation and defense costs covered by a Public Officials/ Law Enforcement policy that didn’t factor in cyber risk aggregation.

Historically, the ambiguous wording may have worked in the municipality’s favor. Today, regulators are demanding clarity, and insurers are introducing explicit cyber exclusions to avoid these unforeseen payouts.

Eliminating Ambiguity

As local governments operate on limited budgets, relying on traditional policies to “silently” cover a modern cyber catastrophe is a gamble your residents can’t afford.

Here are the critical steps your administration should take right now:

Stop Relying on Silence: Understand that the days of assuming coverage from general policies are ending. New, clearer exclusions are rapidly being introduced to your insurance forms.
Conduct a Full Policy Audit: Work with your risk manager and broker to review every liability and property policy. Identify the specific cyber exclusions (or lack thereof). Where possible, aim for language that is affirmative—it clearly states what is covered and what is excluded.
Invest in Dedicated Cyber Insurance: A comprehensive, standalone Cyber Insurance Policy is the only way to reliably cover first-party losses unique to municipalities:
- Ransomware Response: Cost of ransom negotiation, forensic IT, and decryption.
- Public Notification: Mandated costs for notifying thousands of affected residents after a breach of PII (Personally Identifiable Information).
- System Restoration: Costs for rebuilding and restoring municipal data and computer systems.

Cybersecurity is no longer just an IT issue; it is a fundamental public safety and fiscal responsibility. By actively addressing “silent cyber,” local government leaders ensure that when the inevitable digital crisis occurs, the city’s financial resilience and ability to serve its citizens are not compromised by an insurance dispute.

Tags budgeting, cyber-security, cybersecurity, governance, local-government, silent cyber, technology

Governance & Funding

Cybersecurity is Financial Risk: The Hidden Million-Dollar Price Tag of Hacking Local Governments

Post author By Elisabeth Dubois
Post date June 2, 2026
No Comments on Cybersecurity is Financial Risk: The Hidden Million-Dollar Price Tag of Hacking Local Governments

When a cyberattack hits a local government, the price tag goes far beyond ransom demands and new computers. It triggers a financial tsunami of hidden costs that divert taxpayer money from vital public services for years. These aren’t just IT budget line items; they are existential threats to a municipality’s financial stability and ability to serve its citizens.

1. Direct Recovery Costs

The first wave of financial devastation hits during the frantic, high-priced effort to claw back control of municipal systems.

Emergency Procurement and Consultant Fees: When systems go dark, normal competitive bidding processes are thrown out the window. Municipalities are forced to hire specialized incident response firms and forensic investigators on an emergency basis, paying premium, last-minute rates to stop the attack, find the root cause, and clean systems.
System Rebuild and Replacement: Local governments frequently rely on decades-old, vulnerable infrastructure. Cyber insurance rarely covers the full cost of an upgrade. An attack often forces a massive, unplanned leap into modern infrastructure—costing millions more than any planned capital improvement project.
- Case in Point: The 2018 Atlanta ransomware attack cost the city an estimated $17 million to recover—a sum equivalent to funding the city’s entire Parks and Recreation budget for a full year. One single breach effectively erased twelve months of community development.

2. Long-Term Financial Damage

The financial markets treat cyber vulnerability as a systemic operational failure, driving up the cost of a municipality’s future operations and debt.

Credit Rating Downgrades: Rating agencies like S&P Global and Moody’s view a severe cyberattack as a symptom of weak governance and operational instability. A major breach can trigger a direct downgrade of a municipality’s credit rating.
Increased Borrowing Costs: A lower credit rating—or even the public reputation of being digitally vulnerable—makes a municipality a high-risk borrower. When the municipality issues municipal bonds to fund critical infrastructure (like roads, water treatment plants, or schools), it is forced to offer higher interest rates to attract investors.
- A seemingly minor 0.5% increase in a bond’s interest rate translates into millions of dollars in additional interest payments over a 20- or 30-year term. That is pure capital coming out of the community’s treasury forever.
The Cyber Insurance Impact: The insurance market has turned its back on soft targets. Because public entities are viewed as high-risk, local governments face a brutal insurance landscape:
- Skyrocketing premiums paired with slashed coverage limits.
- Strict, non-negotiable security mandates (like mandatory multi-factor authentication or EDR) that underfunded municipalities can’t afford to implement.
- The looming threat of non-renewal leaves the municipality entirely exposed.

3. Operational and Reputational Costs

Some of the most damaging costs are non-financial, yet they have a profound effect on governance and citizen life.

Massive Productivity Losses: Municipal staff are idled, unable to perform basic functions like processing permits, managing utility billing, or accessing court records. The municipality continues to pay salaries while operations grind to a total halt.
Legal and Regulatory Fines: If the attack involved a data breach, the municipality may face regulatory fines from state or federal agencies (especially if health or law enforcement data was involved). They also face the potential for class-action lawsuits from affected citizens whose Personally Identifiable Information (PII) was exposed.
Erosion of Public Trust: When citizens can’t pay their water bill, apply for a license, or receive timely emergency services due to a hack, public confidence in the government plummets. This can hurt everything from voter turnout to bond measure support and the morale of the government workforce.

The true cost of a municipal cyberattack is measured by what the community is forced to abandon. Every dollar handed to a ransomware hacker, an emergency IT consultant, or a bond investor is a dollar stolen from parks, paved streets, public safety, and schools.

Cybersecurity is no longer an IT issue—it is the single most critical form of municipal fiscal risk management.

Tags cyber-security, cybersecurity, governance, local-government, technology

Basics & Actionable Steps Governance & Funding

You Paid For The Lock — Now USE IT!

Post author By Eudora Fleischman
Post date March 19, 2026
No Comments on You Paid For The Lock — Now USE IT!

The Gap Between Owning & Fully “Implemented” Cyber Tooling You Already Own

You fought for the budget. You built the business case, presented the risk landscape to leadership, justified every line item, and won cybersecurity funding. New tools were purchased — Identity and Access Management, advanced EDR/XDR, SIEM and more. Boxes checked. Audit requirements are satisfied. A genuine win.

But here is the uncomfortable question nobody asks in the post-purchase debrief: did you actually fully implement them?

Not install. Not license. Implement — fully configured, integrated into your architecture, with every feature activated, monitored and tested. Because there is a dangerous gap between owning a security tool and deriving security from it. And that gap is exactly where attackers live.

Only 14%

of organizations are confident they have the people and skills required to meet their cybersecurity needs today — WEF Global Cybersecurity Outlook 2025

The Stryker Wake-Up Call

On March 11, 2026, medical technology giant Stryker suffered a devastating cyberattack that wiped data from thousands of employee and personal devices across 79 offices worldwide. The attackers — an Iran-linked group — did not deploy malware. They did not exploit a zero-day vulnerability. They simply obtained high-privilege administrative credentials and weaponized Microsoft Intune’s Remote Wipe feature, a legitimate IT management tool built for lost or stolen device recovery, to factory-reset tens of thousands of enrolled devices simultaneously.

The lesson is not that Intune is dangerous. The lesson is that privileged access was not properly governed, identity boundaries between on-premises and cloud environments were not enforced, and monitoring either did not exist or did not trigger fast enough. All of these are configuration failures in tools organizations already owned.

The attackers did not break in through a sophisticated exploit. They walked through a door left open by an incomplete implementation.

The Preparedness Gap Is Real — and Growing

The Stryker attack is not an anomaly. It is a symptom of an industry-wide crisis that the World Economic Forum’s (WEF) Global Cybersecurity Outlook 2025 has quantified and it is sobering.

72%

of organizations report that cyber risks increased in the past year — WEF Global Cybersecurity Outlook 2025

2 in 3

organizations report moderate-to-critical cybersecurity skills gaps, lacking the talent needed to meet their security requirements — WEF Global Cybersecurity Outlook 2025

54%

of large organizations cite third-party and supply chain risk management as their biggest barrier to achieving cyber resilience — WEF Global Cybersecurity Outlook 2025

35%

of small organizations believe their cyber resilience is inadequate — a proportion that has increased sevenfold since 2022 — WEF Global Cybersecurity Outlook 2025

These numbers describe an industry buying security and not implementing it. Organizations are acquiring the tools, but the talent, architecture, and operational discipline needed to extract full value from those investments is not keeping pace. The result is a fleet of half-deployed, partially configured tools that create a false sense of security while leaving real gaps wide open.

The Agentic AI Threat Multiplier

Attackers are not waiting for organizations to catch up. Generative AI is reshaping the cybercrime landscape at an accelerating pace and the gap between offense and defense is widening.

47%

of organizations cite the advance of adversarial AI capabilities — including AI-enhanced phishing, malware development and deepfakes — as their primary GenAI cybersecurity concern — WEF 2025

66%

of organizations believe AI will have the most significant impact on cybersecurity in the next 12 months, yet only 37% have processes in place to assess the security of AI tools before deployment — WEF 2025

In an Agentic AI attack scenario where AI autonomously chains together reconnaissance, credential harvesting, lateral movement and execution — a monolithic, single-vendor security stack is a structural liability. If the attacker understands your provider’s architecture better than you do, and your tools are not fully configured, they will find the path of least resistance.

This is not hypothetical. It is the architecture of the Stryker attack, translated into the AI era.

Do You Have the Talent to Use What You Bought?

Before the next purchase order is signed, every security leader, technical and executive alike, should answer these questions honestly:

Do we have in-house expertise to fully configure and operationalize the features in our existing tools?
Was our tool selection driven by a holistic architecture strategy, or were tools purchased reactively to satisfy an audit requirement?
Are all features within our EDR/XDR, IAM, and SIEM platforms fully activated, integrated, and effectively monitored?
Do we have unified, normalized logging across every layer of our technology stack feeding a well-configured and monitored dashboard?
Is every vendor connection to our environment governed by Zero Trust principles — remote browser isolation, VPN-less access, and Just-In-Time privileged access with approval notification chains configured?

If the honest answer to any of these is ‘no’ or ‘I’m not sure,’ you are not alone — but you are exposed.

A Layered, Heterogeneous Defense: The Architecture That Holds

A monolithic, single-vendor solution may be cost-effective and operationally convenient. But in an Agentic AI threat environment, it is a single point of architectural failure. A breach that understands one vendor’s toolset can traverse your entire environment.

A heterogeneous, layered defense, built intentionally, implemented fully, and integrated across every layer of your stack is a fundamentally different proposition for an attacker. When one protective layer is compromised, the next one holds. The following architecture has proven itself in real-world attack scenarios:

External Perimeter

SASE and next-generation firewall with full north-south traffic decryption and inspection and integrated real time defense
Advanced API gateways for all internet-facing applications with bot detection and agentic AI defense capabilities
All vendor and third-party remote access governed exclusively through remote browser isolation and VPN-less Zero Trust Network Access (ZTNA)

Internal Network

Switch-to-switch encryption across internal network segments
Micro-segmentation with east-west firewall inspection, full traffic decryption, and XDR/API integration with network admission control policies
Patch panel and port-level monitoring via MAC device admission control with logging and firewall integration feeding XDR

Endpoint

EDR/XDR deployed with all features fully activated
Consider stacking heterogeneous endpoint agents from different vendors — if one provider’s agent is compromised or bypassed, a second independent layer remains active

Identity and Privileged Access

Isolate privileged identities: on-premises admins must not carry high-privilege roles in Microsoft 365 or Entra ID — a critical lesson from the Stryker attack
Deploy Entra Private Access for Domain Controllers, extending Conditional Access and MFA requirements to sensitive Active Directory operations including LDAP and Kerberos
Implement Just-In-Time (JIT) access with approval workflows for all privileged identity management (PIM) accounts
Replace manual service account passwords with Active Directory Group Managed Service Accounts (gMSAs)
Rotate the KRBTGT password at minimum twice per year; in a breach scenario, rotate immediately — do not wait
Restrict all Domain Controller network access; ensure DCs cannot directly reach the internet
Audit and enforce strict anomaly monitoring across all security logs

Cloud Security

Conduct cloud security posture reviews frequently — cloud providers release new security features continuously; newly available controls should be assessed and implemented as a priority, not deferred
Consider disabling Password Hash Sync to keep credential validation on-premises through pass-through authentication or federation
All Saas tenant entry points should be isolated to just your agency IP block, with access for remote users only via browser based isolation and ZTNA solutions and fronted by advanced application gateways or proxies

A layered, heterogeneous defense does not require unlimited budget. It requires deliberate architecture and full implementation of the tools you already own.

How to Close the Configuration Gap Without Starting Over

1. Request a Free Implementation Assessment From Your Vendors

Most enterprise security vendors will conduct a complimentary implementation health check if asked directly. They will identify misconfigured features, unused capabilities, and integration gaps. Many will also provide staff education sessions at no additional cost. This is one of the highest-ROI actions available to any security team and it costs nothing but time.

2. Consider an MSP With Cybersecurity Depth

If in-house talent is the constraint — and the WEF data confirms it is for the majority of organizations — a Managed Security Service Provider (MSSP) with genuine cybersecurity staff, 24/7 monitoring capabilities, and a contractual cyber retainer for incident response is not a cost; it is a force multiplier. The right MSSP partner helps you operationalize the tools you already own and ensures that someone is watching when your team cannot be.

3. Build a Unified Visibility Layer

Every device, every endpoint, every cloud workload, every network segment should feed normalized logs into a centralized, well-configured SIEM or XDR dashboard. Visibility gaps are where attackers operate undetected. Unified logging is not glamorous, but it is foundational.

4. Prioritize Identity Above All Else

The Stryker attack was an identity attack. The WEF report confirms that identity theft has become the top personal cyber risk for both CISOs and CEOs in 2025. If you can only harden one area this quarter, harden identity: implement JIT access, enforce MFA everywhere without exception, isolate privileged accounts, and audit every administrative role in both your on-premises and cloud environments.

5. Review Attack Anatomy Regularly

An easy way to have a leg up on all attacks is to regularly review the anatomy of attacks. This is a free and easy way to identify gaps within your architecture and alerting. You can implement additional custom alerts from the indicators of compromise you review in attack anatomy, address configuration updates and hardening, and review with your team or your Managed Service Provider. Attack review should be part of your day-to-day operations. You cannot protect against what you do not understand. Also, you cannot harden architecture if you have not operationalized architecture review.

The Bottom Line

The cybersecurity industry has a spending problem masquerading as a security problem. Organizations are acquiring tools at scale while the skills gap required to effectively implement them grows faster than the workforce can fill it. The result is a fleet of expensive, partially deployed technology that creates compliance confidence without creating actual resilience.

The WEF Global Cybersecurity Outlook 2025 reports that 49% of public-sector organizations lack the talent to meet their cybersecurity goals — an increase of 33% in a single year. The private sector is not immune.

The answer is not more tools. It is full implementation of the tools you already own, a deliberate layered heterogeneous architecture designed to survive a breach of any single component, and the operational talent — whether in-house or through a trusted partner — to run it.

You paid for the lock.

Now use it.

About the Author

Eudora Fleischman | Infrastructure Architect & Retired CISO Eudora Fleischman is the Infrastructure Architect and Retired with over 31 years of experience in infrastructure architecture, cybersecurity, governance risk, and disaster recovery management and serves as an Advising Member of the Local Government Cybersecurity Alliance.

Sources

World Economic Forum — Global Cybersecurity Outlook 2025 (January 2025, in collaboration with Accenture)

Stryker SEC Filing & Incident Reports, March 2026

Tags ai, budgeting, cyber-security, cybersecurity, governance, local-government, security, technology

Emerging Tech & AI Governance & Funding

Seven Phases of AI Governance for Local Government

Post author By Eudora Fleischman
Post date March 6, 2026
No Comments on Seven Phases of AI Governance for Local Government

A Practical Framework for Agencies Beginning Their AI Journey

Government Technology | AI Governance | Public Sector

AI is already inside your agency. Vendors are embedding it into the software you use every day — permitting systems, HR platforms, records management tools, and public safety software. In most cases, no one asked. It arrived as a feature update, buried in a release note, with no governance framework in place to receive it.

At the same time, regulations are moving fast. California’s Civil Rights Council implemented binding AI employment regulations in October 2025. Dozens of additional state and local AI laws are in various stages of development. The agencies that will navigate this landscape successfully are not the ones that adopt AI fastest — they are the ones that build the right governance foundations first.

What follows is a condensed version of a practical, phased governance framework developed from real public-sector cybersecurity and advisory experience. It is designed for the city manager, IT director, HR leader, or department head who needs a clear, easy to understand, actionable path — not an academic exercise.

The Core Principle: Governance Before Tools

The most common mistake organizations make is adopting AI tools before establishing the governance infrastructure to use them responsibly. Policies written after deployment are reactive. Data classified after AI ingestion is too late. Vendor contracts negotiated without AI governance language leave agencies legally exposed.

This framework is sequenced deliberately. Each phase builds on the one before it. The goal is not to slow down AI adoption — it is to make adoption sustainable, defensible, and aligned with the communities these agencies serve.

Phase 1: Establish Governance Authority First

Before any technical work begins, designate who is responsible for AI governance in your organization. This may be a named AI Governance Officer, an AI Steering Committee, or a hybrid model. The specific structure matters less than the fact that accountability exists. Without it, governance activities have no center of gravity, decisions stall, and there is no clear point of contact when regulators come asking. Establish a recurring executive reporting cadence from day one — even if early reports are brief. AI governance without executive visibility and informing elected officials is governance in name only.

Phase 2: Data Governance and Classification Must Come First

AI cannot operate safely or compliantly without governed, classified data. Before activating any AI feature, conduct a thorough assessment of where your data lives, how it flows, who owns it, what regulatory requirements apply to it, and which data might be inadvertently exposed to AI systems. Define sensitivity labels — public, internal, confidential, restricted — and educate every employee on how to handle data accordingly. This is the foundation. Everything else depends on it.

Phase 3: Start with Problems, Not Tools

Conduct structured interviews with department leaders to identify real operational challenges that AI might address. For each candidate use case, assess feasibility, operational impact, risks, staffing implications, and full cost — including ongoing expenses for in-house staff or MSP consulting support. Compile the results into an AI Use Case Roadmap, have leadership formally prioritize it, and use it to drive every subsequent resource and tooling decision. Agencies that skip this step end up with duplicate tools, misaligned spending, and AI deployments that solve problems no one had, and, in the end, without a goal. Funding and resources become wasted efforts.

Phase 4: Build Policy and Vendor Governance Around Your Use Cases

Only after your data governance is established and your use cases are defined should you develop formal AI governance policies. Policies written in the abstract tend to be ignored. Policies built around real, approved use cases get used. Alongside internal policy, embed AI governance requirements language directly into vendor contracts — including mandatory disclosure of sub-processors and data residency/sovereignty, notification obligations if their AI systems are attacked or compromised, resiliency, recovery and liability terms for discriminatory or harmful AI outputs. Agencies that assume vendor contracts handle these issues are almost always wrong.

Phase 5: Organizational Change Management Is Not Optional

The most technically sound AI governance framework will fail if employees do not understand it, trust it, or know what it requires of them. Develop a layered internal communications strategy tailored to different audiences — frontline staff, supervisors, and executives each need different messages. Pair it with role-appropriate training that covers data handling requirements, how to recognize and report unexpected AI behavior, and what the governance policies actually require in practice. Change management is not soft. In local government, it is often the difference between a governance program that lives on paper and one that actually changes behavior.

Phase 6: Regulatory Compliance Requires a Monitoring Function, Not a One-Time Review

A single legal review at the time of AI deployment is not sufficient. California’s AI regulatory landscape alone — covering employment discrimination, automated decision systems, data privacy, and civil rights — is evolving continuously. Assign ongoing responsibility for regulatory monitoring, maintain an internal AI regulatory tracker, conduct periodic reviews with qualified legal counsel, and build civil rights and algorithmic fairness impact assessments into your use case evaluation process. The cost of falling behind is not theoretical: it includes legal exposure, audit findings, loss of public trust, and — in systems that affect critical services — real harm to real people.

Phase 7: Build AI-Specific Incident Response Before You Need It

Traditional cybersecurity incident response plans were not designed for AI-specific failure modes: model poisoning, data corruption through adversarial inputs, rogue agentic AI behavior, or model collapse. Develop AI-specific runbooks that define what normal AI behavior looks like, how anomalies are detected, what triggers a shutdown or rollback of AI agent access and actions, and what the communication obligations are internally and externally. Complement this with red-team and blue-team exercises and annual tabletop simulations that involve IT, legal, HR, and leadership together. The organizations that respond well to AI incidents are the ones that have rehearsed them.

This Is a Governance Model, Not a Checklist

What distinguishes this framework from a deployment checklist is its cyclical nature. Each phase requires a scheduled review cadence, named accountability, and ongoing adaptation. Monthly executive reporting, quarterly roadmap reviews, annual red team exercises, and full governance audits — these are not nice-to-haves. They are what separates a governance program that holds up under regulatory scrutiny from one that looks good on paper until something goes wrong.

Local government agencies are under real pressure to demonstrate responsible AI stewardship to their constituents, their oversight bodies, and their regulators. The agencies that build this foundation now — before the pressure becomes a crisis — will be far better positioned to capture the genuine operational benefits that AI can deliver, while protecting the public trust that makes those agencies effective in the first place.

Responsible AI adoption is not primarily a technology challenge. It is a governance, accountability, and culture challenge. Technology is the easy part.

About the Author Eudora Fleischman – Managing Director of Artemis Technology Advisors and Retired Infrastructure and Cybersecurity Manager & CISO. Eudora is a government cybersecurity and AI governance advisor with 31 years of technical and leadership experience and 21 of those years working with public-sector organizations on cybersecurity GRC, data security, regulatory compliance, organizational resilience, disaster recovery and responsible technology adoption.

Tags ai, artificial-intelligence, cyber-security, cybersecurity, governance, local-government, public sector, technology

Governance & Funding

A Cyber Insurance Briefing for Elected Leaders

Post author By Elisabeth Dubois
Post date October 30, 2025
No Comments on A Cyber Insurance Briefing for Elected Leaders

In today’s digital landscape, a local government’s data—from citizen records and utility operations to internal communications—is a prime target for cybercriminals. A single ransomware attack or data breach can cripple services, drain resources, and erode public trust.

While strong cybersecurity measures are your first line of defense, Cyber Insurance acts as a crucial safety net, helping your municipality manage the massive financial fallout of a successful attack.

If your village, town, city, county, or public utility is considering or renewing a policy, here is a look at what local governments can expect, the vital differences between what is typically covered versus what isn’t, and the critical questions you must ask your municipality and your broker.

The Six Critical Questions Elected Leaders Must Answer

As an elected leader, your top priority is the continuity of public service and the protection of taxpayer funds. Cyber risk is no longer an “IT problem”—it is a governance and financial crisis waiting to happen. Before you sign a policy, your governing body must confront these fundamental questions about your municipality’s readiness and resilience.

Focus Area	The Core Question for the Governing Body	The Bottom Line for Taxpayers
Operational Impact	If our critical digital systems (email, payroll, utility controls) were locked down by an attack tomorrow, what essential public service would fail immediately?	We must know which services—from 911 dispatch to water quality monitoring—are immediately jeopardized. If the lights go out, your response must be immediate.
Downtime Tolerance	How many hours can our municipality sustain a complete disruption of public records and digital services before the damage to the community becomes irreversible?	Every hour of downtime multiplies the cost, halts services, and directly erodes public trust. This defines your operational breaking point.
Financial Cost	What is the documented, unbudgeted cost our municipality would face for recovery, separate from any ransom demand?	The true expense is in forensic investigation, legal fees, and system restoration. You need a transparent figure on the financial exposure, which often runs into the millions.
Budget Resilience	Do we have an explicitly dedicated and sufficient reserve fund that can absorb an unbudgeted recovery cost of at least $250,000?	Most local governments do not. This question forces a review of whether a cyber event would force painful cuts to essential public programs.
Risk Strategy	*Are we relying only* on our technology defenses, or have we established a financial safety net for when those defenses inevitably fail?**	Technology is a tool, but cyber insurance is the risk transfer mechanism. It is a layer of resilience for a modern public entity.
Governance & Accountability	Who is the executive-level owner of cyber risk in this municipality, and is a tested incident response plan in place?	Cyber risk is a leadership issue. Insurance helps ensure that the highest levels of governance have a clear, tested plan to guide the community through the chaos of a breach.

What is Typically INCLUDED in a Policy?

Cyber policies generally cover three distinct areas:

Coverage Area	What is Covered?	Examples
First-Party (Breach Response)	Who pays the costs for us to recover from the attack?	Fees for forensic investigators, legal counsel, system restoration, and paying cyber extortion (ransom) demands (subject to limits).
Third-Party (Liability to Others)	Who pays if we get sued or fined for exposing citizen data?	Defense costs, settlements, damages from citizen lawsuits, regulatory fines, and costs for notifying all affected individuals.
E-Crime & Financial Loss	Who pays if a criminal tricks an employee into sending public funds to a fraudulent account?	Financial loss from Computer Fraud, Funds Transfer Fraud (e.g., fraudulent vendor invoices), and Social Engineering Fraud.

What is EXCLUDED?

Exclusions can be policy-specific, but there are several common areas where cyber insurance will not provide coverage:

Failure to Maintain Minimum Security: Claims can be denied if the breach is traced to your municipality failing to implement a required security measure, such as an unpatched server or not enforcing Multi-Factor Authentication (MFA).
Property Damage or Bodily Injury: Physical damage caused by a cyber event (e.g., a hack on a utility system causing a physical failure) may be covered by a General Liability or Property policy, not the cyber policy, unless specifically added.
Acts of War or Terrorism: Losses stemming from hostilities or state-sponsored cyber-attacks are often explicitly excluded.
Cost of Hardware/Software Upgrades: The policy will pay to restore systems, but generally not for the cost of upgrading to newer technology.
Known Vulnerabilities: If a claim arises from a vulnerability your municipality was aware of before the policy inception date, coverage may be denied.

Where Are the Hidden Traps?

The real risk often lies in the fine print. You need to look beyond the general coverage summary and scrutinize the endorsements and warranties within the policy. These items can act as “trap doors” that allow insurers to legally deny a claim.

1. The “Failure to Maintain Security” Clause

This is the most common and dangerous reason for denial today. Many policies contain a clause that makes coverage conditional upon maintaining specific security controls, most notably Multi-Factor Authentication (MFA).

The Warranty Trap: If your municipality warrants (guarantees) in the application that 100% of privileged users or remote access points use MFA, and an attack happens through an account that didn’t have it, the insurer may reject the entire claim based on a breach of warranty.
The No-MFA Endorsement: A particularly insidious version of this is the MFA Exclusion Endorsement. This endorsement is added to a policy to state that the insurer will not pay any claim that arises from or is attributed to the lack of MFA on specific systems (e.g., all email, remote access, or privileged accounts).
- What does the No-MFA Endorsement mean for our paid policy? It means you could pay your full premium for a $1 million policy, but if the claim is traced back to a compromised employee email account that lacked MFA, the insurer can legally reject the entire claim. You have the policy, but no coverage for your greatest risk.

Action: Ensure your policy defines required security controls clearly and realistically. If an MFA endorsement is present, treat it as a policy killer unless you are 100% certain every covered access point complies.

2. The Retroactive Date

All policies have a date—the Retroactive Date—before which the insurer will not cover any incident, even if the loss is discovered during the policy period. If a hacker has been in your system for six months and you purchase a policy today, you may not be covered for the full extent of the intrusion. This prevents coverage for “silent data breaches.”

3. The Exclusion for Software/Hardware “Betterment”

After an attack, forensic experts often recommend system upgrades (e.g., replacing an old server or moving to cloud services). Insurers will only pay for the cost of restoring the old system, not the cost of making it “better” or new. Your municipality must be prepared to budget for these betterment costs, which can be substantial and unexpected.

The Six Critical Questions to Ask Your Broker

Cyber insurance should be a true safety net, not a piece of paper. Use these questions to determine if your policy provides the coverage, expertise, and support your community needs.

1. What does the policy cover? What specific security controls are mandatory, and what happens if we fail to maintain them?

Demand a clear list of mandatory controls (like MFA for all remote access). Clarify if non-compliance with a warranty will void the entire policy or only exclude payment for claims related to that specific missing control.

2. What is the annual premium and deductible, and how does this fit our budget risk?

Understand the financial spread: Premiums for municipalities often range from $600 to over $100,000 annually, with deductibles from $1,000 to $100,000. Ensure these costs are sustainable and that the deductible is affordable in a crisis.

3. Does the insurer have demonstrated experience specifically with the public sector?

Government entities have unique challenges: tight budgets, complex regulatory compliance (like state breach laws), and critical services. An experienced insurer will offer tailored coverage that respects these public sector obligations.

**4. What loss prevention and risk mitigation services are provided in addition to the coverage?**

Look for high-value extras included in the policy: access to incident response hotlines, employee training platforms, vulnerability scans, and tabletop exercises. These proactive services reduce risk and can help lower future premiums.

5. If we report a breach, what is the guaranteed response time, and who is our dedicated contact?

Day to day or in a crisis, you need human support, not an automated line. Ask for a commitment to a response within hours, not days. Confirm you will have access to a cyber specialist or dedicated claims manager or 24/7 breach response team.

6. What is the likely impact of making a claim on our future premiums and coverage availability?

Ask for candor: Will premiums spike after a claim, or will the insurer consider non-renewal? Understanding the long-term relationship ensures you are not penalized for using the safety net you paid for.

Tags ai, cyber insurance, cyber-security, cybersecurity, governance, local-government, security, technology

Basics & Actionable Steps Governance & Funding Press Release

Announcing the Local Government Officials Guide to Cybersecurity

Post author By Elisabeth Dubois
Post date October 21, 2025
No Comments on Announcing the Local Government Officials Guide to Cybersecurity

We are thrilled to announce the official publication of a critical new resource: the Local Government Officials Guide to Cybersecurity (LGOGC)!

This project was developed by the Local Government Cybersecurity Alliance (LGCA) specifically to empower elected and appointed officials—from supervisors and council members to city managers and agency heads—to effectively navigate the increasingly complex world of cyber risk.

Moving Beyond the Technical Jargon

Cybersecurity is not just an IT department problem; it is an enterprise-wide, whole-of-government issue that impacts finance, legal compliance, emergency services, and public trust.

The LGOGC cuts through technical jargon to focus on what matters most to community leaders: governance, accountability, and resilience. This guide was truly built by and for local government professionals, ensuring every concept is practical and immediately relevant to your fiduciary duty to protect the systems that serve your communities.

LGOGC Cybersecurity Guide (October 2025)Download

What the Guide Will Help You Achieve

The LGOGC provides a clear, actionable framework to help local leaders translate responsibility into practical action. Inside, you’ll find guidance to:

Integrate cybersecurity into your strategic and budget planning.
Strengthen oversight and reporting mechanisms.
Align your efforts with nationally recognized frameworks, such as NIST CSF 2.0.
Build a culture of cyber resilience that spans all departments and elected offices.

Download and Share Your Feedback

We believe that making cybersecurity governance as natural and necessary as financial oversight is achievable in every county, city, town, village, and district. This guide is a huge step toward that goal.

Download the Local Government Officials Guide to Cybersecurity (LGOGC) now.

We invite your feedback! Tell us how your jurisdiction is addressing these challenges and what resources would be most valuable to you next in our community forum or white paper.

Tags ai, artificial-intelligence, cyber-security, cybersecurity, governance, local-government, security, technology

Basics & Actionable Steps

Relevant Laws & Compliance Checklists: What Local Governments Need to Know

Post author By Elisabeth Dubois
Post date August 27, 2025
No Comments on Relevant Laws & Compliance Checklists: What Local Governments Need to Know

Cybersecurity laws and regulations are evolving rapidly. For local governments, staying compliant isn’t just about checking boxes—it’s about protecting public trust, ensuring operational continuity, and avoiding costly legal exposure. As the threat landscape changes, so do the legal obligations that govern how municipalities handle data, respond to incidents, and manage third-party risks.

Why Legal Review Matters

Boards and senior leaders must be regularly updated on both existing laws and proposed legislation that could impact current practices. This includes federal mandates, state-specific statutes, and sector-based requirements. Engaging your general counsel or external legal advisors is essential to ensure that your organization remains compliant and prepared.

Legal teams can help:

Interpret new regulations and assess their applicability.
Identify gaps in current policies and procedures.
Draft or revise internal compliance checklists.
Advise on risk exposure and liability mitigation.

Federal Laws to Watch

Several federal statutes directly affect state and local governments:

Federal Information Security Modernization Act (FISMA): Now applies more stringently to local governments, requiring robust protections for information systems and timely incident reporting.
Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA): Requires organizations in critical infrastructure sectors—including many municipal services—to report cyber incidents within 72 hours and ransomware payments within 24 hours.
State and Local Government Cybersecurity Act of 2021: Provides federal support through grants, cooperative agreements, and training programs.
Federal Rotational Cyber Workforce Program Act of 2021: Encourages talent development and resource sharing across government agencies.

These laws are designed to improve coordination, transparency, and resilience across public sector entities.

State-Level Regulations

Cybersecurity legislation continues to evolve rapidly across the United States. In 2025, 48 states and Puerto Rico introduced or considered more than 500 bills or resolutions related to cybersecurity. These laws reflect growing concerns about ransomware, data breaches, and the need for stronger digital infrastructure in government.

Key Trends and Examples

New York: Updated procurement laws now require endpoint device purchases to align with the NIST Cybersecurity Framework. As of 2025/2026, there is a .gov web domain mandate, incident reporting requirements, and a training mandate for local governments.
Arkansas: Mandated the Division of Information Systems to maintain cybersecurity policies aligned with state standards.
Idaho: Requires all state agencies to implement multifactor authentication and maintain cybersecurity best practices.
Mississippi: Established limits on cyber liability claims and introduced new requirements for cybersecurity insurance.
Montana: Expanded its workforce development program to include cybersecurity roles beyond entry-level analysts.
Hawaii: Adopted resolutions to build cybersecurity education pipelines and strengthen its innovation economy.

These laws vary widely in scope and applicability. Some focus on procurement, others on workforce development, insurance, or incident reporting. Local governments must consult legal counsel to determine which laws apply and how to comply.

Compliance Checklists and Internal Oversight

To manage compliance effectively, local governments should maintain internal checklists that cover:

Data classification and retention policies.
Incident response and reporting protocols.
Vendor risk assessments and contract language.
Employee training and awareness programs.
Access controls and audit trails.
Insurance coverage and legal disclosures.

These checklists should be reviewed and updated regularly, especially when new laws are enacted or existing ones are amended. Legal advisors can help tailor these tools to your organization’s structure, risk profile, and regulatory environment.

Cybersecurity compliance is not one-size-fits-all. Each state may have different laws, and local governments must navigate these requirements with care. Legal review should be a standing agenda item for boards and councils, and compliance checklists should be living documents that evolve with the law.

If your organization hasn’t conducted a legal review recently, now is the time. Engage your legal team, update your checklists, and ensure that your cybersecurity practices are aligned with current and emerging regulations.

Tags cyber-security, cybersecurity, security, technology

Why Water Systems Are Attractive Targets

Cybersecurity Has to Reach the Operational Technology Environment

Seven Actions Municipalities Can Take Now

Questions Elected Officials Should Be Asking

Put Cybersecurity Into the Emergency Response Plan

Cybersecurity Is Also a Budget Conversation

Preparedness Matters More Than Perfection

Resources for Municipal Water and Wastewater Leaders

Why Law Enforcement is a Prime Target

The Critical Risks to the Command

The CJIS Shift: Beyond the Checklist

The High Cost of Non-Compliance

Why Leadership Cannot Simply “Outsource” the Problem

An Action Plan for Law Enforcement Leaders

What is Silent Cyber for a Municipality?

Real-World Scenarios for Local Government

Eliminating Ambiguity

1. Direct Recovery Costs

2. Long-Term Financial Damage

3. Operational and Reputational Costs

The Stryker Wake-Up Call

The Preparedness Gap Is Real — and Growing

The Agentic AI Threat Multiplier

Do You Have the Talent to Use What You Bought?

A Layered, Heterogeneous Defense: The Architecture That Holds

External Perimeter

Internal Network

Endpoint

Identity and Privileged Access

Cloud Security

How to Close the Configuration Gap Without Starting Over

1. Request a Free Implementation Assessment From Your Vendors

2. Consider an MSP With Cybersecurity Depth

3. Build a Unified Visibility Layer

4. Prioritize Identity Above All Else

5. Review Attack Anatomy Regularly

The Bottom Line

The Six Critical Questions Elected Leaders Must Answer

What is Typically INCLUDED in a Policy?

What is EXCLUDED?

Where Are the Hidden Traps?

1. The “Failure to Maintain Security” Clause

2. The Retroactive Date

3. The Exclusion for Software/Hardware “Betterment”

The Six Critical Questions to Ask Your Broker

1. What does the policy cover? What specific security controls are mandatory, and what happens if we fail to maintain them?

2. What is the annual premium and deductible, and how does this fit our budget risk?

3. Does the insurer have demonstrated experience specifically with the public sector?

4. What loss prevention and risk mitigation services are provided in addition to the coverage?

5. If we report a breach, what is the guaranteed response time, and who is our dedicated contact?

6. What is the likely impact of making a claim on our future premiums and coverage availability?

Moving Beyond the Technical Jargon

What the Guide Will Help You Achieve

Download and Share Your Feedback

Why Legal Review Matters

Federal Laws to Watch

State-Level Regulations

Key Trends and Examples

Compliance Checklists and Internal Oversight

Sign In

Register

Reset Password

**4. What loss prevention and risk mitigation services are provided in addition to the coverage?**