Loading...

After the 2026 PLC Attacks: An Arizona Checklist for Securing Internet-Exposed Industrial Controllers

Industrial IoT (IIoT)

Published by IOT Arizona Research & Editorial Team

After the 2026 PLC Attacks: An Arizona Checklist for Securing Internet-Exposed Industrial Controllers

Starting on July 27, 2026, water and wastewater utilities in at least seven states began reporting cyber incidents to the FBI. The targets were programmable logic controllers, the rugged industrial computers that open valves, start pumps and hold pressure setpoints. In an August 6 public service announcement, the FBI and EPA said attackers were going after internet-facing Rockwell Automation Allen-Bradley MicroLogix 1100 and 1400 series controllers, and that some of the activity had degraded water operations. The agencies added that operators of other PLC brands should take the same precautions.

Arizona was not named among the affected states. That is not a reason to relax. The same kinds of controllers run small water districts in rural counties, pump stations on irrigation networks, mine dewatering systems, food processing lines and utility infrastructure supporting the Valley's semiconductor and data center build-out. An Arizona State University cybersecurity expert told KTAR that water systems are among the most attractive targets available to foreign adversaries.

This article is written for plant managers, operations leads and small utility staff who need a practical starting point. It focuses on what can be checked quickly, which controls matter most, and how to secure industrial IoT without disrupting production.

Why This Matters Beyond Water Utilities

The July attacks followed a familiar pattern: controllers reachable directly from the internet, often with default or weak passwords, and no gateway or VPN between the device and the outside world. That pattern is not unique to water. It shows up anywhere equipment was connected for convenience, such as a PLC given a cellular modem so a technician could check it from home, or a vendor granted remote access years ago and never removed.

Industrial IoT has made those shortcuts more common. Every connected sensor, gateway and remote monitoring panel adds value, but each one is also a potential path into the control network if it is not set up carefully.

Arizona's Particular Exposure

A 2026 practitioner-led assessment of Arizona cybersecurity by the Sonoran Desert Security User Group identified several systemic weaknesses, including rural cybersecurity capacity gaps, legacy infrastructure and technical debt, third-party and supply chain risk, and governance gaps across small and mid-sized organizations. Those findings map closely onto industrial operations in the state:

  • Small water systems and irrigation districts often run with one or two operators who handle everything from chemical dosing to IT.
  • Mining operations in remote parts of the state depend on long-distance telemetry and vendor remote support.
  • Manufacturers and suppliers tied to the semiconductor cluster face customer security requirements that are rising quickly.
  • Agricultural and irrigation infrastructure is adding connected pumps and meters as water accounting pressure grows under the new Colorado River guidelines.

An Afternoon Exposure Audit

You do not need a large budget to find out whether your controllers are exposed. A small team can work through these steps in a few hours.

  1. List every controller and gateway. Walk the site and the drawings. Include PLCs, HMIs, RTUs, cellular routers and any "temporary" remote access devices.
  2. Identify every external connection. For each device, note how it reaches the outside world: plant firewall, cellular modem, satellite link or vendor-installed router.
  3. Check your public footprint. Ask your internet provider or an IT partner to scan the public IP addresses assigned to your organization, including cellular data plans, to confirm no industrial protocols or management interfaces are reachable from the internet.
  4. Review credentials. Confirm default passwords are changed on every controller, HMI and router. Remove shared accounts where possible.
  5. Inventory remote access. List every vendor, contractor and employee with remote access, how they connect, and whether that access is still needed.
  6. Confirm manual operation. Verify that operators can run critical processes by hand if controllers must be isolated, and that they have practiced it recently.

If step 3 finds anything exposed, treat it as urgent. The federal guidance is direct: remove PLCs from direct internet exposure, change default passwords and route remote access through a VPN or secure gateway.

Controls Ranked by Effort and Impact

ControlEffortImpactNotes
Remove internet-facing controllersLowVery highDirectly addresses the attack path used in 2026
Change default credentialsLowHighInclude routers, HMIs and engineering workstations
Secure remote access with MFAMediumVery highReplace always-on vendor connections with on-demand, logged sessions
Segment OT from ITMedium to highVery highKeeps office ransomware from reaching pumps, valves and process lines
Offline backups of PLC programsLowHighSpeeds recovery if logic is altered or wiped
Passive OT network monitoringMediumHighGives asset visibility and alerts on unusual commands without touching controllers
Firmware and patch managementMediumMedium to highMust follow change control to avoid production disruption

