A cybersecurity company called Cyware is teaming up with WaterISAC, the group that helps American water utilities warn each other about hackers.
The goal is simple: when one water system spots an attack, the warning should reach the others fast, including thousands of tiny rural systems with little or no security staff.
Why it matters beyond your tap: many of the huge computer buildings that power artificial intelligence rely on the local water supply to stay cool and to fight fires. If the local water plant is hacked, those buildings are exposed too. No price or timeline was announced.
Cyware announced on Sept. 30, 2026, in a release distributed via PR Newswire, a partnership with WaterISAC, the information-sharing organization for the US water sector. Under the arrangement, WaterISAC will use Cyware’s threat intelligence platform to collect, enrich and distribute cyber threat data and vulnerability alerts to water and wastewater utilities.
WaterISAC said its existing partnership with the National Rural Water Association already lets it serve more than 20,000 of the sector’s smallest utilities, and that Cyware was selected after an evaluation of available platforms. No financial terms, contract length or rollout schedule were disclosed.
Executive Summary
WaterISAC, the hub through which US water utilities, security experts and government partners share threat warnings, is moving its intelligence work onto Cyware’s platform. The stated aim is to replace manual processes for gathering and enriching threat data with automation, so that alerts reach members faster and larger utilities can receive intelligence directly.
The deal matters because the US water sector is extraordinarily fragmented. The release counts more than 50,000 utilities, many of them small, and argues that each one is a potential point of failure. Collective defense, the idea that a threat seen by one member protects all of them, only works if warnings reach the weakest participants in a form they can act on.
For data center operators, the announcement is a reminder that a facility’s physical resilience depends on infrastructure it does not control. Cooling systems that draw on municipal water, and fire-suppression systems fed by the local supply, inherit the cyber posture of whichever utility serves the site.
Why a Water-Sector Deal Belongs on a Data Center Risk Register
Data center resilience planning usually focuses on what sits inside the fence: backup generators, redundant cooling loops, dual fiber paths. Water is often treated as a commodity input. But many facilities, especially those using evaporative or other water-based cooling, draw on the local municipal supply, and building fire-suppression systems commonly depend on it as well. The Cyware release itself lists fire suppression alongside drinking water and sanitation as a core function of water systems.
That dependency runs through operational technology, or OT: the control systems that run pumps, valves, chemical dosing and treatment at a water plant. Cyware’s release states that adversaries targeting OT now move at machine speed. If a utility’s controls are disrupted, pressure and supply can be affected for every customer on that system, including a data center campus. The operational conclusion is that the relevant cyber defender for a site’s water is not a national agency or a large vendor, but one of more than 50,000 local utilities, each with its own level of security staffing and maturity.
For operators and developers, that makes the local utility’s cyber posture a legitimate site-selection and resilience input, weighed alongside on-site water storage and cooling design. It also means that sector-wide efforts like WaterISAC’s affect data center risk indirectly: a better-informed local utility is a more dependable upstream supplier.
The Small-Utility Problem Is the Real Test
The most revealing detail in the announcement is structural. WaterISAC says its partnership with the National Rural Water Association already lets it serve more than 20,000 of the smallest utilities. WaterISAC Executive Director Tom Dobbins described the Cyware platform as helping WaterISAC’s analysts deliver more real-time insights to members and letting the organization extend intelligence directly to larger utilities.
Read together, those statements suggest a tiered model: analysts work in the platform, larger utilities may connect directly, and smaller utilities receive curated output. That is a reasonable design, since a rural system with no dedicated security staff cannot ingest a raw threat feed. But it also means the speed gains Cyware describes will be felt most by larger members and by WaterISAC’s own analysts. Whether a warning reaches every participant regardless of size, as Cyware’s Tom Stockmeyer framed the goal, depends on how that last step is handled.
What the AI Claims Establish, and What They Do Not
Cyware positions itself around agentic AI, meaning software that automates steps an analyst would otherwise perform, such as collecting, enriching and routing threat data. The release says this will help WaterISAC significantly reduce manual effort and deliver intelligence more efficiently. Those are plausible benefits for an intelligence team, but the release offers no baseline, no target metrics and no description of how automated outputs are validated before distribution.
It is also worth separating intelligence speed from response speed. A warning delivered in seconds helps only if the recipient can act on it. For a small utility, the bottleneck is often people and budget rather than information. The partnership addresses the information side; the response side remains with each utility. Cyware has also said it is supporting NRECA on Department of Energy-funded research into automated collective defense for electric cooperatives, which places the company across both utility inputs that data centers depend on most: power and water.
Background
The US water sector is unusually fragmented: more than 50,000 utilities, ranging from large metropolitan systems to small rural operations with minimal staff. WaterISAC serves as the sector’s information-sharing hub, one of a family of industry-specific ISACs that pool threat warnings so members can learn from one another. Through its partnership with the National Rural Water Association, WaterISAC says it reaches more than 20,000 of the smallest utilities.
Cyware is a threat intelligence software vendor that unifies intelligence management, sharing and collaboration, and orchestration and automation. It markets itself around agentic AI and collective defense, and counts enterprises, government agencies and ISACs among its customers. The WaterISAC deal extends that ISAC-focused strategy into a sector whose resilience underpins other infrastructure, including data centers that rely on local water for cooling and fire protection.
In July, hackers broke into the control systems of a drinking-water provider in Oregon. Officials have not said which one. It was part of a wave that reached at least 100 American water systems in seven states.
The attackers reached small computers that run pumps and valves over the internet and locked operators out. Some towns saw water pressure drop, flooding, or a precautionary boil-water notice.
This matters beyond your tap. Many of the huge computer buildings behind artificial intelligence use local tap water to stay cool, so a hacked water utility is their problem too.
Oregon Public Broadcasting reported on August 7, 2026, that Oregon Gov. Tina Kotek’s office confirmed hackers gained access to an Oregon water district’s core operating technology in July. Oregon Enterprise Information Services, which provides cybersecurity support to state agencies, confirmed a July incident involving unauthorized access to operational technology used by an Oregon drinking-water provider. State officials would not name the district, would not say whether the incident is linked to a wider campaign, and said the impact is still being assessed.
The Oregon disclosure follows a July 30 New York Times report that at least 100 US water systems had detected malicious attacks, which the paper said were initiated by hackers in Iran. An FBI release the same day acknowledged attacks in seven states and said some of the activity degraded water operations. At least 30 systems were targeted in Minnesota, where one treatment plant temporarily went offline; in Georgia, one system lost water pressure and briefly issued a boil-water precaution.
Executive Summary
An unnamed Oregon drinking-water provider is the latest confirmed victim of a July campaign against municipal water and sewage systems. According to the FBI, attackers connected over the internet to programmable logic controllers, the small industrial computers that run pumps and valves, then changed their IP addresses and passwords, cutting operators off from monitoring and control. Reported effects included loss of pressure and flooding.
For the data center industry, the episode matters because water is an operating input, not only a sustainability metric. Facilities that reject heat through evaporative cooling draw continuously on local utilities. The campaign shows that at least 100 of those utilities could be reached directly from the internet within days. A data center’s resilience therefore depends partly on the security of infrastructure it neither owns nor audits.
The same class of controller also runs chilled-water plants, pumps and valves inside data centers. The FBI’s guidance to water utilities, to limit remote access and keep manual fallback procedures, reads as a checklist for cooling plant operators as well.
What the FBI Says Happened
The FBI’s description of the attack is short and specific. Between July 27 and July 30, attackers connected to programmable logic controllers (PLCs), rugged single-purpose computers that open valves, start pumps and read sensors, directly over the internet. They then changed the devices’ IP addresses and passwords, which the agency said resulted in a loss of monitoring and control. Operators could no longer see or steer parts of their own systems.
The consequences were physical. The FBI said operational effects included loss of pressure and flooding, and warned that pressure loss could potentially allow untreated groundwater to seep into pipes. In Minnesota, where at least 30 systems were targeted, one treatment plant temporarily went offline. In Georgia, a pressure drop prompted a precautionary boil-water notice.
Attribution remains partly open. The New York Times reported the campaign was initiated by hackers in Iran. Oregon officials declined to say whether their incident belongs to that campaign and referred questions to federal investigators. That caution is reasonable while the investigation continues, and the operational lessons do not depend on who was behind the attacks.
Why AI Cooling Risk Sits Outside the Fence
Many data centers remove heat with evaporative cooling towers, which lose water continuously to evaporation and replace it, as so-called makeup water, from the local municipal supply. AI clusters pack far more heat into each rack than conventional servers. Even when the chips are cooled directly by liquid, that heat still has to leave the building, and in many designs it leaves through those same towers. For a significant share of facilities, water pressure at the meter is as much a dependency as power at the substation.
The failure modes the FBI listed match that dependency closely. A pressure loss or an offline treatment plant is exactly the event a cooling plant’s onsite water storage exists to ride through. What the July campaign changes is the likelihood and breadth of that event. At least 100 systems in at least seven states were affected in a matter of days. The technique did not require first breaching a corporate network, because the controllers were reachable from the internet. A risk that site selection teams once modelled as drought or main breaks now has a cyber path, and it can hit many utilities simultaneously.
The people exposed are the ones who build, lease and finance capacity: operators sizing onsite storage, tenants whose service agreements assume cooling continuity, and lenders underwriting sites in water-dependent markets. Oregon hosts major data center clusters around Hillsboro, The Dalles and Prineville. Nothing disclosed so far indicates the affected district serves any of them. The point is structural, not local.
The Same Controllers Run the Chiller Plant
PLCs are not unique to water utilities. The same kind of device, often from the same vendors, sequences chillers, modulates pumps and controls valves in data center mechanical plants. Remote access is common there for the same reason Tualatin Valley Water District spokesperson Justin Dyke gave for utilities: it lets operators respond quickly when demand shifts. The convenience cuts both ways when a controller’s management interface is reachable from the open internet.
The FBI’s recommendations to water systems translate almost directly. Limit remote access to controllers. Enforce authentication and other security protocols. Maintain manual procedures for when automation is lost. Dyke described that last practice at his district: if online systems go down, operators make changes by hand. Data center operators can apply the same test to their cooling plants and ask whether staff can run the chilled-water system safely with the controls network unavailable.
A Defense Spread Across 2,500 Districts
Oregon has more than 2,500 water districts, and all of its drinking-water systems are locally managed. Oregon Enterprise Information Services consults with districts on cybersecurity and threat assessments but does not run them. That structure is typical of US water and puts security decisions in the hands of many small operators with limited budgets and staff.
It also limits disclosure. The Portland Water Bureau said it routinely examines vulnerabilities with the city’s security team, the Cybersecurity and Infrastructure Security Agency and the FBI, but declined to say whether it was targeted in July. Tualatin Valley reported an increase in attempts, none successful. Klamath Falls and Corvallis reported no increase, and Redmond and Bend reported no breach. For a large water customer, that patchwork means a utility’s security posture is mostly invisible unless the customer asks directly.
Background
Water utilities have spent years connecting their treatment plants, pumping stations and reservoirs to remote monitoring. This lets small operating teams adjust flow and reservoir levels quickly as demand changes. The same connectivity, when controllers are reachable from the internet, exposes physical equipment to remote tampering. Federal agencies, including the FBI and the Cybersecurity and Infrastructure Security Agency, work with utilities on these risks, but in states like Oregon, day-to-day operation and security remain local responsibilities.
Oregon is also one of the country’s established data center markets, with large campuses around Hillsboro, The Dalles and Prineville. Water supply has featured in local debate about their growth. As AI workloads raise heat density per rack, cooling design, and for many facilities the municipal water behind it, has become a primary constraint on where and how capacity gets built.
A coordinated cyberattack hit more than 30 local public water systems in Minnesota this week. Federal investigators are now involved.
The damage was small. One city’s well and treatment plant briefly shut down, and there are no signs the tap water became unsafe. Officials say early clues point to hackers linked to Iran, but that is not confirmed.
Why it matters beyond Minnesota: the giant computer buildings behind apps and artificial intelligence often cool their machines with water from these same local utilities. A hack at the water plant is a risk to them too.
A coordinated cyberattack affected more than 30 community water systems in Minnesota in the week of July 27, according to Minnesota IT Services, the state’s technology agency, Al Jazeera and Reuters reported on July 30. Local officials said the well and treatment plant in at least one city temporarily went offline, but the attack appears to have had minimal impact, and there are no indications the water supply became unsafe to drink. The FBI said on Wednesday that it was “actively engaged with victims.”
State officials said the incidents resemble activity attributed to hackers aligned with Iran’s government, and cautioned that the assessment is preliminary. The New York Times, citing unnamed state and federal officials, reported that Iranian hackers were the likely culprits, while noting that attribution is not definitive and that the attackers may have posed as Tehran-aligned actors. The attack comes amid renewed US–Iran hostilities after a June memorandum of understanding that paused the fighting broke down this month.
Executive Summary
More than 30 local water systems in a single US state were hit in what state officials called a “coordinated cyberattack.” The physical consequences were limited: one city’s well and treatment plant briefly went offline, and drinking water was not reported unsafe. But the breadth of the event and the FBI’s involvement put the security of utilities’ operational technology (OT) — the industrial control systems that run pumps, wells and treatment processes — back at the top of the critical-infrastructure agenda.
For the data center industry, the relevance is indirect but concrete. Many facilities that use evaporative cooling draw their water from municipal systems like these. The Minnesota incident is a reminder that a data center’s cooling supply depends not only on its own cybersecurity but on the cybersecurity of utilities it neither owns nor controls, and whose security resources are set by local public budgets rather than by the data center.
No data center has been reported as affected, and attribution of the attack remains preliminary. The episode’s value for operators is as a live test of a common assumption: that water outages are local, physical events rather than coordinated ones spanning many utilities at once.
The Cooling Risk Sits Outside the Fence
Data centers that use cooling towers or other evaporative systems reject heat by evaporating water, which has to be continuously replaced — industry shorthand calls this “makeup water.” Where a campus draws that water from a municipal utility, the utility’s wells, pumps and treatment plant become part of the data center’s cooling chain. Those assets are run by OT: programmable controllers and supervisory software that start pumps, open valves and dose chemicals. An intrusion that reaches them is, for every large water customer downstream, a cooling-supply risk.
Minnesota shows what that looks like in practice. More than 30 community water systems were affected in a single coordinated event, and in at least one city the well and treatment plant went temporarily offline — precisely the kind of interruption that stops water flowing to a large commercial customer. Water resilience planning has traditionally centered on familiar, local failures: a main break, a drought restriction, a fault at one plant. A coordinated intrusion is different in kind, because it can reach many independent systems at once, which may also affect neighboring utilities or backup supplies an operator expected to lean on.
The exposure is not uniform. AI training and inference hardware concentrates far more heat per rack than conventional servers, pushing operators toward liquid cooling and larger heat-rejection systems. Closed-loop liquid cooling and air-cooled chillers consume little water; evaporative designs trade lower electricity use for continuous water dependence. The operators most exposed to an event like Minnesota’s are water-reliant sites on a single municipal feed with limited on-site storage. Nothing reported so far indicates that any data center served by the affected systems saw an interruption, and the outage that did occur was brief.
Minimal Impact Is the Good News, Not the Whole Story
The most important outcome is that drinking water was not reported unsafe and service disruption appears to have been limited. That is a credit to the utilities and responders involved, and it should temper any alarm.
But officials’ own description points to a campaign rather than a one-off. Minnesota IT Services spokesperson Emily Zimmer said “the timing, methods of access, and targeted infrastructure share characteristics with other coordinated cyber incidents our federal partners have observed involving critical infrastructure.” Community water systems often run lean, with limited dedicated security staff, which makes a campaign that sweeps many of them at once hard to defend against one utility at a time.
The number that matters for infrastructure planners is therefore the 30-plus, not the single outage. Breadth indicates that access was obtainable across many separate operators simultaneously. A contained result this time says more about where the attackers stopped than about how far they could have gone.
Attribution Is Unsettled; the Threat Picture Is Not
State officials said the incidents resemble those attributed to Iran-aligned hackers but called that assessment preliminary. Officials cited by The New York Times said Iranian hackers were the likely culprits, while acknowledging the conclusion could change and that the attackers may have impersonated Tehran-aligned groups to raise tensions. Former intelligence officials told the paper a false-flag operation was less likely. The fair reading is that the available indications point one way but are not conclusive, and no technical evidence has yet been published that would let outside analysts test either view.
For defenders, final attribution matters less than the context. Water infrastructure has become a target across the current conflict: reported US strikes have hit Iranian water plants, and Iran has targeted desalination plants in neighboring Gulf states. Whoever is ultimately responsible for Minnesota, that backdrop raises the baseline risk to water-sector OT, and to every large customer that depends on it.
What Operators Can Ask Their Water Utility
Data center operators cannot secure a municipal utility’s control systems, but they can reduce how much a compromise of them would cost. Practical steps include confirming how and how quickly the utility will notify large customers of a cyber incident, knowing how many hours of cooling the site’s on-site water storage actually covers, qualifying alternative supplies such as reclaimed water or trucked delivery, and weighing low-water cooling designs for new builds.
The relationship can run both ways. Large water customers have a direct stake in their utility’s security posture, and utilities facing coordinated campaigns have an interest in knowing which customers carry the highest consequences from an outage. Minnesota makes that conversation easier to start.
Background
Water utilities are among the more exposed parts of US critical infrastructure: many are small, locally run and operate industrial control systems designed for reliability rather than security. US agencies have previously linked attacks on water-sector equipment to Iran: in late 2023, intrusions into industrial controllers at several US water utilities, including the Municipal Water Authority of Aliquippa in Pennsylvania, were attributed to a group affiliated with Iran’s Islamic Revolutionary Guard Corps.
Data centers become significant water users when they rely on evaporative cooling, which trades lower electricity use for continuous water consumption. As AI workloads raise heat density, cooling design, and the water supply behind it, has become a central siting and permitting question. The Minnesota incident arrives amid renewed US–Iran hostilities: the US joined Israel in a war against Iran on February 28, and a June memorandum of understanding that paused the fighting broke down in July.
Eight US government agencies, including the National Security Agency, warned on June 3 that hackers are breaking into the electronic gauges that measure what is inside fuel storage tanks, and tampering with them.
These gauges sit on tanks across energy, chemical, farming and transport sites. The same kind of gauge often watches the diesel that keeps a data center’s emergency generators running during a power cut.
If a gauge reports the wrong amount of fuel, a backup plan can fail exactly when it is needed. The agencies are urging every operator to lock these devices down.
On June 3, 2026, the National Security Agency said in a press release that it had joined the Cybersecurity and Infrastructure Security Agency (CISA) and six other federal agencies in publishing a fact sheet titled CISA and Partners Urge Hardening Automatic Tank Gauge Systems. Automatic tank gauges (ATGs) are networked devices that remotely monitor fuel and liquid levels, temperature and potential leaks in storage tanks.
The agencies said unattributed threat actors have been compromising internet-exposed ATGs and then modifying them through command execution. The co-authors are CISA, the NSA, the FBI, the Department of Energy, the Environmental Protection Agency, the TSA, the Department of Transportation and the Department of Agriculture. The NSA recommended that all operational technology owners in national security systems, the Department of War, the defense industrial base, the federal government and US critical infrastructure sectors review and implement the fact sheet’s mitigations.
Executive Summary
Eight federal agencies have jointly flagged ongoing malicious activity against a device most people have never heard of: the automatic tank gauge, the electronic sensor-and-console unit that reports how much liquid is in a tank, how warm it is and whether it is leaking. The warning names energy, chemical, food and agriculture, and transportation as affected sectors, and describes attackers not just reading these devices but changing them.
For data center operators, the relevance is direct even though the sector is not singled out. Every facility with diesel backup generators stores fuel on site, and the number that tells an operator how many hours of emergency runtime remain is typically produced by tank-monitoring equipment of exactly this kind. A warning that such equipment is being actively modified by outsiders turns generator fuel data from a facilities housekeeping item into something that belongs inside the security program.
The broader lesson is about scope. As AI campuses scale up their on-site generation and fuel storage, the attack surface grows with it, and much of that surface is operational technology (OT), the industrial control equipment that runs physical plant rather than business IT.
The Gauge Behind the Runtime Promise
A data center’s resilience story usually runs in layers: utility power, then batteries in the uninterruptible power supply (UPS) to bridge the first seconds of an outage, then diesel generators to carry the load for hours or days. That last layer is only as good as the fuel behind it, and operators state their emergency runtime in hours of on-site fuel. The figure they rely on comes from tank monitoring, the level, temperature and leak readings the agencies say ATGs are built to provide.
The agencies describe attackers compromising internet-exposed ATGs and then modifying them through command execution, meaning they issued commands that changed how the device behaves. Applied to a generator fuel system, the operational risks are straightforward to reason about: a gauge that overstates fuel can leave an operator believing it has a day of runtime when it has far less; one with suppressed leak alarms can let a spill go unnoticed; one that throws false alarms can trigger unnecessary emergency deliveries or shutdown procedures. None of those outcomes needs an attacker to touch the generator itself. The fuel reading is part of the power chain, and that is why it now has to be defended like one.
That argument scales with AI. Large AI training and inference campuses draw far more power than traditional enterprise halls, and operators that back that load with diesel need correspondingly more generators and more stored fuel. More tanks mean more gauges, and every networked gauge is a device that has to be inventoried, patched or isolated.
A Broad Coalition, a Broader Recommendation
The makeup of the coalition says something about how the agencies view the problem. The EPA regulates fuel storage and leak detection, the Department of Energy covers the energy sector, the TSA and Department of Transportation cover pipelines and transport, and the Department of Agriculture covers farm fuel storage. Pairing them with the NSA, CISA and the FBI signals that the concern spans environmental, safety and national security lines at once.
Data centers are not among the sectors the fact sheet names. But the NSA’s recommendation is deliberately wide: all OT owners and operators in national security systems, the Department of War, the defense industrial base, the federal government and US critical infrastructure. Facilities that host government workloads, defense contractors or critical services fall squarely inside that language, and colocation providers serving those customers will likely be asked about it.
Where Security Programs Tend to Thin Out
Tank gauges often sit in an organizational gap. They are frequently specified by the fuel system or generator contractor, maintained by facilities staff, and sometimes connected so that a fuel supplier or monitoring service can read them remotely. The network team may not know they exist, and the security team may never have scanned them. That is the pattern that leaves OT devices reachable from the internet, and it is the exposure the agencies describe.
The practical response is unglamorous: find every gauge, confirm none is reachable from the public internet, place them behind segmented networks, review remote-access arrangements with vendors, and apply the fact sheet’s mitigations. Just as important, operators should keep an independent way to verify fuel levels, such as periodic manual measurement, so that a single compromised device cannot quietly rewrite the runtime assumption an entire backup plan depends on.
The agencies have not attributed the activity, and the warning should be read for what it is: evidence of ongoing compromise and modification of exposed devices, not a claim that any data center has lost backup power. That measured reading is still enough to justify action, because the fix is cheap relative to the consequence.
Background
Automatic tank gauges have been standard equipment on fuel storage tanks for decades, in large part because they automate the leak detection that environmental rules require for stored fuel. Over time many gained network interfaces so that owners, fuel suppliers and service contractors could read them remotely, and security researchers have documented internet-reachable units for roughly a decade.
CISA leads federal efforts to protect US critical infrastructure and frequently co-publishes guidance with the NSA, the FBI and sector-specific agencies. Data centers depend on the same class of equipment: diesel generators backed by on-site fuel tanks remain the dominant form of emergency power, and fuel monitoring is part of how operators plan how long they can run without the grid.
A cybersecurity firm has concluded that the breach of the Los Angeles Metro system was carried out by the Iranian government rather than the hacktivist group initially believed responsible, according to reporting by Cybersecurity Dive published May 25, 2026. The reassessment turns what looked like ideologically motivated hacking into a nation-state operation against one of the largest public transit agencies in the United States.
Executive Summary
The core news is a change in attribution, not a new intrusion: an incident already known to have affected LA Metro is now being attributed by a security firm to Iranian government actors instead of an independent hacktivist group. Attribution — the process of identifying who is actually behind a cyberattack, using technical evidence such as infrastructure, tooling, and tradecraft — is one of the hardest problems in security, and revisions like this one are not unusual as investigations mature.
The distinction matters far beyond labeling. A hacktivist group typically seeks publicity and disruption on a limited budget; a state actor brings sustained resources, strategic intent, and potential interest in long-term access to operational systems. If the firm’s assessment holds, LA Metro joins a growing list of U.S. critical-infrastructure operators — utilities, water systems, ports — that have found themselves targets of state-sponsored campaigns rather than opportunistic crime.
When Hacktivism Is a Costume
The reported finding fits a pattern security researchers and U.S. agencies have documented for years: state-backed operators adopting hacktivist personas to claim attacks while obscuring their sponsor. A self-declared activist brand gives a government deniability, lets it signal capability without formal escalation, and muddies the victim’s response — agencies respond differently to vandals than to foreign intelligence services. U.S. advisories have previously linked Iranian-affiliated actors operating under hacktivist-style names to attacks on American critical infrastructure, including water utilities.
That said, the source here is a single security firm’s assessment as reported in trade press, and the article available to us does not detail the evidence behind the conclusion. Attribution claims deserve scrutiny in both directions: the original hacktivist claim should not have been taken at face value, and the new state-actor attribution should be weighed against the firm’s disclosed methodology once it is public. Neither the firm’s identity nor LA Metro’s or the federal government’s position on the finding is established by the headline alone.
Transit Is Now a Nation-State Target
Public transit is a soft but strategic target. Agencies like LA Metro run a mix of traditional IT (payment systems, employee email, rider data) and operational technology, or OT — the industrial control systems that run trains, signals, and stations. Years of modernization have connected these once-isolated systems to networks, widening the attack surface faster than transit budgets have funded defenses. Unlike banks or cloud providers, transit agencies are public bodies with constrained security spending and long procurement cycles.
For a state adversary, the appeal is less about stealing data than about demonstrating reach into daily American life. Even an intrusion that never touches train control erodes public confidence and forces expensive remediation. That is why federal agencies have pushed performance-based cybersecurity directives onto rail and transit operators in recent years: the sector’s threat model has shifted from criminals and vandals to well-resourced foreign services.
Why Attribution Changes the Defense Calculus
Reattribution from hacktivist to state actor changes practical decisions. It typically elevates federal involvement — CISA, the FBI, and TSA all have roles in transit cyber incidents — and it changes assumptions defenders must make: state actors are more likely to have established persistent, quiet access rather than a one-time smash-and-grab, so incident response must hunt for footholds, not just patch the entry point. Cyber-insurance treatment can also differ, since some policies contain exclusions for state-sponsored or ‘act of war’ events, a contested area of insurance law.
For infrastructure operators and their vendors, the lesson is uncomfortable but useful: the initial story about who attacked you is often wrong, and architecture should not depend on getting it right. Segmentation between IT and OT networks, monitored access to control systems, and logging sufficient to support later forensics all pay off regardless of whether the adversary turns out to be a teenager or a foreign intelligence service.
Background
LA Metro serves Los Angeles County, one of the most populous regions in the United States, operating bus and rail networks that depend on a mix of business IT and industrial control systems. U.S. transit agencies broadly have spent the past several years under new federal cybersecurity directives after officials warned that foreign state actors were probing American critical infrastructure. Iranian-linked cyber operations against U.S. targets are well documented in government advisories, including cases in which state-affiliated actors used hacktivist personas — the same pattern a security firm now says played out at LA Metro. This article is based on a single dated report; details of the evidence behind the attribution were not available in the source material.
The U.S. Government Accountability Office (GAO), Congress’s independent watchdog, publicized a warning on May 21, 2026 that America’s drinking water and wastewater systems remain vulnerable to cyberattack. The notice, titled “America’s Water Systems Are Vulnerable to Cyberattack,” continues a line of GAO work flagging weaknesses in how the sector — and its federal overseer, the Environmental Protection Agency (EPA) — manages cybersecurity risk.
Executive Summary
The GAO’s message is blunt: the systems that treat and deliver water to American homes and businesses are exposed to cyber threats, and the federal oversight structure meant to manage that risk has gaps. The EPA is the designated “sector risk management agency” for water — the federal body responsible for coordinating the sector’s security — and GAO has repeatedly examined whether the agency has the strategy, authority, and resources to do that job effectively.
Why does a watchdog notice matter when it announces no new program or funding? Because GAO reports are the primary mechanism by which Congress learns that a policy is not working. When GAO says water systems “are vulnerable,” it is signaling to lawmakers that the current largely voluntary approach to water-sector cybersecurity has not closed the gap — and implicitly inviting legislation, budget action, or new regulatory authority. For anyone who operates critical infrastructure, or depends on it, that is a signal worth reading carefully.
Why Water Utilities Are a Soft Target
The American water sector is extraordinarily fragmented: tens of thousands of community water systems, most of them small, locally governed, and thinly staffed. Unlike banking or electricity — sectors with large sophisticated operators and mandatory security standards — a typical small water utility has no dedicated cybersecurity staff and a limited budget that voters and ratepayers expect to go toward pipes and treatment, not firewalls.
The technical exposure compounds the organizational one. Water treatment and distribution run on operational technology (OT) — the industrial control systems, sensors, and programmable logic controllers that open valves and dose chemicals. Much of this equipment is decades old, was never designed with security in mind, and has increasingly been connected to the internet for remote monitoring and maintenance convenience. That connection is exactly what publicly reported incidents in recent years have exploited, including a 2021 intrusion at a Florida treatment plant and 2023 attacks on utilities running internet-exposed control devices.
The EPA Oversight Question
The editorial heart of GAO’s warning is not the utilities themselves but the federal architecture above them. The EPA carries the water-sector security mandate, yet its cybersecurity toolkit has historically leaned on voluntary guidance, assessments, and technical assistance rather than enforceable standards. GAO’s role is to ask whether that model is producing results — and its continued use of the word “vulnerable” suggests its answer remains no.
The hard policy problem is that neither of the obvious fixes is free. Mandatory cybersecurity standards would require statutory authority, an enforcement apparatus, and a way to fund compliance at utilities that can barely fund operations. Continued voluntarism avoids those costs but leaves protection uneven, concentrated in large utilities that would likely have invested anyway. GAO reports typically press agencies toward measurable strategies — defined roles, risk-based priorities, and outcome tracking — precisely because they force a choice between these paths rather than allowing drift.
What It Means Beyond the Water Sector
Water security is not only a water problem. Hospitals, manufacturers, and data centers all depend on reliable municipal water — and for data centers specifically, water is often a cooling input, meaning a successful attack on a water utility can cascade into digital-infrastructure availability. Operators of facilities in any sector should treat this warning as a prompt to examine their own upstream utility dependencies and contingency plans, not just their own perimeters.
There is also a market signal here. Sustained federal attention to OT security in water — even without new mandates — tends to pull procurement toward vendors offering network segmentation, secure remote access, and monitoring for industrial control systems, and toward managed-security providers who can serve utilities too small to build in-house teams. If Congress responds to GAO with funding or requirements, that demand hardens into a genuine market. Until then, the sector’s spending will likely remain uneven, tracking utility size rather than actual risk.
Background
The U.S. water sector comprises tens of thousands of community drinking-water systems and thousands of wastewater utilities, most locally owned and operated. Federal security policy designates the EPA as the sector’s risk management agency, working alongside the Cybersecurity and Infrastructure Security Agency (CISA), but the sector has no mandatory federal cybersecurity standards comparable to those governing the bulk electric grid. GAO, Congress’s watchdog, has scrutinized this arrangement for years, and real-world incidents — from a 2021 Florida treatment-plant intrusion to 2023 attacks on internet-exposed utility control devices — have kept the question of whether voluntarism is enough squarely on the policy agenda.
A newly formed cybersecurity industry coalition has said it intends to take a leading role in protecting United States critical infrastructure — the power grids, pipelines, water systems, telecommunications networks and data centers that other services depend on. The formation was reported on 11 May 2026 by Cybersecurity Dive.
The coverage available to us is headline-level: it establishes that the coalition exists and states its ambition, but the membership roster, funding model, governance structure and operating timeline are not detailed in the material we can verify. This article analyzes the structural question the announcement raises — what an industry-led body can and cannot do for national cyber defense — and sets out the specifics that remain open.
Executive Summary
The announcement is best understood as a positioning move in a shifting division of labor. For roughly a decade, US critical infrastructure cyber defense has been organized around a federal hub — the Cybersecurity and Infrastructure Security Agency (CISA) — surrounded by sector-specific industry groups. Through 2025 and into 2026, CISA absorbed widely reported workforce reductions and proposed budget cuts, while the statutory liability protections that encouraged companies to share threat data with the government lapsed in late 2025 and became the subject of ongoing legislative debate. A vacuum, real or anticipated, invites someone to fill it.
Why it matters for infrastructure operators: cyber defense at national scale is fundamentally a coordination problem, not a product problem. Attacks on one utility or carrier are previews of attacks on the next, and the value of any defensive body lies almost entirely in how fast and how completely warning travels between competitors. Whoever convenes that exchange sets the terms — what gets shared, with whom, under what legal cover, and at what price.
What is not yet established: the coalition’s claim to leadership is, at this stage, a stated intention rather than a demonstrated capability. Nothing in the available reporting confirms who has joined, what the group will fund, or how it will relate to the federal agencies and existing sector bodies already occupying this space. Those are the tests worth applying, and they are answerable within months.
Why Industry Is Volunteering for a Job It Once Resisted
For most of the past decade, the private sector’s posture toward critical infrastructure cybersecurity policy was defensive: resist mandates, negotiate reporting rules, worry aloud about liability. A coalition announcing that it intends to lead is a notable inversion. The plainest explanation is not altruism but exposure. Roughly the great majority of US critical infrastructure is privately owned and operated, which means the operators absorb the losses — outage costs, ransom payments, regulatory penalties, insurance repricing — regardless of who holds the coordinating role in Washington.
If federal coordinating capacity contracts, the risk does not disperse; it lands on balance sheets. Under those conditions, funding a shared defensive apparatus becomes a rational cost, in the same way that competing airlines jointly fund safety data programs because a crash at one carrier damages all of them. The economics here are the economics of a public good that private parties have decided to buy for themselves.
The counter-reading deserves equal weight. Industry coalitions are also lobbying vehicles, and a group that positions itself as the operational leader of critical infrastructure defense acquires substantial influence over the regulation of its own members — including which standards become de facto requirements and which incidents are deemed reportable. Neither reading is disprovable from a formation announcement. Both should be held open until the governance documents appear.
What a Coalition Can Do — and What Only Governments Can
A well-run private body can do a great deal. It can pool threat intelligence faster than any agency clears it; it can run joint exercises, publish detection signatures, fund shared tooling for smaller utilities that cannot afford their own security teams, and set procurement standards that vendors must meet to sell into the sector. These are genuine capabilities, and where they already exist — in the sector-based Information Sharing and Analysis Centers, or ISACs, and in cross-vendor groups like the Cyber Threat Alliance — they have measurable value.
What no coalition can do is exercise state power. It cannot compel a reluctant operator to patch, cannot seize infrastructure used by an adversary, cannot see foreign signals intelligence, cannot indict anyone, and cannot grant legal immunity to a company that hands over customer-adjacent telemetry. That last point is not a technicality. The 2015 information-sharing framework worked largely because it told general counsels that sharing indicators would not create antitrust or privacy liability. With that protection lapsed and its restoration unresolved, a private coalition asking members to share aggressively is asking them to accept legal risk that only Congress can remove.
The realistic model, then, is complementary rather than substitutive. Industry can carry operational tempo — the fast, technical, day-to-day work of spotting and blocking. Government retains the coercive and intelligence functions. The failure mode to watch for is a coalition that markets itself as a replacement for federal capacity, because that framing tends to reduce political pressure to fund the functions industry structurally cannot perform.
Winners, Losers, and Who Pays for Coordination
If the coalition matures, the clearest beneficiaries are large operators with mature security programs. They already generate high-quality telemetry, they can absorb membership costs, and they gain influence over standards they were going to meet anyway. Hyperscale cloud providers and major data center and network operators sit in a particularly strong position: they see enormous volumes of attack traffic, which makes them the most valuable contributors and therefore the most powerful voices at the table.
The parties at risk of being left out are the ones the country most needs covered — small municipal water systems, rural electric cooperatives, regional hospitals, mid-sized carriers. These organizations often run legacy operational technology, employ few or no dedicated security staff, and cannot pay meaningful dues. Any coalition serious about critical infrastructure rather than large enterprise defense has to answer how those operators are subsidized. A pricing model that tracks ability to pay is a strong signal of seriousness; a flat corporate membership fee is a signal that the group’s practical scope is narrower than its name.
There is also a vendor question worth watching without prejudging it. Security suppliers have a legitimate operational role in any such body — they hold much of the visibility — and also a commercial interest in defining the standards their products satisfy. Governance that separates threat-sharing operations from standards-setting, with disclosed member lists and recusal rules, is the ordinary remedy. Its presence or absence will be visible in the founding documents.
The Evidence Test to Apply Over the Next Two Quarters
Announcements of this kind are cheap; sustained coordination is expensive. Four observable markers separate the two. First, a published member list with named operators from more than one sector — a coalition drawn from a single industry is a trade association with a broader title. Second, a funded budget and paid technical staff, rather than a volunteer steering committee. Third, a concrete first deliverable with a date: a joint exercise, a shared detection feed, a subsidized tooling program for small utilities.
Fourth, and most diagnostic, an explicit statement of how the group relates to CISA, to the sector coordinating councils, and to the existing ISACs. Critical infrastructure defense is not an empty field; it is a crowded one with a decade of institutional plumbing. A new body that names its interfaces is doing engineering. A new body that does not is, for now, doing communications.
None of this is a reason for skepticism about the underlying need. The threat picture that plausibly motivated the coalition — persistent adversary pre-positioning inside operational technology networks, ransomware against hospitals and municipalities, the exposure of long software supply chains — is well documented and does not depend on this announcement being substantive. The question is narrower and fairer: whether this particular vehicle is built to carry that weight.
Background
US critical infrastructure cyber defense has been organized since the mid-2010s around a public-private model: a federal coordinating hub, formalized as CISA in 2018, working alongside sector coordinating councils and the Information Sharing and Analysis Centers that circulate threat data within industries. The Cybersecurity Information Sharing Act of 2015 supplied the legal foundation, giving companies liability protection for passing indicators of compromise to the government and to each other. In 2021, CISA added the Joint Cyber Defense Collaborative to bring major technology and security firms into planning alongside federal agencies.
That arrangement has come under strain. CISA sustained widely reported staffing reductions and proposed budget cuts through 2025 and into 2026, while the 2015 law’s information-sharing protections lapsed in late 2025 with restoration still contested in Congress. At the same time, publicly documented threats to operational technology networks — the industrial control systems that run grids, pipelines and water treatment — have grown more persistent. Roughly the great majority of the affected assets are privately held, meaning the operators carry the financial consequences regardless of how federal capacity evolves. That combination is the setting into which this coalition has announced itself.
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.
US government agencies have issued a warning about an active cyber threat targeting critical infrastructure, as reported by Fox Business on April 29, 2026. The alert concerns the control-system layer of infrastructure — including programmable logic controllers (PLCs), the small ruggedized computers that directly operate pumps, valves, breakers, and machinery in sectors such as power, water, and manufacturing.
Details in the initial report are limited: the public reporting confirms an active campaign and a federal warning, but the underlying advisory’s specifics — which sectors, which vulnerabilities, and which actor — are not spelled out in the source item.
Executive Summary
The core of the announcement is straightforward: federal cybersecurity authorities believe an active campaign is underway against the systems that physically run American critical infrastructure, and they consider it serious enough to warn operators publicly. Warnings of this kind are typically issued by the Cybersecurity and Infrastructure Security Agency (CISA), often jointly with the FBI and NSA, and are directed at the operational technology (OT) side of the house — the industrial networks that sit behind, and are supposed to be separated from, ordinary corporate IT.
Why it matters: PLCs and related industrial controllers were largely designed decades ago for reliability, not security. Many run without authentication, cannot be easily patched, and were never meant to touch the internet — yet thousands are reachable online. When an attacker moves from stealing data to manipulating a controller, the consequences shift from financial loss to physical disruption: outages, equipment damage, and safety risk.
For infrastructure operators — including data center, network, and cloud providers whose facilities depend on building automation, power management, and cooling control systems — the warning is a prompt to treat OT exposure as a live operational risk, not a compliance checkbox.
Why Attackers Keep Coming Back to PLCs
A programmable logic controller is a purpose-built computer that reads sensors and drives physical equipment on a fixed loop — open this valve, start that pump, trip this breaker. The installed base is enormous, long-lived, and heterogeneous: controllers commissioned 15 or 20 years ago still run production processes today. Many speak industrial protocols (Modbus, for example) that carry no authentication at all — any device that can reach the controller on the network can often command it.
That makes PLCs asymmetrically attractive. An attacker does not need a sophisticated exploit if the device accepts unauthenticated commands by design; they need network access. This is why federal advisories in recent years have repeatedly emphasized unglamorous basics — inventorying internet-exposed devices, changing default passwords, and putting controllers behind firewalls and VPNs — rather than exotic defenses.
The Pattern Behind the Warning
This alert does not arrive in a vacuum. US agencies have spent several years documenting both state-linked pre-positioning in critical infrastructure — most prominently the Volt Typhoon campaign attributed to China, which agencies said sought footholds in US infrastructure networks — and opportunistic attacks by lower-skill actors on exposed water and utility systems. Real-world incidents, from the 2021 Colonial Pipeline ransomware shutdown to intrusions at small water utilities, have shown that the gap between a network compromise and a physical consequence can be uncomfortably short.
The honest caveat: from the initial reporting alone, we cannot tell which category this campaign falls into — a capable state actor, criminal ransomware crews, or opportunists scanning for exposed controllers. Those are very different threats with different defenses, and the distinction matters more than the headline. Until the underlying advisory’s technical details are widely digested, operators should assume the guidance applies to them and act on exposure, not attribution.
The Economics of OT Security Debt
Critical-infrastructure operators face a structural problem that ordinary IT does not: you cannot patch a controller that is running a water plant on Tuesday afternoon, and replacing fleets of working industrial hardware to gain security features is capital-intensive with no revenue upside. Utilities in particular operate under rate regulation that can make discretionary security spending hard to justify quickly. The result is a persistent installed base of insecure-by-design equipment — security debt that accumulates faster than refresh cycles retire it.
The likely beneficiaries of sustained federal pressure are the OT-security specialists — firms focused on industrial asset inventory, network monitoring, and segmentation — and vendors of modern controllers with secure-by-design features. The costs land on asset owners, and disproportionately on small operators such as municipal water systems, which own critical processes but lack dedicated security staff. Any policy response that ignores that resourcing gap will under-deliver.
What This Means for Data Center and Cloud Operators
It is tempting for digital-infrastructure companies to read “PLC warnings” as someone else’s problem. They should not. Modern data centers are industrial facilities: building management systems, power distribution and switchgear controls, generators, and cooling plants all run on the same classes of controllers and protocols named in OT advisories. A compromised cooling or power-management controller is a facility-availability event, and at AI-era power densities the thermal margin between normal operation and equipment shutdown is measured in minutes.
The practical checklist is well established even before this advisory’s specifics emerge: know every OT device you own, ensure none are directly internet-reachable, segment OT networks from corporate IT, eliminate default credentials, monitor industrial protocols for anomalous commands, and rehearse manual-operation fallbacks. None of that requires waiting for attribution.
Background
Critical infrastructure — energy, water, transportation, communications, and the industrial base — runs on operational technology: control systems designed in an era when isolation from outside networks was assumed. That assumption eroded as operators connected plants for remote monitoring and efficiency, leaving insecure-by-design devices reachable from hostile networks. The US government has responded with an escalating series of advisories and initiatives over the past decade, from post-Colonial Pipeline security directives to joint alerts on state-sponsored pre-positioning in infrastructure networks.
CISA, created in 2018, coordinates this defense across sixteen designated critical-infrastructure sectors, most of which are privately owned — meaning federal warnings largely rely on voluntary action by companies and municipalities. The recurring theme of recent years is that the gap between attacker interest and defender readiness in OT remains wide, particularly among small utilities with limited security resources.
