jain.com — data centers, connectivity and security, analyzed daily

Tag: water utilities

  • Hack-Back Memo Puts State Hackers Out of Scope, Despite Attacks on 45 Water Systems

    Hack-Back Memo Puts State Hackers Out of Scope, Despite Attacks on 45 Water Systems

    TL;DR · 30-second read

    The Short Version

    The American government will now let approved private companies break into, and even wreck, computers run by foreign criminal hacking gangs. In March, officials said they would not do this.

    Each company must set aside at least $1 million, which it loses if it breaks the rules. Every attack needs written approval from the Justice Department and Homeland Security.

    The catch: hackers working directly for a foreign government are off-limits. That matters because the order came after suspected Iranian attacks on water suppliers in 45 American towns.

    Tom’s Hardware reported that President Donald Trump signed a presidential memorandum on August 12 creating the first US program that lets vetted private companies conduct offensive cyber operations against foreign cybercrime organizations. These include operations that destroy data and systems. Participating firms must post at least $1 million in escrow, which they forfeit if they break program rules. Every operation needs written approval from Department of Justice and Department of Homeland Security officials.

    A National Coordination Center will run the program. Implementation guidance is due within 60 days. The policy reverses public statements administration officials made in March.

    Executive Summary

    The memorandum authorizes two kinds of activity. “Cyber Surveillance Operations” means getting into foreign systems without permission to gather intelligence while staying undetected. “Cyber Effects Operations” means disrupting or destroying those systems and their data. Both large firms and smaller specialists will be eligible. Participants may also sign commercial deals with other private firms and with state and local agencies to receive threat data and propose operations based on it.

    This matters for two reasons. First, it turns offensive cyber activity, long treated as a government monopoly in the US, into something a licensed private sector can do under supervision. Second, its target definition is narrow. A group qualifies as a target unless “clear intelligence exists” that it is part of a foreign government or wholly run at a government’s direction. So the program is aimed at criminal ransomware crews, not at the state-directed actors behind many attacks on physical infrastructure. For operators of water, power and data center infrastructure, that distinction shapes what the program can and cannot do for them.

    The Target Line Runs Straight Through Critical Infrastructure

    The memo arrived after suspected Iranian cyberattacks on water suppliers in 45 US municipalities. It also followed a CISA alert about Iranian hackers targeting programmable logic controllers (PLCs), the small industrial computers that open valves, run pumps and switch equipment at water and energy companies. Yet state-directed hackers fall outside the program’s own definition of a valid target. Private operators could go after a ransomware crew that encrypts a utility’s billing systems. They could not go after a government-run unit tampering with its treatment-plant controllers.

    The line is drawn deliberately. Ransomware crews that operate with a state’s tolerance but not under its formal control stay within scope, a description that fits much of the Russia-based ransomware ecosystem. Once an actor is clearly an arm of a foreign state, the matter stays with government. For utility and industrial security teams, the practical conclusion is that nothing changes for defending operational technology against nation-state intrusion. Segmentation, monitoring and incident response for control systems remain their responsibility. The new program targets the financially motivated threat, not the geopolitical one.

    There is also an ambiguity problem. Eligibility turns on whether “clear intelligence” ties a group to a government, and in practice attribution is often contested and slow. A group judged criminal today may later prove to have state links. That question will matter a great deal to any firm whose operation lands on the wrong side of the line.

    A $1 Million Bond on a Destructive Capability

    The escrow requirement is the program’s main economic control. A minimum of $1 million, forfeited for rule-breaking, is a meaningful commitment for a small specialist firm. Whether it is proportionate to the harm a destructive operation could cause is a separate question. Wiping servers that turn out to be shared with innocent third parties could produce losses well above that figure. The minimum works as a deterrent and an entry filter. It is not obviously a compensation fund.

    The commercial provisions may matter more for the market’s shape. Participants can contract with other private firms and with state and local agencies, receive threat data and propose operations based on it. That creates a potential new service line for security vendors: selling disruption, not just detection. Two background facts point the same way. Congress earmarked $1 billion for offensive cyber operations in last year’s spending bill. Google said in August last year that it was preparing to take part in disruptive actions against cybercriminals. Large platform companies with deep telemetry into criminal infrastructure look like natural participants. Smaller firms may compete on specialized tasks, as the eligibility rules anticipate.

    Escalation, Legal Exposure and a Classified Annex

    DOJ and DHS officials cannot approve operations likely to cause loss of life or amount to an armed attack under international law. The memo does not prohibit such operations outright, however. Approval authority for them sits in a classified annex. Companies weighing participation, and the public, therefore cannot see the full rulebook for the highest-risk cases.

    Personnel face exposure too. Jake Williams, vice president of research and development at Hunter Strategy, told TechCrunch that Americans involved in these operations “could easily be classified as non-uniformed combatants while traveling overseas.” That is a risk that falls on individual employees, not only on their employers, and firms will need to account for it in staffing, travel policy and insurance.

    The speed of the reversal adds uncertainty. In March, Thomas Lind, then a senior adviser at the Office of the National Cyber Director, said the administration had no plans to authorize private offensive operations: “We’re not interested in fighting pirates with pirates.” National Cyber Director Sean Cairncross said the same week that companies running offensive campaigns were not what the administration meant when it asked industry for help. A policy that changed direction within months could change again, which makes long-term investment in offensive capability a harder bet.

    Collateral Risk Is Written Into the Rules

    The memo requires any company that unintentionally hits a US person or a system on US soil to halt operations and notify the government immediately. That clause concedes that operations aimed abroad can land at home. Criminal groups commonly route activity through rented servers and compromised machines owned by unrelated parties. Hosting providers, cloud platforms and data center operators therefore have a direct interest in how approvals weigh that possibility, and in how quickly they would be told if their infrastructure were affected.

    Defenders more broadly face a quieter risk: retaliation. A criminal group whose systems are destroyed by a US firm may not distinguish between that firm and US targets generally. The memo’s safeguards govern how operations are approved. They do not change who absorbs the response.

    Background

    For decades, US law and policy have treated breaking into someone else’s computer as illegal, even when that someone is an attacker. Offensive cyber operations have been reserved for government agencies such as the military and intelligence community. Proposals to let private victims “hack back,” including the Active Cyber Defense Certainty Act introduced in Congress in 2017, never became law. Critics warned of misattribution, collateral damage and escalation.

    Pressure grew as ransomware crews, many operating from jurisdictions beyond the reach of US law enforcement, hit hospitals, pipelines and municipalities. Some large technology firms have already worked with authorities to take down criminal infrastructure, and Google said last year it was preparing to take part in disruptive actions. The August 12 memorandum is the first formal framework for private firms to go further, under federal supervision.

    Sources

    Source: White House authorizes private companies to launch ‘hack-back’ cyberattacks that destroy data and systems, targeting foreign cybercrime organizations. Tom’s Hardware on the August 12 presidential memorandum creating a supervised private offensive cyber program.

  • As CISA Faces a 30% Cut, California Makes AI Cyber Defense of Utilities a State Job

    As CISA Faces a 30% Cut, California Makes AI Cyber Defense of Utilities a State Job

    TL;DR · 30-second read

    The Short Version

    California’s governor announced a plan on August 10 to use artificial intelligence to find and block hackers targeting the systems behind tap water, electricity and emergency phone lines.

    The timing is the story. The federal government has proposed cutting its main cyber defense agency’s budget by about 30 percent, and a monitoring service that small towns used for free for two decades has lost its federal funding and is starting to charge. California is taking on more of that protection itself. It has not yet said how much it will spend.

    On August 10, 2026, California Governor Gavin Newsom announced an AI Cyber Defense Program, which his office describes as first-in-the-nation, according to the announcement published on CA.gov. The Governor directed state agencies to set up the program inside the California Cybersecurity Integration Center (Cal-CSIC), using AI for vulnerability detection, network hardening and incident response; to expand AI-enabled cyber defenses to local governments and critical infrastructure partners; and to designate an AI Cybersecurity Officer in every state agency.

    The Governor’s office tied the move to AI-enabled attacks and to federal pullbacks: a proposed Fiscal Year 2027 cut of roughly $707 million, about 30%, to the Cybersecurity and Infrastructure Security Agency (CISA), the end of federal funding for the Multi-State Information Sharing and Analysis Center (MS-ISAC) in late 2025, and the winding down of the current funding phase of a $1 billion federal state-and-local cyber grant program.

    Executive Summary

    California is building a state-run layer of AI-assisted cyber defense for the systems residents depend on most: water, power, transportation and emergency communications. The program sits in Cal-CSIC, the state’s existing hub for threat intelligence and incident coordination, and extends beyond state agencies to local governments and critical infrastructure operators.

    The significance is less the technology than the division of labor. For two decades, small water districts, counties and cities leaned on free or grant-funded federal services for round-the-clock monitoring and incident help. With those services shrinking or moving to paid models, California is positioning the state as the provider of last resort for AI-era cyber defense.

    What the announcement does not yet include is a budget, a timeline or eligibility rules, so the scale of what the state can actually absorb remains an open question.

    Why Utility Cyber Defense Is Becoming a State Job

    The most consequential directive is not the AI itself but the second item on the list: expanding access to advanced cybersecurity capabilities, including AI-enabled defenses, for local governments and critical infrastructure partners. That commits the state, through Cal-CSIC, to supplying defensive capacity to organizations it does not run: municipal water systems, county networks, and the operators of the power, transportation and emergency communications services that Cal OES Director Caroline Thomas Jacobs named.

    The Governor’s office set this against three federal changes. The proposed FY2027 budget would cut CISA, the federal agency that provides field support, incident response and defensive tools, by roughly $707 million, about 30% below earlier levels. MS-ISAC, which for more than twenty years gave thousands of state, local, Tribal and territorial governments 24/7 monitoring and threat intelligence at no direct cost, lost federal funding in late 2025 and is moving to paid models. And the State and Local Cybersecurity Grant Program, launched with $1 billion under the Bipartisan Infrastructure Law, is nearing the end of its current funding phase. Each of these disproportionately served small jurisdictions, such as a water district with a handful of IT staff that could never run its own round-the-clock security operations center. When that free federal layer thins, those operators can pay, go without, or lean on the state. California is choosing to make the third option real.

    Two caveats keep this in proportion. The CISA figure is a budget proposal; Congress sets appropriations, and it has advanced bipartisan legislation to keep the grant program authorized. And the state has attached no dollar figure to its own program, so how much of the federal gap it can fill is unknown. The stakes are illustrated by the case federal officials recently flagged in Minnesota: a suspected Iran-linked operation touching more than 30 municipal water utilities in a single campaign, exactly the kind of many-small-targets pattern where limited local defenses matter most.

    What AI-Enabled Defense Means in Practice

    The program names three functions. Vulnerability detection means finding weaknesses, such as unpatched software or exposed services, before attackers do. Network hardening means closing unnecessary openings and tightening configurations. Incident response means containing a breach and restoring service. AI’s promise across all three is speed and scale: sorting thousands of alerts, scanning large inventories of systems, and flagging anomalies faster than a small team could.

    The Governor’s office grounds the urgency in disclosures by leading AI developers that advanced systems independently carried out sophisticated cyber operations in controlled testing, and in adversaries using AI to attack more cheaply and effectively. The logic follows: if the cost of attacking falls, defenders relying on manual processes fall behind, and automation is the natural counter. The announcement does not, however, name the tools, vendors or performance measures the state will use.

    Utilities are also harder to protect than office networks. Water treatment and the power grid run on operational technology, the industrial controllers that open valves, dose chemicals and switch circuits. Much of it is old and cannot be scanned or patched aggressively without risking the very service it runs. Whether the program reaches into those control systems or stays on the business-network side will largely determine how much protection it delivers to the services it names.

    Governance First: An AI Cyber Officer in Every Agency

    The third directive, an AI Cybersecurity Officer in every state agency, creates a named point of accountability across government. It aligns with Cal-Secure 2.0, the state’s 2026 cybersecurity roadmap, which already prioritizes workforce, coordination and wider use of AI-enabled security tools.

    It also completes a two-sided posture. Through Senate Bill 53, signed in 2025, the largest frontier AI developers must publish their safety frameworks and report certain critical safety incidents to the state. With this program, California is both regulating the developers whose models could be misused and deploying AI defensively. The state has not said whether incident reports filed under SB 53 will inform Cal-CSIC’s defensive work, which would be the most direct way to connect the two.

    What It Means for Data Center and Utility Operators

    Data centers, fiber networks and cloud facilities in California depend on the same grid and water systems the program targets, so a compromise upstream is an outage risk downstream. If private operators qualify as critical infrastructure partners, access to state threat intelligence and AI-enabled tooling could be a meaningful resource, particularly for smaller regional providers without large security teams.

    Until eligibility and terms are published, though, prudent planning assumes nothing. Local governments that relied on MS-ISAC’s no-cost services should budget for paid alternatives rather than count on state coverage arriving on a particular date. For security vendors, the program signals state demand for AI-driven detection and response, though procurement details have not been released.

    Background

    California has built out a state cyber apparatus over several years: Cal-CSIC as its threat intelligence and coordination hub, the Cal-Secure statewide cybersecurity roadmap (updated to Cal-Secure 2.0 in 2026), executive orders on artificial intelligence in 2023 and 2026, and SB 53, the Transparency in Frontier Artificial Intelligence Act, signed in 2025.

    Nationally, state and local cyber defense has leaned heavily on federal support: CISA’s field staff, incident response and tools; MS-ISAC’s no-cost monitoring for thousands of governments; and the $1 billion State and Local Cybersecurity Grant Program. All three are now shrinking, changing or facing uncertain funding, which shifts more of the burden to states and the local operators of water, power and communications systems.

    Sources

    Source: Governor Newsom announces new AI cyber defense program to protect California’s critical infrastructure, the Office of the Governor of California’s August 10, 2026 announcement of the AI Cyber Defense Program and related directives.

  • Minnesota’s 30+ Water Systems Show Why a CISA OT Mandate Alone Won’t Protect Utilities

    Minnesota’s 30+ Water Systems Show Why a CISA OT Mandate Alone Won’t Protect Utilities

    TL;DR · 30-second read

    The Short Version

    Hackers have tampered with the computers that run water and sewage plants in at least seven American states. In Minnesota alone, more than 30 local water systems were targeted, allegedly by attackers working for Iran.

    A group of industrial security firms and plant operators wants the federal government to stop issuing warnings and start requiring basic protections. The catch: the rule they want would only cover federal government sites. Small-town water utilities would still rely on a federal grant program that Congress has not yet renewed.

    The Operational Technology Cybersecurity Coalition (OTCC) has called on the Cybersecurity and Infrastructure Security Agency (CISA) to issue a Binding Operational Directive setting baseline security controls for operational technology, the systems that run physical equipment, across federal civilian facilities. Industrial Cyber reported the statement on August 3, 2026. It follows the FBI’s confirmation, as of July 30, that water and wastewater utilities in at least seven states had reported cyber incidents, some of which disrupted operations. The worst impact was in Minnesota, where alleged Iranian-affiliated state actors targeted more than 30 water systems.

    The coalition also asked Congress to reauthorize and fund the State and Local Cybersecurity Grant Program, support Andrew McClure as director of the Department of Energy’s Office of Cybersecurity, Energy Security, and Emergency Response (CESER), and pass long-term authority for the Cybersecurity Information Sharing Act of 2015, which is set to expire at the end of September.

    Executive Summary

    The OTCC is asking Washington to move from advisories to requirements on industrial cybersecurity. Its headline request, an OT-focused Binding Operational Directive from CISA, would oblige federal civilian agencies to put fundamental controls on the systems that operate pumps, valves, power equipment and building infrastructure.

    The detail that matters most is one the coalition states itself: such a directive would not have applied to the Minnesota water utilities. OTCC executive director Tatyana Bolton argues its value lies in the demand signal it sends to the private sector. The coalition’s three requests to Congress are the measures that actually reach local utilities. They cover grant money for state and local defenders, energy-sector security leadership, and the legal basis for companies to share threat data with the government.

    For anyone who owns or depends on critical infrastructure, including energy, water and the data centers that draw on both, the practical question is whether those congressional levers move before the information-sharing law lapses at the end of September.

    A Mandate That Stops at the Federal Fence Line

    A Binding Operational Directive is a compulsory instruction from CISA to federal civilian executive branch agencies. It is not a regulation on industry. Bolton says so plainly: an OT directive “only applies to FCEB entities, and the water utilities in Minnesota would not have been required to implement the requirements.” The incident that prompted the call therefore sits outside the reach of the call’s headline remedy. More than 30 targeted water systems in one state, and reported incidents in at least seven, all involve utilities that are mostly local, not federal.

    The coalition’s argument for the directive is indirect. Federal requirements tend to become the reference point that vendors build to, insurers ask about and state regulators borrow. Bolton cites a 2024 National Security Agency directive covering OT on National Security Systems, which required security, reporting and inventory measures, as evidence that such a baseline is “not a novel or unimplementable idea.” That precedent supports the feasibility claim. Whether a federal-only directive changes behaviour at a small municipal water plant is a separate claim, and the coalition presents it as a signal rather than a mechanism.

    Who is affected, then? Federal civilian agencies would carry the direct compliance burden. The operators under active attack, small utilities with limited security staff, would see change only if the signal travels. That is why the coalition itself describes the directive as insufficient on its own.

    The Levers That Reach Local Utilities

    The requests aimed at Congress do more of the work for the actual victims. The State and Local Cybersecurity Grant Program funds state and local governments, and the coalition frames it bluntly: without it, Congress is “leaving small towns to protect themselves from nation-state actors like Iran.” For a utility serving a few thousand customers, the constraint is usually money and staff, not awareness of best practice. A grant program addresses that constraint. A federal directive does not.

    The Cybersecurity Information Sharing Act of 2015 matters for a different reason. It lets private companies pass technical threat data to the government. That flow is how agencies spot a campaign moving across sectors and warn the next target before it is hit, which is exactly the pattern of an attack wave that reached at least seven states. The coalition warns the US “can no longer rely on short-term extensions” with the authority due to expire at the end of September. A lapse would thin the evidence that the FBI and EPA warnings are built on.

    The request to back Andrew McClure at CESER extends the argument to energy. The Environmental Protection Agency leads on water, but the coalition notes that energy underpins all 16 critical infrastructure sectors, and CESER is responsible for protecting the OT that runs the grid.

    Internet-Exposed Controllers Are Everyone’s Problem

    The FBI and EPA warning centred on hackers targeting internet-connected industrial controllers. These are the small computers that open valves, run pumps and dose treatment chemicals. The same class of equipment runs substations, backup generation, and the chillers and power distribution inside commercial buildings and data centers. Bolton points to “increasing convergence between IT and OT,” meaning office-style networking reaching equipment that was once isolated. That convergence is why a technique proven against water plants is relevant well beyond water.

    For infrastructure operators outside the water sector, the lesson is not that their own facility was hit; nothing reported suggests that. The lesson is that their upstream dependencies, municipal water and the grid, run on controllers of this kind, often operated by organisations with far smaller security budgets than their largest customers.

    Weighing the Coalition’s Case

    The OTCC describes itself as a coalition of OT cybersecurity organizations and owners and operators. Firms that sell OT security stand to benefit from mandates, and readers can weigh the call with that in mind. The substance of the requests is modest, however. The directive covers only the government’s own systems, and the congressional items reauthorize or fund existing programs rather than create new regulatory regimes.

    The assertion that deserves the closest scrutiny is the demand-signal effect, which is plausible but not demonstrated in the statement. The strongest parts of the case are the concrete, dated items: an information-sharing authority with a known expiry, and a grant program whose absence falls hardest on the smallest operators.

    Background

    The Operational Technology Cybersecurity Coalition is an advocacy group of OT cybersecurity organizations and infrastructure owners and operators, led by executive director Tatyana Bolton. CISA, part of the Department of Homeland Security, coordinates national cyber defense and can issue binding directives to federal civilian agencies. For most privately and locally run infrastructure, however, it relies on advisories and voluntary guidance, alongside sector agencies such as the EPA for water and the Department of Energy for power.

    US water and wastewater service is delivered largely by local utilities, many of them small, which operate industrial control systems with limited security staff. Bolton points to repeated warnings that Chinese and Iranian actors have pre-positioned inside critical infrastructure, and to growing IT and OT convergence, as the backdrop to what the coalition calls years of guidance without enough action.

    Sources

    Source: OTCC urges CISA to issue binding OT cybersecurity directive after cyberattacks disrupt water utilities (Industrial Cyber). The OT Cybersecurity Coalition calls for a CISA OT directive and congressional action after attacks on water utilities in at least seven states.

  • NIST’s 3 Water Blueprints Show AI Cooling’s Cyber Risk Starts at Utility Remote Access

    NIST’s 3 Water Blueprints Show AI Cooling’s Cyber Risk Starts at Utility Remote Access

    TL;DR · 30-second read

    The Short Version

    A US government standards agency has published a guide telling water and sewer utilities that their riskiest weak spot is remote access: the ways staff and outside contractors log in from elsewhere to run pumps and treatment equipment.

    More than half of American water systems serve 500 people or fewer and have few staff to defend them.

    This matters beyond your tap. Many of the giant computer buildings behind artificial intelligence use water to keep their machines cool, often supplied by those same local utilities.

    The US National Institute of Standards and Technology (NIST) has published SP 1800-45, Cybersecurity for the Water and Wastewater Sector: Build Architecture, which identifies secure remote access as the immediate cybersecurity priority for water and wastewater utilities, Industrial Cyber reported on June 26. The project, run by NIST’s National Cybersecurity Center of Excellence (NCCoE), offers high-level reference architectures and three example implementations built from commercially available products.

    The three designs cover a traditional on-premises gateway (demonstrated with TDI ConsoleWorks), a cloud-managed access model (StrongDM with Cisco Duo), and encrypted machine-to-machine links between remote sites (Q-Net Security hardware). NIST describes them as product-agnostic demonstrations of capability, not vendor endorsements.

    Executive Summary

    NIST’s new practice guide gives water utilities a concrete starting point for what it calls the most pressing gap in their operational technology (OT), the networks of controllers and sensors that physically run pumps, valves and treatment processes. Utilities have moved from manual, on-site operation to automated and remotely managed systems. That shift improved efficiency but opened two-way paths into equipment that, if misused, could let an attacker manipulate processes or create unsafe conditions.

    The guidance matters to the data center industry because water is an upstream dependency for many facilities that use water-based cooling. A data center can harden its own networks and still depend on a municipal control system it neither owns nor sees into. NIST’s focus on remote access marks where that external dependency is most exposed, and its emphasis on staffing and funding signals that many utilities will struggle to close the gap quickly.

    The guide is also a snapshot of a market decision facing thousands of utilities: build remote-access security in-house, rent it from a cloud provider, or encrypt the links between sites in hardware. Each choice moves risk to a different place, and at least one vendor is already arguing that none of these designs goes far enough.

    Why a Water Security Guide Is a Data Center Story

    A water-cooled data center, especially one that relies on evaporative cooling towers, depends on a steady supply of water at usable pressure and quality. That supply is managed by the local utility’s SCADA (supervisory control and data acquisition) system: servers, programmable logic controllers (PLCs, the small industrial computers that switch pumps and valves) and operator screens spread across a main control station, regional centers and remote pump stations. NIST’s point is that these pieces are held together by remote access, both people logging in from outside and machines at separate pumping stations talking to each other over telecom networks. The guide warns that enabling two-way remote access to operational or safety systems widens the attack surface and could allow malicious actors to manipulate processes or create unsafe conditions.

    Follow that chain downstream and the conclusion in our headline follows. For a facility whose cooling depends on municipal water, the earliest point at which a cyber incident could reach its cooling is not its own chiller plant. It is the utility’s remote-access layer: the vendor login to an operator screen, the cloud-brokered session, or the unencrypted controller traffic between pump stations. NIST’s three blueprints map directly onto those three entry points, which is why they read as a map of inherited risk for anyone siting or operating water-cooled capacity.

    The exposure is uneven. Facilities using air cooling or closed-loop liquid systems draw far less from the municipal supply than those running evaporative towers, and any disruption at a utility would hit hospitals, homes and industry first and just as hard. The practical point is narrower and more useful: for water-dependent sites, the utility’s cyber posture belongs in site selection, resilience planning and supply conversations, alongside drought risk and capacity allocation.

    Utility Size Decides Which Blueprint Is Realistic

    NIST’s own figures show why no single design fits the sector. Very small community water systems, serving between 25 and 500 people, make up more than half of all systems but serve a small fraction of the population. Fewer than 1 percent of utilities are classified as very large, serving more than 100,000 people, yet they supply nearly half of the US population. Larger utilities tend to run dispersed infrastructure with complex SCADA networks and dedicated IT and OT staff. Smaller ones often rely on simpler or fully manual systems, aging hardware, few staff and tight budgets.

    That split drives the choice of architecture. NIST expects larger systems to support in-house deployments, while smaller utilities are likelier to lean on vendor-managed or cloud-based remote access. The consequence is that for a large share of the country’s water systems, security will rest heavily on the terms of a service contract. NIST explicitly warns utilities to check those contracts for encryption, access controls, intrusion detection and vulnerability management. The guide also stresses that adequate staffing and funding are essential to configure and maintain any of these environments, a quiet acknowledgment that the architecture is the easy part.

    Three Architectures, Three Places to Put the Risk

    The first design is the classic industrial pattern: a demilitarized zone (DMZ, a buffer network between the outside world and the control system) guarded by paired firewalls, with a remote access server inside it. Users authenticate with multi-factor authentication over HTTPS, role-based rules limit which SCADA consoles, operator screens and PLCs they can reach, and every session is logged. NIST demonstrated it with TDI ConsoleWorks. It offers the utility the most control and demands the most in-house skill.

    The second moves authentication, authorization and session monitoring to cloud-managed infrastructure. Users sign in with multi-factor authentication, receive an access token, and a security gateway inside the operational network checks that token before allowing a connection. NIST demonstrated this with StrongDM and Cisco Duo. It lowers the management burden, which is why NIST pitches it at smaller utilities, but it shifts part of the trust to the provider.

    The third addresses traffic that no person touches: PLCs and remote terminal units exchanging process data between sites. Here NIST recommends encryption appliances at each network edge that authenticate one another and encrypt data before it leaves. The demonstration used Q-Net Security’s Q-Box hardware to protect Modbus traffic between PLCs. Modbus is a long-established industrial protocol that was not designed with built-in encryption, so this design closes a gap that access controls on human users do not address.

    The Hardware-Isolation Critique, Weighed Fairly

    Mike Carr, field CTO of Xona Systems, agreed that remote access is the water sector’s biggest cybersecurity weakness, but argued that the named products are all software sitting on the same attack surface adversaries already exploit. He called for hardware-enforced protocol isolation that physically separates the user from the critical network, summarised as “You can’t hack what you can’t reach.”

    The critique makes a real point: remote-access gateways are themselves internet-facing targets, and adding controls to an exposed path is not the same as removing the path. Several parts of the claim need testing against the guide itself, though. The third implementation is hardware-based. NIST presents all three as product-agnostic examples rather than recommended products. And NIST treats remote diagnostics and vendor maintenance as operational necessities, while noting that some utilities already choose one-way alarming or on-site work for sensitive tasks. The statement that attacks are seen “in the field every day” comes without incident data. Utilities weighing the argument should ask any vendor, including this one, for evidence that its model preserves the maintenance access they actually need.

    Background

    NIST, part of the US Department of Commerce, publishes widely used cybersecurity frameworks and guidance. Its National Cybersecurity Center of Excellence produces the SP 1800 series of practice guides, which show how commercially available products can be combined to solve specific security problems in a given sector. SP 1800-45 applies that approach to water and wastewater utilities, a critical infrastructure sector made up of thousands of systems that range from tiny rural operators to large metropolitan authorities.

    For the data center industry, water has become a central siting and operating issue as capacity grows for AI and cloud workloads. Facilities that cool with water depend on the reliability of local utilities, which puts utility resilience, including the cybersecurity of utility control systems, alongside power availability and land in data center planning.

    Sources

    Source: NIST SP 1800-45 outlines remote access security as key priority for water, wastewater sector amid expanding OT cyber risks (Industrial Cyber): coverage of NIST’s practice guide on securing remote access to water and wastewater operational technology.

  • Iran-Linked Actor Claims Breach of California Water Utility: What Is Verified?

    Iran-Linked Actor Claims Breach of California Water Utility: What Is Verified?

    A California water utility is investigating a claim by an Iran-linked threat actor that it breached the utility’s systems, according to a June 17, 2026 report from Cybersecurity Dive. As of the report, the intrusion is a claim under investigation — not a confirmed compromise — and the utility has not publicly validated the actor’s assertions.

    Executive Summary

    The report is short on confirmed detail but long on significance: a threat actor publicly associated with Iran has asserted that it compromised a water utility in California, and the utility has opened an inquiry into whether the claim is real. In critical-infrastructure security, that sequence — public breach claim first, verification later — has become a recurring pattern, and it matters regardless of how the investigation resolves.

    Water and wastewater systems sit at the intersection of two uncomfortable facts. They are unambiguously critical infrastructure — a service failure has immediate public-health consequences — and they are, as a sector, among the least-resourced operators of industrial control technology in the United States. That combination makes them attractive targets for state-aligned actors seeking psychological and political impact, whether or not a given claim reflects a genuine operational compromise. For operators of data centers, networks, and other critical facilities, the episode is a reminder that adversary messaging is itself part of the attack, and that the ability to rapidly verify or refute a breach claim is now an operational capability in its own right.

    A Claim Is Not a Breach — and That Distinction Is the Story

    Everything public in this report hinges on the word “probes.” The utility is investigating; it has not confirmed an intrusion, and the actor’s assertion stands unverified. That matters because state-aligned and hacktivist-branded groups have a documented history of exaggerating, recycling, or fabricating claims against high-visibility targets. Publicly claiming a water-system breach generates headlines and anxiety at essentially zero cost to the attacker, whether or not any system was touched.

    At the same time, dismissing such claims outright would be equally unwarranted. Iranian-affiliated actors have previously carried out real, confirmed intrusions against U.S. water utilities — most visibly the late-2023 wave of attacks on internet-exposed Unitronics programmable logic controllers, which defaced operator screens at multiple utilities and prompted advisories from CISA and the water sector’s information-sharing bodies. The honest posture, for readers and for the utility itself, is disciplined agnosticism: treat the claim as unproven, investigate as if it could be true, and communicate what is and is not known.

    Why Water Utilities Keep Appearing in the Crosshairs

    Water systems run on operational technology, or OT — the industrial controllers, sensors, and SCADA (supervisory control and data acquisition) software that open valves, run pumps, and dose chemicals. Much of this equipment was designed decades ago for reliability, not for exposure to a hostile internet, and many of the roughly 50,000 community water systems in the U.S. are small operations without dedicated cybersecurity staff. Remote-access tools bolted on for operator convenience, default credentials, and flat networks between office IT and plant floors are recurring findings across the sector.

    For a state-aligned actor, this asymmetry is the appeal. Even a shallow intrusion — a defaced control screen, exfiltrated documents, a screenshot of an operator interface — can be presented as evidence of reach into an adversary nation’s drinking water, with psychological effect far exceeding the technical sophistication involved. The attacker’s goal is often the announcement as much as the access. That is why federal agencies have repeatedly urged water utilities to remove control systems from the public internet, enforce multifactor authentication, and change default passwords: measures that are basic, but that close precisely the doors these campaigns walk through.

    The Verification Problem Is Now an Operational Cost

    When a breach claim surfaces publicly, the target inherits an urgent, expensive burden: prove or disprove it, fast, under public scrutiny. That requires log retention deep enough to reconstruct weeks or months of access, asset inventories accurate enough to know what “our systems” even means, and forensic readiness in OT environments where taking a controller offline for imaging can interrupt service. Utilities that lack these capabilities face prolonged uncertainty — and prolonged uncertainty, not the intrusion itself, often does the most reputational damage.

    There is a broader lesson here for every critical-infrastructure operator, including the data-center and connectivity industry. Incident response planning has traditionally started at detection; it increasingly needs to start at allegation. The ability to say, credibly and quickly, “we have investigated and here is what we found” depends on investments made long before any claim appears — monitoring of OT networks, segmentation between IT and control systems, and rehearsed communication plans. Those investments are unglamorous, but this episode shows exactly when they pay off.

    Background

    The U.S. water sector comprises tens of thousands of mostly small, locally governed utilities, and it has repeatedly been flagged by federal agencies as a cybersecurity soft spot among the sixteen designated critical-infrastructure sectors. Unlike bulk electric power, water has no binding federal cybersecurity standards regime of comparable reach, leaving practices uneven across systems of very different sizes and budgets. Iranian-affiliated threat activity against the sector is not hypothetical: the 2023 compromises of Unitronics control devices at several U.S. utilities — carried out by actors the U.S. government linked to Iran’s Islamic Revolutionary Guard Corps — demonstrated that opportunistic attacks on exposed water-system equipment do occur, and prompted sector-wide advisories on securing internet-facing controllers. Against that history, public breach claims aimed at water utilities land on well-prepared soil, which is precisely why each new claim demands careful verification rather than reflexive acceptance or dismissal.

    Source: California water utility probes breach claim by Iran-linked actor — Cybersecurity Dive report, June 17, 2026, on a California water utility’s investigation of an unverified breach claim by an Iran-linked threat actor.

  • AI-Assisted Intrusion Attempt on a Mexican Water Utility Marks a New Escalation

    AI-Assisted Intrusion Attempt on a Mexican Water Utility Marks a New Escalation

    Cybersecurity Dive reported on May 7, 2026 that Anthropic’s Claude — one of the most widely used commercial AI models — was used in an attempted compromise of a water utility in Mexico. The report describes an attempted intrusion rather than a confirmed breach, but it places a name-brand AI assistant at the center of an attack on critical infrastructure: the systems that treat and deliver drinking water.

    Few operational details were available at publication — the utility was not named, the attacker was not identified, and the specific role Claude played in the operation was not spelled out in the material available to us.

    Executive Summary

    The reported incident matters less for what happened — an attempt, apparently unsuccessful — than for what it represents. Security researchers have warned for several years that general-purpose AI models would lower the barrier to entry for cyberattacks by helping less-skilled actors with reconnaissance, phishing, and malicious code. A reported attempt against a water utility moves that concern from the abstract to a sector where failure has physical, public-health consequences.

    It also continues a pattern in which AI developers themselves surface the misuse. Anthropic has previously published threat intelligence describing attackers abusing its models, including AI-assisted intrusion campaigns disclosed in 2025. When the tool being misused is a commercial product with usage monitoring, the vendor becomes an unusual new node in the detection chain — one that traditional network defenders never had.

    For infrastructure operators, the practical takeaway is not that AI created a new class of vulnerability, but that it compresses the time and skill needed to exploit the old ones. Water utilities — often small, thinly staffed, and running legacy control systems — are precisely where that compression bites hardest.

    Why Water Utilities Are the Soft Underbelly of Critical Infrastructure

    Water and wastewater systems are among the most fragmented critical-infrastructure sectors anywhere in the world: thousands of operators, many serving small populations on municipal budgets, with cybersecurity often handled part-time or not at all. Their industrial control systems — the SCADA and PLC equipment that opens valves, doses chemicals, and runs pumps (collectively called operational technology, or OT) — were frequently designed decades ago with no assumption of internet exposure. Recent years have brought intrusions at U.S. water authorities and repeated government advisories urging the sector to harden remote access and segment control networks.

    An attempt against a Mexican utility fits that global pattern rather than breaking it. Attackers, whether criminal or state-aligned, probe where defenses are thinnest, and water systems combine high public impact with comparatively low security maturity. The nationality of the target matters less than the target class: if AI-assisted tooling is being pointed at water systems anywhere, operators everywhere should assume they are in scope.

    What “AI-Assisted” Actually Changes for Attackers

    It is worth being precise about what an AI model can and cannot contribute to an intrusion. Models like Claude do not conjure novel exploits out of nothing, and vendors build safeguards intended to refuse plainly malicious requests. What AI demonstrably does is accelerate the unglamorous majority of attack work: researching a target organization, drafting convincing phishing lures, writing and debugging scripts, and triaging technical information at a speed a lone operator could not match. Anthropic’s own prior threat reporting, along with disclosures from other AI vendors, has described attackers using models in exactly these supporting roles — and, in the most serious 2025 disclosures, orchestrating substantial portions of intrusion campaigns with agentic AI tooling.

    The economic effect is a lower skill floor and a higher operational tempo. Attacks that once required a competent team can increasingly be attempted by fewer, less-skilled people. For defenders, that shifts the threat model: the question is no longer whether a sophisticated adversary might target a small utility, but how many unsophisticated ones now can. The reported incident, notably, was an attempt — a reminder that AI assistance does not guarantee success, and that basic controls still decide outcomes.

    The AI Vendor’s Dilemma: Dual-Use Tools and Public Disclosure

    This story also illustrates an emerging norm in which the AI company is both the abused platform and, frequently, the reporting party. A commercial model with centralized usage monitoring gives its vendor visibility that no firewall vendor or ISP has: the attacker’s actual working process. That visibility carries obligations — to detect misuse, disrupt it, and disclose it — and headlines like this one are the cost of transparency. A vendor that publicizes abuse of its own product accepts reputational risk that a silent competitor avoids, which is why disclosure practices deserve encouragement rather than punishment by headline.

    The available reporting does not specify who detected this attempt or how, and that distinction matters. If the vendor caught it, that validates model-level monitoring as a defensive layer. If the utility or a third party caught it, that says more about conventional defenses holding. Either way, the incident will sharpen debate about what AI companies owe critical-infrastructure operators: proactive victim notification, indicator sharing, and coordination with national cyber authorities are all plausibly on the table.

    What Infrastructure Operators Should Take From This

    None of the defensive fundamentals change because an attacker used AI; they simply become less optional. Segmenting IT networks from OT networks, eliminating direct internet exposure of control equipment, enforcing multi-factor authentication on remote access, and monitoring for anomalous activity remain the controls that turn attempts into non-events. What changes is the assumed frequency and polish of attacks: phishing emails get better, reconnaissance gets faster, and the long tail of small utilities that relied on obscurity loses that protection.

    For the broader infrastructure industry — data centers, network operators, and the vendors who serve utilities — the incident reinforces a commercial reality as much as a technical one: demand for OT security services, managed detection, and secure-by-design control systems is being driven by a threat environment that AI is measurably accelerating.

    Background

    Anthropic, founded in 2021 by former OpenAI researchers, develops the Claude family of AI models and has positioned itself around AI safety — including a practice of publicly disclosing misuse of its own products. In 2025 the company published threat intelligence describing attackers using Claude in intrusion campaigns, part of a broader industry reckoning with the dual-use nature of capable AI systems.

    The water sector, meanwhile, has spent years near the top of critical-infrastructure risk assessments. Thousands of small operators run aging industrial control systems on tight budgets, and governments in the U.S. and elsewhere have issued repeated warnings about intrusions targeting water authorities. The convergence of those two storylines — commodity AI capability and a chronically under-defended sector — is the context in which this reported incident lands.

    Source: Anthropic’s Claude used in attempted compromise of Mexican water utility — Cybersecurity Dive report, May 7, 2026, on an AI-assisted intrusion attempt against a water utility in Mexico.