Remote Access Is Where Most Trouble Starts

Across water and industrial incidents, exposed or poorly secured remote access keeps appearing as a root cause. The 2021 intrusion at the Oldsmar, Florida water plant, where an attacker used a shared remote access tool to briefly change a chemical setpoint, remains the textbook example.

For Arizona operations spread across large distances, remote access is a genuine necessity, not a luxury. The goal is to make it deliberate. Good practice includes a single, monitored entry point instead of multiple vendor tools, multifactor authentication for every user, sessions that must be requested and approved rather than left open, and logging that records who connected, when and what they changed. Cellular routers attached directly to controllers deserve special scrutiny, because they often bypass the plant firewall entirely.

Patching Without Stopping the Line

September 2026 brought a fresh round of industrial control system advisories from Schneider Electric, Siemens and Aveva. Schneider's most severe new issue, CVE-2026-3869, affects certain Modicon M580 and M580 Safety controllers and carries a critical rating of 9.2 under CVSS version 4.0.

Industrial patching is harder than office IT patching. Controllers run continuous processes, updates may require downtime, and a failed firmware update can stop production. A workable approach is to subscribe to vendor and CISA advisories for the equipment you actually run, rank each advisory by whether the affected device is reachable from untrusted networks, apply compensating controls such as tighter segmentation immediately, and schedule firmware updates during planned maintenance under formal change control.

Manual Operation Is a Security Control

Federal guidance to water operators stresses the ability to run processes manually, along with tested backups, fail-safe mechanisms and standby systems. That advice applies equally to mines, factories and irrigation networks. An operation that can safely isolate its controllers and run by hand for a few days turns a potential crisis into an inconvenience. Practice it at least once a year, and document the steps in plain language that a new operator could follow.

A 30, 60 and 90 Day Plan for Small Operators

Small water systems, irrigation districts and single-site manufacturers rarely have a dedicated security team. A phased plan keeps progress realistic.

First 30 days. Complete the exposure audit above. Close any internet-facing controllers, change default credentials and disable remote access accounts that are no longer needed. Export and store offline copies of every PLC program and HMI configuration.

Days 31 to 60. Consolidate remote access into a single secure method with multifactor authentication. Write a one-page incident response plan that names who to call, including your controls integrator, your insurer and federal contacts such as CISA and the FBI. Run a tabletop exercise with operators using a realistic scenario, such as a pump station setpoint changing unexpectedly overnight.

Days 61 to 90. Begin separating the control network from business IT, even if the first step is just a properly configured firewall between them. Evaluate passive monitoring tools that can map assets and flag unusual commands. Add security requirements, such as unique credentials and documented remote access methods, to every new equipment purchase and integrator contract.

Free assessment services from CISA and resources from industry groups such as the water sector's information sharing center can help small operators without large budgets.

Regulation and Funding to Watch

  • America's Water Infrastructure Act already requires community water systems serving more than 3,300 people to complete risk and resilience assessments that cover their electronic and cyber systems.
  • CIRCIA incident reporting rules for critical infrastructure were expected to be finalized in September 2026. Utilities and industrial operators should review what reporting obligations may apply to them.
  • The Water Cyber Shield Act, introduced in Congress in August 2026, would authorize $300 million a year to help utilities fund cybersecurity upgrades and would require risk assessments and incident reporting. It is a proposal, not yet law, but it signals where federal policy may head.
  • Customer requirements from semiconductor, aerospace and defense buyers increasingly reference standards such as ISA/IEC 62443, which affects Arizona suppliers regardless of federal rules.

Where Industrial IoT Security Is Heading

The direction is clear. Buyers are asking for secure-by-design equipment, asset visibility tools are becoming standard in larger plants, and regulators are moving from voluntary guidance toward reporting obligations. For Arizona operators, the most valuable step remains the least glamorous one: knowing exactly what is connected, who can reach it, and how to run without it. Operations teams in Phoenix, Chandler and Tucson looking for OT security and industrial IoT integrators can start with the IoT Arizona company directory.

Related articles

Top