On-demand course · Start anytime
Getting Started in OT/ICS Cybersecurity — now on demand
With Mike Holcomb · Self-paced, with hands-on labs
Learn to protect our families, friends, and communities — the fundamentals of industrial control system security, at your own pace.
Get started today →
For informational purposes only. This dashboard is a curated awareness aid, not authoritative guidance, legal advice, or a substitute for vendor advisories, official CVSS/CISA KEV data, or a professional risk assessment of your environment. Severity and exploitation indicators are editorial aids that may be incomplete or change after generation — always verify against the linked primary sources before acting. Owner and status notes you enter are stored only in your own browser.

Free OT/ICS Cybersecurity Threat Intel You Can Use

What could impact your environment? And how would you prevent it?
Generated Thu, 19 Nov 2026, 11:27 AM ET • Sector: All Critical Infrastructure
18 stories across 4 categories
7.0/ 10
Overall Threat Level High
Why 7.0 (High): State-attributed sabotage of refrigeration controllers across many European countries and several sectors holds the level at the floor of High; no new attack wave has been reported since early November.
Top threat: Internet-reachable controllers and HMIs, especially unpatched Danfoss AK-SM 800A and end-of-life Copeland XWEB EVO units.
Confirmed OT attack: Setpoint tampering at hundreds of supermarkets and French blood-service sites; France blames the IRGC and expects EU sanctions on 14 December.
Also watching: PHP2Shell and PHP’s seven new critical fixes; Osaki meter halt; Santos port; Equinor IT attack.
What would raise it: A new attack wave, or confirmed disruption at several power, water or gas operators.
Top Story

France expects EU sanctions on 14 December over Iran’s refrigeration sabotage as Iran-linked hackers turn to physical attacks

France’s foreign minister said on 17 November he expects EU foreign ministers to agree sanctions on 14 December against the people behind October’s sabotage of supermarket refrigeration controllers, freezing their assets and barring travel, a day after EU foreign policy chief Kaja Kallas confirmed new Iran sanctions are being prepared. Paris blames the IRGC’s Shahid Kaveh unit for the attack on about 700 French sites, which French authorities say caused at least 15 fires, and has sought arrest warrants for three officers; Iran rejects the accusations. Health-ISAC warned on 16 November that settings were also changed at French blood-service sites, putting donor blood and therapies at risk. US and Israeli officials have told the Wall Street Journal that Iran-linked hackers also sabotaged equipment at small Midwest water stations and aboard two tankers. For OT defenders the lesson is plain: any internet-reachable controller is now a proven target.

Confirmed attacks, state attribution — Confirmed vs claimed: the WSJ account of water-station lockouts and tanker network breaches rests on unnamed US and Israeli officials, and US officials said in September they were investigating possible Iranian involvement in the tanker incidents (no formal US attribution); Check Point links the activity mainly to the IRGC-affiliated CyberAv3ngers; the refrigeration attacks are confirmed, and France’s IRGC/Shahid Kaveh attribution and the Paris prosecutor’s warrant request (11 Nov, reported by RFI) are official French steps, not court findings; Belgium’s interior minister says Belgian evidence points to Iran but explicitly not as an official attribution; Health-ISAC’s 16 Nov bulletin is a sector warning, not a new incident; Iran’s Foreign Ministry rejects the accusations, and on 14 Nov an IRGC spokesman dismissed the French findings (Iran International); France’s request for EU sanctions, its expectation of a 14 Dec decision and Barrot’s 17 Nov France 5 remarks that sanctions (asset freezes, travel bans) could come within a month are the foreign minister’s own statements (reported by Asharq Al-Awsat, The New Arab and APA, which notes the attribution has not been independently confirmed), and on 16 Nov EU foreign policy chief Kaja Kallas confirmed further sanctions are being prepared (dpa), with no targets, timing or EU decision yet announced; the BSI and CCB warnings of 13 Nov are official agency statements, and the six AK-SM 800A flaws are Midnight Blue’s research with no exploitation of them reported No CVE confirmed as the entry route; AK-SM 800A CVEs pending; not in CISA KEV
No single patch — remove internet exposure, change credentials, replace end-of-life controllers Action: Treat Iranian-state activity as the planning case for every internet-reachable controller: water and pumping PLCs, refrigeration, HVAC, small hydro and vessel networks. Take web-managed controllers and HMIs off the internet, put remote access behind a VPN with multi-factor authentication, change default and shared passwords, and alarm on setpoint, defrost and mode changes. Keep process or temperature monitoring that does not depend on the controller, rehearse manual operation, and preserve logs before any reset.
Suggested SLA: Internet-exposure removal — 24 hours; credential reset and remote-access restriction — 72 hours; setpoint-change alerting, independent monitoring and a manual-operation check — 7 days Owner:
Arab News, from AFP (17 Nov 2026, Barrot: EU decision expected 14 Dec); APA (18 Nov 2026, Barrot on France 5: sanctions within a month); dpa, via Yahoo News (16 Nov 2026, Kallas: EU sanctions in preparation); Asharq Al-Awsat and The New Arab (16 Nov 2026, French sanctions push); Health-ISAC (16 Nov 2026, cold-chain bulletin); Wall Street Journal (13 Nov 2026), via Newsmax wire on Yahoo News and Voice of Emirates; RFI via AOL (11 Nov 2026, Paris prosecutor’s warrant request); The Record (9 Nov 2026, French attribution and at least 15 fires); Insurance Journal, from Reuters (13 Nov 2026, BSI warning); Bytes Europe (13 Nov 2026, CCB warning); Midnight Blue (Nov 2026, AK-SM 800A research); GBHackers (13 Nov 2026); NPR (9 Nov 2026, Iranian denial); Iran International (14 Nov 2026, IRGC response); Arab News, from AFP (12 Nov 2026, Belgian statement) • Barrot: EU sanctions within a month 17–18 Nov 2026; EU confirms sanctions in preparation, French sanctions push and Health-ISAC bulletin 16 Nov 2026; WSJ report 13 Nov 2026; BSI and CCB warnings 13 Nov 2026; warrant request 11 Nov 2026; French attribution 9 Nov 2026; IRGC rejects French findings 14 Nov 2026; October attack 11–12 Oct 2026; investigations ongoing
Read source
Incidents & Attacks
Critical Incident — CISA/FBI/HHS/USDA/DOT joint warning (5 Nov 2026) and a second wave of refrigeration attacks across about 11 European countries (1–4 Nov); Belgium says its evidence points to Iran (12 Nov), no formal attribution

CISA and FBI warn of an ongoing threat to internet-connected refrigeration as European supermarket attacks reach at least 11 countries

Hackers are tampering with internet-connected refrigeration controllers in European supermarkets, and on 5 November CISA and the FBI, with HHS, USDA and DOT, warned the threat is ongoing and also reaches healthcare, chemical, transport and cold-storage operations. Hundreds of French stores were hit in October; a second wave on 1–2 November reached about 11 countries, forcing units into continuous heating or defrost, and three French blood-service sites had settings changed with no blood lost. On 10 November Sweden warned that more incidents are likely after refrigeration was tampered with at seven Coop stores and an undisclosed number of ICA stores on 2 November; its NCSC says the victims mainly ran older systems from one manufacturer protected by weak passwords. On 12 November Belgium’s interior minister said evidence on the Belgian attacks points to Iran but stopped short of an official attribution (see top story); a pro-Russian claim is unverified, and France has formally attributed only the separate 12 October attack, to Iran’s Revolutionary Guard. Exposure is falling but not gone: exposed Danfoss StoreView instances dropped from 3,004 to 708 between 9 October and 5 November (The Hacker News, 9 November). Sekoia reported on 10 November that the second wave used a non-public, unauthenticated flaw that renames the controller’s admin account, apparently a step towards resetting its password, and assesses that both waves may come from the same actor. If a controller is reachable from the internet, treat it as at risk today.

Confirmed attacks — Confirmed vs claimed: CISA and the FBI (5 Nov) confirm hackers are compromising internet-connected refrigeration and cold-chain monitoring and name no actor; Copeland confirmed on 4 Nov that its xweb controllers were targeted; officials confirmed Germany, Romania and the UK on 4 Nov, for about 11 countries; Belgian prosecutors are investigating. The pro-Russian claim (NoName057(16), Z-Pentest, 5 Nov) is unverified, and SentinelOne rates Russian involvement credible but unproven. France formally attributed its 12 October attack to Iran’s IRGC on 9 Nov (see top story); no government has formally attributed the November wave or the US commissary freezers, though on 12 Nov Belgium’s interior minister said Belgian evidence points to Iran (not an official attribution). ANSSI told the French Senate the French cases pointed to exposed administration interfaces and weak passwords rather than the Danfoss flaws. No CVE confirmed as the entry route (earlier-disclosed flaws exist in these products, including Danfoss CVE-2025-41450/-41451/-41452 and Copeland CVE-2026-25085/-21718/-24663); not in CISA KEV; CERT-FR alert CERTFR-2026-ALE-012 covers Danfoss AK-SM/AK-SC, Copeland and Dixell xweb
No fix for end-of-life controllers — isolate or replace them; supported units should run current firmware Action: Take every web-managed refrigeration controller and cold-chain monitor off the internet tonight (Danfoss AK-SM/AK-SC, Copeland and Dixell xweb first). Allow remote access only through a VPN with multi-factor authentication, change default passwords, check defrost durations and setpoints on every case, and alarm on temperature with monitoring that does not depend on the controller. Ask your refrigeration contractor in writing which sites it reaches over the internet. Keep logs and configurations before any reset, and never re-expose an end-of-life unit.
Suggested SLA: Internet-exposure removal — 24 hours; defrost and setpoint audit plus password change — 72 hours; independent temperature alerting — 7 days; replacement plan for end-of-life controllers — 30 days Owner:
TechCrunch (5 Nov 2026, CISA/FBI joint statement); SentinelOne Labs (3 Nov 2026, updated 4 Nov); Cybersecurity Dive (3 Nov 2026, updated with 4 Nov developments); Unit 42 (6 Nov 2026, exposure counts); Censys (6 Nov 2026, exposure analysis); BleepingComputer (5 Nov 2026); Nextgov (29 Oct 2026); Al Jazeera (4 Nov 2026); CERT-FR CERTFR-2026-ALE-012; The Cyber Express (6 Nov 2026, CISA/FBI/HHS/USDA/DOT advisory summary); Industrial Cyber (6 Nov 2026); Help Net Security (6 Nov 2026); SecurityWeek (6 Nov 2026, hardening guidance); The Hacker News (9 Nov 2026, exposure trend); eBuilder Security (11 Nov 2026, Swedish government and NCSC warning); Arab News/AFP (12 Nov 2026, Belgian statement); Sekoia TDR (10 Nov 2026, second-wave technique) • Attacks overnight 1–2 Nov 2026; Germany, Romania and UK confirmed 4 Nov 2026; CISA/FBI joint warning 5 Nov 2026; French attribution of the October attack 9 Nov 2026; Swedish government warning 10 Nov 2026; Belgian minister points to Iran 12 Nov 2026 — investigations ongoing
Read source
Critical Incident — PHP2Shell plus Gaia root flaw CVE-2026-123039 used to backdoor Check Point gateways and wipe a VMware ESXi host (wave 1 from 30 Oct, Israel; wave 2 from 2 Nov, multiple countries); CVE-2026-123039 added to CISA KEV 13 Nov 2026

Attackers rooted unpatched Check Point gateways through PHP2Shell, planted backdoors and wiped a VMware host; the root flaw is now in KEV

Check Point Research said on 12 November that attackers exploited the PHP2Shell flaws on unpatched Check Point Mobile Access portals from 30 October, about a week after fixes shipped, then used a local flaw in the gateway’s DynamicCLI service (CVE-2026-123039) to become root. They planted web shells and backdoors named TSGA and TSProxy, scanned the internal network, moved over SSH to a VMware ESXi host and ran a wiper that overwrites and deletes files. The first wave hit Israeli organizations, some destructively; a second wave from 2 November reached gateways in several countries and sectors with no destruction seen. The backdoors resemble tooling linked to the China-nexus group UNC5221, but Check Point does not attribute the campaign with confidence. CISA added CVE-2026-123039 to KEV on 13 November. No OT victim is reported, but these firewalls often sit at the IT/OT boundary and ESXi hosts often run HMIs and historians (editorial assessment).

Exploited in the wild — Confirmed vs claimed: the attack chain, backdoors and ESXi wipe are Check Point Research’s own incident findings; Check Point confirms CVE-2026-123039 is exploited and CISA lists it in KEV; victims are unnamed and no count is given; the China-nexus link is a tooling resemblance, and Check Point raises false-flag and access-broker scenarios; no OT impact is reported In CISA KEV — CVE-2026-123039 added 13 Nov 2026; PHP2Shell CVE-2026-109618 and CVE-2026-109619 added 26 Oct 2026
Patch now — Check Point fix for CVE-2026-123039 (sk1000362; Gaia R80.30 to R82.20 affected per CCCS AV26-1154) plus the PHP2Shell updates Action: Patch Check Point gateways and management servers, and keep Mobile Access and Gaia portal interfaces off the open internet where you can. If a portal was exposed and unpatched after 21 October, assume compromise: look for zz*.tpl files in the portal template directory and unfamiliar daemons, rebuild rather than clean, rotate every credential the gateway held, and check any ESXi host it could reach over SSH. Confirm you have offline backups of virtualized HMIs, historians and engineering workstations.
Suggested SLA: Patch and restrict portal exposure — immediately (actively exploited, in KEV); compromise hunt on gateways exposed before patching — 72 hours; offline-backup check for virtualized OT hosts — 7 days Owner:
Check Point Research (12 Nov 2026); SecurityWeek (13 Nov 2026); Canadian Centre for Cyber Security AV26-1154 (12 Nov 2026, updated 13 Nov); CISA KEV alert (13 Nov 2026); BleepingComputer (Nov 2026) • Wave 1 from 30 Oct 2026; wave 2 from 2 Nov 2026; research published 12 Nov 2026; KEV addition 13 Nov 2026
Read source
Critical Active exploitation — PHP2Shell chained with a Linux kernel flaw to root exposed PAN-OS firewalls, 23–24 Oct; OT vendor advisories 28–30 Oct; Siemens adds metering gateways 16 Nov

PHP2Shell attacks rooted about two dozen Palo Alto firewalls, and Siemens, Schneider and ABB now list grid-control, DCS and RTU products, several with no fix

Palo Alto’s Unit 42 verified on 29 October that a suspected China-nexus actor chained the PHP2Shell flaws (CVE-2026-109618 and CVE-2026-109619) with Linux kernel bug CVE-2026-46300 to gain root on about two dozen internet-exposed PAN-OS firewalls on 23–24 October, then stole Active Directory credentials. Victims were in the US, Japan, Taiwan and South Korea. The OT exposure keeps widening: Siemens lists Spectrum Power grid-control systems and AMIS TS, and on 16 November added its WTV676 and WTV776 metering gateways (all versions, no fix), Schneider lists a Foxboro DCS server, and ABB lists Netcontrol RTUs and ASPECT gateways, several with no fix yet. Attribution is suspected, not confirmed, and no Siemens, Schneider or ABB product is reported exploited. No OT operator has been named, so treat this as an IT-to-OT boundary warning.

Exploited in the wild — Confirmed vs claimed: the root compromises are Dream’s findings, verified by Unit 42, and Palo Alto confirms exploitation of exposed PAN-OS management interfaces; the China-nexus attribution is suspected, not confirmed; victims are unnamed; the affected OT products come from Siemens’, Schneider’s and ABB’s own advisories, and none of them is reported exploited In CISA KEV — CVE-2026-109618 and CVE-2026-109619 added 26 Oct 2026 (federal deadline 29 Oct); Linux CVE-2026-46300 (CVSS v3.1 7.8, Red Hat) added 28 Oct 2026 (deadline 31 Oct), as of CISA’s 30 Oct catalog
Fixes: PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12 (21 Oct); all PAN-OS hotfixes out by 29 Oct; APE1808 via Siemens support; Siemens Spectrum Power 3, 7 and TG and Energy Engage V3.1SP1 via PHP or Red Hat updates; Schneider Control Engineering remediation and Security Expert 1.48.4.0. No fix: Spectrum Power 4, AMIS TS, WTV676/WTV776 metering gateways, blueplanet 360, Energy Engage V2.0SP9, Foxboro DCS H90 (block ports), ABB Netcontrol/NAM, ASPECT and Arctic (never); ABB APROL patch not yet published Action: Take PAN-OS and RUGGEDCOM APE1808 management interfaces off the internet, restrict them to a jump host and apply the hotfixes; if one was exposed before patching, hunt for web shells and root-level changes and reset the Active Directory credentials it could reach. Ask Siemens which Spectrum Power, AMIS TS, Energy Engage and WTV metering-gateway components you run, and keep no-fix web and monitoring components reachable only from a management network. Block TCP 2301 and 2381 to Foxboro DCS H90 servers; keep ABB RTUs, NAM and Arctic gateways off the internet, reach their web interfaces only over VPN from a dedicated host, and plan replacement of the Arctic units. Get every other OT vendor’s PHP2Shell position in writing.
Suggested SLA: Restrict exposed PAN-OS / APE1808 management interfaces — immediately (actively exploited); compromise hunt on any device exposed before patching — 72 hours; OT vendor inventory and isolation of no-fix products — 7 days; patch where fixes exist — 7 days Owner:
Unit 42 (updated 29 Oct 2026); Palo Alto Networks advisory for CVE-2026-109618 (updated 29 Oct 2026); The Record (29 Oct 2026) and Infosecurity Magazine (30 Oct 2026), citing Dream; CISA KEV catalog (30 Oct 2026 release); Siemens SSA-166980 V1.4 (16 Nov 2026, WTV676/WTV776 added; V1.2 29 Oct 2026), SSA-566512 V1.1 (28 Oct 2026), SSA-019113 and SSA-082556; Schneider Electric SESB-2026-295-01 v3.2.0 (30 Oct 2026); ABB Netcontrol and Arctic advisories (30 Oct 2026), ASPECT advisory (29 Oct 2026) and APROL SA26P015 (23 Oct 2026); CERT@VDE VDE-2026-127 and VDE-2026-137 • Root compromises 23–24 Oct 2026, verified by Unit 42 29 Oct 2026; KEV additions 26 and 28 Oct 2026; Siemens, Schneider and ABB updates 28–30 Oct 2026; Siemens metering gateways added 16 Nov 2026
Read source
High Incident — cyberattack forced Chile’s 103 MW Huatacondo solar plant and its battery system off the grid (attack 26 Aug 2026, forced disconnection 27 Aug); still offline per the 14 Nov 2026 grid-coordinator report; congressional information requests filed 11 Nov 2026; no attribution

A Chilean solar-and-battery plant is still off the grid nearly three months after a cyberattack, and lawmakers want answers

The 103 MW Huatacondo solar plant in Chile’s Tarapacá region, with a 98 MW / 312 MWh battery system still in commissioning, has been disconnected from the national grid since late August after a cyberattack. Chile’s National Electric Coordinator triggered its disconnection protocol on 27 August after the owner reported the attack, and its 14 November daily report still lists both assets at zero availability under forced outage. The coordinator calls the case exceptional and is withholding details while it investigates. On 11 November a member of Congress asked the security and energy ministries whether the national cybersecurity agency was notified as Chilean law requires and which control systems were hit; no answer had been published by 16 November. The owner, entry route and affected systems are undisclosed. Two suspected attacks on plants in Coquimbo the next day were reportedly ruled out. For renewables operators, the lesson is how long a plant stays dark once it is pulled off the grid for safety and cannot be restored with confidence (editorial assessment).

Confirmed outage, details withheld — Confirmed vs claimed: the grid coordinator’s operational records attribute the forced disconnection to a cyberattack and its cybersecurity director confirmed the protocol was activated; no technical findings, owner name, attacker or affected systems (SCADA, inverters, protection or battery management) have been published; the questions about those systems come from lawmakers’ information requests, not from findings; ransomware is not reported No CVE or entry route disclosed; not linked to a CISA KEV entry
No patch — incident response and recovery planning Action: Solar, wind and battery operators: map every remote path into plant SCADA, inverter and battery-management systems (vendor portals, O&M contractors, cellular modems), put them behind MFA and a single monitored gateway, and keep known-good offline copies of controller, inverter and protection settings. Agree in advance with your grid operator what evidence you need to show before a plant disconnected for a cyber incident can reconnect.
Suggested SLA: Remote-access inventory for renewable and storage sites — 14 days; offline configuration backups — 30 days; reconnection-criteria discussion with the grid operator — 60 days Owner:
ESS News / pv magazine (17 Nov 2026, citing Coordinador Eléctrico Nacional records); T13 (16 Nov 2026, in Spanish); pv magazine Latin America (16 Nov 2026, congressional requests, in Spanish) • Ongoing — still offline per 14 Nov 2026 coordinator report; congressional requests 11 Nov 2026; reported 16–17 Nov 2026; attack 26 Aug 2026
Read source
High Incident — Ongoing cyberattack on certain IT systems at Norway’s Equinor, disclosed 17 Nov 2026; company update 18 Nov 2026 says it is not self-spreading malware and production continues as normal; internal email reportedly down (Reuters, 18 Nov); no attribution

Equinor says the attack on its IT systems is not self-spreading and production continues normally, but gives no recovery timeline

Equinor, Norway’s state-controlled energy company and the largest supplier of pipeline gas to the EU, disclosed on the evening of 17 November that it was fighting an ongoing cyberattack against certain IT systems. In an update on the morning of 18 November it said it now has a clearer picture of how the attack was carried out and which systems are affected, that the attack is not a virus and cannot spread on its own, and that it has found no effect on employees, partners or suppliers. Staff may have trouble reaching corporate applications and IT services, and Reuters, citing an unnamed source, reported that internal email was down. Oil and gas production continues as normal and the company still reports no sign of data theft. Work to remove the attackers and restore systems continues with national security authorities, and Equinor says it is too early to give a timeframe. It has not disclosed the entry route, the systems involved or the attacker. Nothing reported points to OT, but an active intrusion at a major upstream and gas-export operator is exactly when IT-to-OT boundaries get tested (editorial assessment).

Confirmed attack on IT systems — Confirmed vs claimed: Equinor confirms an ongoing attack on certain IT systems, no production impact and no sign of data theft, and on 18 Nov said the attack is not a self-spreading virus and has not affected employees, partners or suppliers; NSM confirms it is in contact with the company; Havtil and the Police Security Service (PST, per NRK) were notified; entry route, malware and attacker are not disclosed; social-media claims of a wider run of incidents at Norwegian targets are unverified; the email outage is Reuters’ single-source report No CVE disclosed; not linked to a KEV entry
Not a patch issue — containment and IT/OT boundary control Action: Energy operators should treat this as a prompt to check the IT/OT boundary now: confirm which IT-side accounts, jump hosts and file transfers can reach production networks, be ready to cut those paths during an IT incident, and hunt for new remote-access tools and unusual logins on DMZ and historian hosts. Confirm that production can run safely if corporate IT is isolated for days.
Suggested SLA: IT/OT conduit review and isolation plan — 7 days; DMZ and jump-host hunt — 14 days Owner:
Equinor statement (17 Nov 2026, 18:55 CET; update 18 Nov 2026, 09:47 CET); The Record (18 Nov 2026, internal services disrupted, citing Reuters); IBTimes UK (17 Nov 2026, citing NTB, NSM and NRK); Euronext/Reuters wire (17 Nov 2026); The Star, from Reuters (18 Nov 2026) • Disclosed 17 Nov 2026; company update 18 Nov 2026; attack still being removed
Read source
High Incident — Ransomware at Japanese smart-meter maker Osaki Electric (confirmed 17 Nov 2026); production and shipments suspended at its Saitama centre and group plants (reported 18 Nov 2026); no group named

Ransomware halts smart-meter production and shipments at Japan’s Osaki Electric

Osaki Electric, a Japanese maker of electricity smart meters, said ransomware encrypted data on its servers on 17 November. It confirmed the attack at about 10:35 a.m. local time, cut its systems off from outside networks around midday, and suspended production and shipments of smart meters and other products at its Saitama R&D and manufacturing centre and at group production companies Iwate Osaki Electric and Osaki Platech. NHK reported on 18 November that the production-management system was among the systems knocked out. Outside specialists are checking whether data was stolen, and the company has informed police and customers. No group has claimed the attack and the entry route is not disclosed. Nothing reported suggests meters already in the field or electricity supply are affected. For utilities, the risk is supply-chain: delayed meter rollouts, and the question of how a supplier protects the systems that build, configure and sign the devices it ships (editorial assessment).

Confirmed ransomware, production halted — Confirmed vs claimed: the ransomware, the shutdown of production-related systems and the suspension of production and shipments are Osaki Electric’s own disclosure (via TipRanks) and NHK’s report; any data theft is still under investigation; no ransomware group or attacker is named; no effect on installed meters or power supply is reported No CVE or entry route disclosed; not linked to a CISA KEV entry
Not a patch issue — supplier risk and IT/OT separation at manufacturing sites Action: Utilities and metering teams: ask Osaki and other meter and field-device suppliers in writing whether firmware-build, code-signing, key-provisioning and remote-update systems were touched, and hold new firmware or configuration pushes from an affected supplier until it confirms they are clean. Check delivery dependencies for rollout schedules. Manufacturers: make sure plant execution and production-management systems can run, or fail safe, if the corporate network has to be cut off.
Suggested SLA: Supplier integrity questions and firmware-push hold — 7 days; rollout dependency review — 14 days; production-system isolation test — 30 days Owner:
Osaki Electric announcement, via TipRanks (17 Nov 2026, updated 18 Nov 2026); NHK (18 Nov 2026, in Japanese); Kyodo, via Yahoo! Japan News and Tokyo Shimbun (18 Nov 2026, in Japanese) • Attack confirmed 17 Nov 2026; production and shipments still suspended per 18 Nov 2026 reports
Read source
High Incident — Cyberattack on the Santos Port Authority (APS), Brazil; systems down from 6 Nov 2026, attack confirmed 10 Nov; port security raised to level 2 of 3 (8 Nov); core systems in final tests 16 Nov 2026; about 70% of backups recovered; Federal Police inquiry opened 10 Nov; no attribution

Cyberattack on Brazil’s Santos port authority forces manual workarounds at Latin America’s busiest port

The authority that runs the Port of Santos, Brazil’s largest port, lost its IT systems on 6 November after a power fluctuation hit its servers, and on 10 November confirmed the outage was a cyberattack. Access-control and identification systems and digital tools used to coordinate port operations went down, so vessel, truck and train procedures were delayed and some automated checks, such as matching ship dimensions to berths, were done by hand. On 8 November São Paulo’s port security commission raised the port’s protection level to 2 of 3, adding police presence. Internet and phones were back on 9 November, and on 16 November the authority said its main internal systems were in final tests, with some services still running by email and about 70% of affected file backups recovered. Ship movements and landside access continued throughout. Brazil’s Federal Police are investigating; the authority has not said who was behind it, how they got in or whether data was taken. For port and terminal operators, the lesson is that access control and berth planning are operational systems that need a tested manual fallback (editorial assessment).

Confirmed attack, operations degraded — Confirmed vs claimed: the cyberattack, the security-level increase and the restoration timeline are the port authority’s and São Paulo officials’ statements (via DatamarNews and The Rio Times); a ransom demand was reported by local media (A Tribuna) but not confirmed by the authority; attacker, entry route and any data access are undisclosed; terminal operators’ own systems are not reported affected; CNN Brasil’s report that malware was already on the network before the 6 November power event and activated afterwards is unconfirmed by the authority (via CyberDelegate) No CVE or entry route disclosed; not linked to a CISA KEV entry
Not a patch issue — resilience, access-control fallback and recovery Action: Port, terminal and logistics operators: list which operational steps (gate and access control, berth planning, vessel and rail scheduling) stop when the port-community or authority IT systems go down, write and drill the manual procedure for each, and keep offline copies of access lists and berth data. Check that backups of access-control and port-management servers are offline and restorable, and that power events on server rooms are logged so a cyberattack hiding behind an outage is spotted early.
Suggested SLA: Manual-fallback inventory for access control and berth/vessel scheduling — 14 days; offline-backup restore test — 30 days; tabletop of a multi-day port-system outage — 60 days Owner:
The Rio Times (16 Nov 2026, status update citing the Santos Port Authority); DatamarNews (10 Nov 2026, updated 11 Nov, citing A Tribuna); CyberDelegate (17 Nov 2026, citing Folha de S.Paulo, CNN Brasil and Agência Brasil); Interlira Reports (17 Nov 2026) • Outage from 6 Nov 2026; security level raised 8 Nov 2026; attack confirmed 10 Nov 2026; core systems in final tests and ~70% of backups recovered 16–17 Nov 2026; investigation ongoing
Read source
Threat Intelligence & Research
Medium Government threat assessment — DHS Secretary’s written testimony to the House Homeland Security Committee (18 Nov 2026); DNI and DHS tell the same hearing recent US outages were not cyberattacks

DHS tells Congress Iran-backed hackers have stepped up attacks on US water, energy and transport since February, while officials rule out hacking in last week’s outages

In written testimony for a House Homeland Security Committee hearing on 18 November, Homeland Security Secretary Markwayne Mullin said Iranian state-sponsored groups and pro-Iranian criminals have targeted US critical infrastructure since the conflict with Iran began in February, with transportation, healthcare, water, energy and financial services increasingly in their sights. He described the attacks so far as mostly localized, low-damage disruptions of poorly secured industrial control systems, but warned that weak systems and poor cyber hygiene could have devastating consequences. At the same hearing the Director of National Intelligence and DHS said they found no evidence that hackers caused last week’s Microsoft 365 outage, the nationwide FAA ground stop or other recent disruptions, which officials tie to software defects and upgrade failures. For OT owners, the official US view now matches France’s: Iran is going after the weakest exposed controllers.

Official assessment — Confirmed vs claimed: the targeting statement is the DHS Secretary’s written testimony as reported by the Jerusalem Post, Report.az and Bloomberg; it names sectors but no specific new incidents or victims; the “no evidence of a cyberattack” finding on the outages is the officials’ assessment (Mullin said he was 98% confident), with investigations continuing No CVE named; past Iranian ICS activity relied on exposed devices and default or weak passwords
Not a patch issue — exposure and hygiene Action: Treat the testimony as confirmation that small, exposed sites are the target: find every internet-reachable PLC, HMI and controller (including those managed by integrators), remove direct exposure, change default and shared passwords, and confirm you would notice an unauthorized setpoint or logic change. Separate “outage” from “attack” in incident plans so a vendor or upgrade failure gets the same rehearsed manual-operation response.
Suggested SLA: Exposure sweep and removal — 7 days; credential reset on remote-reachable controllers — 14 days; manual-operation and outage-response rehearsal — 60 days Owner:
Jerusalem Post (18 Nov 2026, Mullin written testimony); Report.az (18 Nov 2026); Bloomberg (18 Nov 2026); Federal News Network (18 Nov 2026, outages not a coordinated attack); Washington Examiner (18 Nov 2026, hearing) • Testimony and hearing 18 Nov 2026
Read source
Medium Research — Forescout Vedere Labs AI-assisted hunt across 10 embedded TCP/IP stacks (published 12 Nov 2026); Siemens confirms affected APOGEE, Desigo and TALON building-automation lines (reported 16 Nov 2026)

Forescout’s AI harness finds 99 flaws in embedded TCP/IP stacks in 90 hours, and Siemens confirms building-automation controllers are affected

Forescout Vedere Labs said on 12 November that an AI harness built on off-the-shelf models found 99 vulnerabilities in 10 embedded TCP/IP stacks, such as lwIP, Contiki and Ethernut, in about 90 hours, work it estimates would have taken a researcher nine months. Sixty-six were new and just over half of those rate high or critical, mostly memory-corruption bugs. Because these stacks are built into IoT and industrial devices, the flaws could reach hundreds of products; Siemens has identified affected APOGEE, Desigo and TALON building-automation controllers, and other vendors are still checking. One set of seven flaws, including fixed admin credentials, sits in a discontinued wireless access point whose maker no longer exists, so it will never be patched. No exploitation has been reported. The wider point for OT teams: attackers can now find bugs in old embedded code as cheaply as defenders can (editorial assessment).

No exploitation reported — Confirmed vs claimed: the flaw counts, timing and cost estimate are Forescout’s own research figures; Siemens’ affected product lines are as reported by Help Net Security; 24 of the 54 reported flaws were fixed at publication and the rest are under investigation; the “hundreds of products” reach is Forescout’s estimate Not in CISA KEV; CVE assignments in progress per maintainer
Partial — fixes in some stacks; watch Siemens and other vendor advisories; no fix for the discontinued access point Action: Ask device vendors, starting with building-automation and remote-I/O suppliers, which TCP/IP stack and version their firmware uses and when fixes will ship. Keep embedded controllers off routable networks they do not need, filter malformed traffic at the cell boundary where your firewalls allow it, and replace unsupported wireless access points in OT areas.
Suggested SLA: Vendor stack inquiry for building-automation controllers — 30 days; replacement plan for unsupported OT wireless gear — 90 days Owner:
Forescout Vedere Labs (12 Nov 2026), via Cybersecurity Dive (12 Nov 2026); Help Net Security (16 Nov 2026, Siemens affected lines) • Published 12 Nov 2026; Siemens product lines reported 16 Nov 2026
Read source
Medium Research — Dragos Industrial Ransomware Analysis for Q3 2026 (published 16 Nov 2026), covering July–September; Check Point October 2026 statistics (12 Nov 2026) for comparison

Dragos counts 1,266 ransomware attacks on industrial organizations in Q3, up 11%, and found no case of an operator touching a control system

Dragos said on 16 November that ransomware hit 1,266 industrial organizations between July and September 2026, up 11% on the second quarter, while the number of brands claiming industrial victims jumped from 70 to 99. Manufacturing took 69% of cases, followed by the ICS ecosystem of integrators, engineering firms and equipment makers (116) and transport and logistics (105); oil and gas logged 47. Qilin and The Gentlemen drove 29% of the total. Dragos saw no Q3 case of a ransomware operator manipulating a control system: production stopped because the IT, ERP and virtualization layers plants rely on went down, as when Fairlife reportedly halted all four of its US plants for about 11 days. Entry came through edge devices and enterprise applications exploited within days of disclosure, and through stolen VPN and firewall credentials. Check Point separately counted a record 1,063 claimed victims across all sectors in October.

Statistical research — Confirmed vs claimed: counts are Dragos’s tally of leak-site claims and public reporting, so they largely reflect groups’ own claims; the Fairlife production halt and the Anubis claim are as reported by Dragos; Check Point’s October figures are likewise leak-site claims No single CVE — Dragos cites quickly exploited VMware vCenter, JetBrains TeamCity and SonicWall SMA 1000 flaws as entry routes
Not a single patch issue — edge-device patching and ransomware resilience Action: Patch internet-facing VPNs, firewalls and file-transfer or PLM servers within days of an exploited-flaw notice, and rotate VPN and firewall credentials that may have been harvested. Confirm the IT/OT boundary would hold if the business network were encrypted: no shared domain trust, no OT dependence on IT-hosted virtualization or ERP without a fallback, and offline, tested backups of PLC programs, HMI projects and historian configuration.
Suggested SLA: Exploited edge-device flaws — 72 hours; VPN/firewall credential rotation — 7 days; IT/OT dependency review — 30 days; offline OT backup test — 60 days Owner:
Dragos (16 Nov 2026); Australian Cyber Security Magazine (17 Nov 2026); Check Point Research October 2026 statistics, via iTWire (12 Nov 2026) • Published 16 Nov 2026; data covers July–September 2026
Read source
Critical Advisories
High Advisory — 14 flaws in end-of-life Copeland (Dixell) XWEB EVO refrigeration supervisors disclosed by VulnCheck; CVE records published 12 Nov 2026 (incl. CVE-2026-124010, CVE-2026-124014); exploitation attempts seen within hours; five flaws will not be fixed

Hackers probe 14 newly disclosed flaws in end-of-life Copeland XWEB EVO refrigeration controllers, five of which will never be fixed

VulnCheck has disclosed 14 vulnerabilities in Copeland’s XWEB EVO, the Dixell supervisory system that runs supermarket and cold-storage refrigeration, each of which gave its researcher root on test units. Nine affect only firmware built before a 2021 rewrite and include unauthenticated command execution and a hard-coded admin password. The other five reach the latest firmware: the daily admin password is derived from the device’s MAC address and the date, and the MAC address is visible without logging in, so an attacker can compute the password, turn on SSH and log in as root. VulnCheck’s sensors saw exploitation attempts against two older-firmware flaws within two hours of the 12 November CVE publication; it calls the sources opportunistic scanners, not the state campaign in France. Copeland ended XWEB EVO support on 16 March 2026 and will not fix the five current-firmware flaws; nearly 2,000 units are reachable from the internet. CyberScoop adds that XBOW honeypots posing as these controllers drew hundreds of requests and login attempts within a day, and someone changed the temperature on one simulated freezer.

Exploitation attempts observed — Confirmed vs claimed: the flaws and the probing are VulnCheck’s findings (as reported by SecurityWeek); no successful compromise through these specific flaws has been confirmed, and VulnCheck says the scanning hosts are not evidence of the IRGC-attributed French campaign, although CERT-FR named Copeland and Dixell XWEB among the controllers compromised there; the exposure count is from Onyphe data cited by VulnCheck CVE-2026-124010 and CVE-2026-124014 among 14 CVEs; not in CISA KEV
No fix — product end-of-life since March 2026; isolate and replace Action: Ask your refrigeration contractor which sites run XWEB EVO and whether any are reachable from the internet or a contractor modem. Take them off the internet today, allow access only through a VPN with multi-factor authentication, disable SSH, watch for configuration and setpoint changes, and plan migration to a supported supervisor (Copeland points to XWEB Pro). Keep temperature alarms that do not depend on the controller.
Suggested SLA: Internet-exposure removal — 24 hours; SSH disabled and access restricted — 72 hours; replacement plan for every XWEB EVO unit — 30 days Owner:
SecurityWeek (16 Nov 2026, VulnCheck research and exploitation telemetry; Copeland end-of-life notice); CyberScoop (13 Nov 2026, XBOW honeypot findings; Copeland statement); CERT-FR CERTFR-2026-ALE-012 • CVE records published 12 Nov 2026; probing 12–13 Nov 2026; reported 16 Nov 2026
Read source
High Advisory — Six pre-authentication remote-code-execution flaws in Danfoss AK-SM 800A (firmware up to 5.3.2), disclosed by Midnight Blue; Belgian CCB and German BSI warnings (13 Nov 2026), joined by Ireland’s NCSC; CVEs pending; no exploitation of these flaws reported

Six unpatched pre-login flaws in Danfoss AK-SM 800A refrigeration controllers prompt Belgian, German and Irish warnings to pull them off the internet

Amsterdam consultancy Midnight Blue has disclosed six stack buffer overflows in Danfoss AK-SM 800A system managers, the store-level controllers that run supermarket and cold-storage refrigeration, that allow remote code execution without logging in; one works even with “strict” session control turned on. All firmware up to 5.3.2 is affected and CVEs are still pending. The BSI says the 5.4.0 package released this month is not affected, but Midnight Blue says 5.4.0 predates its research and does not fix these bugs, so treat 5.4.0 as unconfirmed until Danfoss says otherwise. The researchers say an attacker could plant code that survives a factory reset or firmware update, or brick units, because the device does not appear to use secure boot; that is a stated possibility, not a demonstrated one. Belgium’s CCB and Germany’s BSI (13 November) and Ireland’s NCSC have all told operators that firmware updates, password changes and strict mode are not enough for internet-exposed units. Danfoss had published no advisory or fix date as of 16 November. No exploitation of these six flaws is reported.

No exploitation of these flaws known — Confirmed vs claimed: the six flaws are Midnight Blue’s findings, with a lab proof of concept on older firmware, and are the basis of the CCB warning; the BSI says it knows of no active exploitation of the newly reported flaws; the persistence and bricking scenarios are the researchers’ assessment; the wider refrigeration attacks are confirmed (see Incidents & Attacks), though ANSSI linked the French cases to exposed interfaces and weak passwords rather than specific Danfoss flaws CVEs pending; not in CISA KEV
No confirmed fix — 5.4.0 status disputed; removing internet exposure is the control Action: List every Danfoss AK-SM/AK-SC unit with your refrigeration contractor, including any reached through a contractor’s 4G modem, and record its firmware. Take any internet-facing unit off the internet or put it behind a VPN, private APN or tight IP allowlist, change default and shared passwords, and do not count on firmware or strict session control alone. Apply the same check to Copeland and Dixell controllers, keep temperature alarms that do not depend on the controller, and alert on defrost and setpoint changes.
Suggested SLA: Internet-exposure removal — 24 hours; password change — 72 hours; firmware update once Danfoss confirms a fix — 7 days after release, coordinated with your contractor Owner:
Midnight Blue (Nov 2026); The Hacker News (16 Nov 2026, CCB, BSI and Irish NCSC warnings; Danfoss status); Bytes Europe (13 Nov 2026, CCB warning); Cyber Press (13 Nov 2026); Insurance Journal, from Reuters (13 Nov 2026, BSI warning); Filstalexpress (13 Nov 2026, BSI firmware details) • Status re-checked 16 Nov 2026 (no Danfoss fix); CCB and BSI warnings 13 Nov 2026; research published Nov 2026
Read source
High Active exploitation — N-able N-central: 4EverAble2Shell exploited to plant miners (13 Nov 2026); N-central 2026.4 Hotfix 3 fixes 17 more CVEs and removes the Legacy API (16–17 Nov 2026)

N-able ships Hotfix 3 for 17 more N-central flaws after attackers planted miners on servers already running Hotfix 2

N-able released N-central 2026.4 Hotfix 3 on 16 November, which it calls a critical security update. It fixes 17 new CVEs, including authentication bypasses, missing authorization checks, path traversal leading to code execution and a syslog injection that runs commands as root, and it removes the Legacy API option that the actively exploited 4EverAble2Shell chain depends on. On-premises servers need the upgrade now; hosted servers update automatically, but every customer must also upgrade Agents and Probes, which N-able warns can otherwise be impersonated. The fix follows Huntback’s 13 November finding of cryptocurrency miners on 21 N-central servers, 19 of them on Hotfix 2. Remote control and Intune integration stay blocked for now. Many integrators manage plant-side Windows hosts through RMM tools, and a miner today can be a hands-on intruder tomorrow (editorial assessment).

Exploited in the wild — Confirmed vs claimed: Hotfix 3, its 17 CVEs and the Agent/Probe warning are N-able’s own release notes (16 Nov), as reported by The Hacker News; exploitation of 4EverAble2Shell is confirmed by Huntback’s findings, and the 21-server count is theirs and not independently verified; no exploitation of Agent2Shell or of the 17 new CVEs has been reported; no actor is named and no OT victims are reported New chains and Hotfix 3 CVEs not in CISA KEV (as of 17 Nov; five older N-central CVEs are in KEV)
Patch available — N-central 2026.4 Hotfix 3 for on-premises servers, plus Agent and Probe upgrades for every customer Action: Upgrade on-premises N-central servers to Hotfix 3 and upgrade every Agent and Probe. Because Hotfix 2 servers were compromised, hunt before you trust a patched server: look for jup.sh downloads, connections to 157.20.241[.]16, XMRig processes and new admin accounts or scripts. Ask every integrator and MSP whether N-central reaches OT-side hosts, and block RMM agents from plant networks unless the path is approved and monitored.
Suggested SLA: Hotfix 3 on internet-reachable servers — 24 hours; compromise hunt and Agent/Probe upgrades — 72 hours; RMM-to-OT path review — 7 days Owner:
The Hacker News (17 Nov 2026, Hotfix 3, citing N-able release notes of 16 Nov); The Hacker News (13 Nov 2026, citing Huntback and Previdian); The Hacker News (12 Nov 2026, new chains); SecurityWeek (13 Nov 2026); Tenable (10 Nov 2026) • Hotfix 3 released 16 Nov 2026; exploitation reported 13 Nov 2026; Able2Shell disclosed 9 Nov 2026
Read source
Medium Advisory — PHP security release, 19 Nov 2026: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (plus 8.6.0) fix seven critical flaws, each rated CVSS 9.2, incl. CVE-2026-115560, CVE-2026-129289 (PHP-FPM request smuggling) and CVE-2026-129496; two are incomplete-fix follow-ups to PHP2Shell CVE-2026-109619; no exploitation of the new flaws reported

PHP fixes seven critical flaws across every supported version, two of them gaps left by last month’s PHP2Shell patch

PHP’s maintainers shipped PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November, alongside the new 8.6.0, fixing seven critical flaws that The Hacker News lists at CVSS 9.2 each. The most worrying for internet-facing systems are CVE-2026-129289, a PHP-FPM request-smuggling bug that lets an unauthenticated attacker run PHP code when a front-end proxy keeps backend connections open, and CVE-2026-129496, a memory-corruption bug an unauthenticated attacker can trigger. SecurityWeek reports that two of the use-after-free fixes close scenarios the October PHP2Shell patch missed, though PHP says code execution has not been shown for those two; CVE-2026-115560 was publicly disclosed in October. No exploitation of the new flaws is reported, but PHP2Shell itself is now widely exploited and reached firewalls and OT products within days (see Incidents & Attacks), so expect another round of OT vendor advisories.

No exploitation of the new flaws reported — Confirmed vs claimed: the releases, the CVE list and the fixed versions are PHP’s own, as reported by The Hacker News and SecurityWeek; the CVSS 9.2 ratings are as listed by The Hacker News; the link to CVE-2026-109619 is PHP’s description, reported by SecurityWeek; which OT products embed affected PHP versions is not yet known CVE-2026-115560, -129182, -126714, -129289, -129474, -129481, -129496; none in CISA KEV (PHP2Shell CVE-2026-109619 is exploited)
Patch available — PHP 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36; vendor-embedded PHP depends on each OT vendor’s own update Action: Update PHP on the IT and DMZ servers you run yourself, starting with anything behind a reverse proxy using PHP-FPM. Add this release to the PHP2Shell questions you are already putting to OT vendors: which products embed PHP, which versions, and when their updates ship. Keep PHP-based web interfaces on OT products reachable only from a management network.
Suggested SLA: Internet-facing PHP servers — 7 days; OT vendor inquiry — 14 days; vendor updates — next maintenance window after release Owner:
The Hacker News (19 Nov 2026); SecurityWeek (19 Nov 2026); PHP maintainers’ pre-release notice (18 Nov 2026); Siemens, Schneider and ABB PHP2Shell advisories (Oct–Nov 2026) • Released 19 Nov 2026
Read source
Medium Advisory — CISA ICS advisory batch, 17 Nov 2026: Dorsett Controls InfoScan (ICSA-26-321-01, water sector, highest CVSS v3.1 8.1 / v4 8.5) plus Siemens republications incl. SIMATIC, SIMATIC WinCC, RUGGEDCOM APE1808, Mendix Studio Pro, Simcenter Femap, meta-iot2050, ROS# and the SIMATIC S7 Webserver API .NET library (ICSA-26-321-02)

CISA flags six flaws in Dorsett InfoScan water-utility SCADA and republishes a batch of Siemens advisories

CISA’s 17 November ICS release leads with Dorsett Controls InfoScan, a SCADA and telemetry platform tagged for the water and wastewater sector. Versions 1.45.0 and earlier carry six flaws, the worst a TLS certificate-validation weakness (CVSS v3.1 8.1) that could let an attacker in the network path intercept or tamper with traffic; the others include hard-coded encryption keys, a template endpoint with no authentication, and unauthenticated endpoints that leak system details. Dorsett fixed them in version 1.46. The rest of the batch republishes Siemens ProductCERT advisories, among them the SIMATIC S7 Webserver API .NET client library, where a path-traversal flaw needs version 3.3.61 and an information leak needs 3.3.62. CISA reports no known public exploitation of any of these.

No confirmed exploitation reported — Confirmed vs claimed: flaw details, affected versions and fixes are from the CISA advisories (as summarised by WindowsForum); the Siemens items are republications of advisories Siemens first published earlier (the .NET library advisory SSA-390352 dates from 13 Oct 2026) CVE-2026-117659 (InfoScan TLS validation); CVE-2026-85114 / CVE-2026-85115 (S7 .NET library); not in CISA KEV
Patch available — InfoScan 1.46; S7 Webserver API library 3.3.62 Action: Water utilities running InfoScan should upgrade to 1.46, confirm the server is not reachable from the internet, and check that telemetry links run over a VPN rather than relying on the application’s own TLS. Engineering teams should search their software builds for the Siemens S7 Webserver API NuGet package and move to 3.3.62, and match the other Siemens republications against the asset inventory.
Suggested SLA: Exposure check — 7 days; InfoScan and library upgrades — 30 days in the next maintenance window Owner:
CISA ICSA-26-321-01 (Dorsett Controls InfoScan) and ICSA-26-321-02 to -11 (Siemens); WindowsForum (17 Nov 2026, InfoScan and S7 .NET library summaries); Siemens ProductCERT SSA-390352 • Published 17 Nov 2026
Read source
Regulation & Policy
Info Guidance — NIST SP 800-82 Rev. 4 draft (released 21 Sep 2026); public comments close 30 Nov 2026; no CVE

Comments close 30 November on NIST’s draft rewrite of its OT security guide, which adds water, food, rail, maritime and building-automation coverage

NIST’s draft Revision 4 of SP 800-82, the US government’s main guide to operational technology security, is open for public comment until 30 November 2026. The draft reorganises the guide around Cybersecurity Framework 2.0, with risk management now led by the Govern function, and adds sector material for building automation, water and wastewater, food and agriculture, freight rail, maritime vessels, and industrial IoT connected to cloud services. It also expands guidance on asset management, network monitoring and detection, protecting system-management functions, and applying zero-trust principles. Many regulators, insurers and auditors use 800-82 as a reference, so its final wording can shape what operators are asked to show; the comment window is the chance for practitioners to flag guidance that would not work on a plant floor.

Open consultation — Confirmed vs claimed: the draft, its contents and the 30 November deadline are from NIST’s own publication page; the final text is not yet set No CVE — guidance item
No patch applies — standards and governance planning Action: Have your OT security lead skim the sections for your sector and the new asset-management and monitoring guidance, and send comments using NIST’s comment template before 30 November where the draft does not fit how your plant actually runs.
Suggested SLA: Review and submit comments — before 30 Nov 2026; gap check against the final text — 90 days after publication Owner:
NIST CSRC, SP 800-82 Rev. 4 initial public draft (21 Sep 2026); SecurityWeek (24 Sep 2026) • Forward-looking: public comments close 30 Nov 2026
Read source
Info Policy — Operational Technology Cybersecurity Coalition report “The Missing Pillar of AI Security: Critical Infrastructure Resilience” (published 17 Nov 2026); recommendations only; no CVE

OT industry coalition asks Washington to make keeping plants running through an attack a pillar of US AI security policy

The Operational Technology Cybersecurity Coalition published a report on 17 November arguing that US AI security policy should centre on keeping essential services running through a successful attack. Its 18 recommendations fall into three groups: close gaps in baseline cybersecurity rules without duplicating them and fund under-resourced operators; build an AI governance framework for OT and secure long-term access to AI-enabled defensive tools; and fund the Cyber Response and Recovery Fund and reconstitute the Cyber Safety Review Board. The coalition points to attackers using AI-generated scripts against industrial controllers and to long-known weaknesses such as internet-exposed controllers on outdated software. The recommendations are proposals from industry roundtables, not requirements, but they signal where OT vendors and operators will push lawmakers next.

Policy proposal — Confirmed vs claimed: the report, its date and its 18 recommendations are from the coalition’s own publication; none has been adopted by Congress or an agency No CVE — policy item
No patch applies — governance and resilience planning Action: Use the report’s assume-compromise framing to test your own plans: can each site keep its essential process running safely if IT and remote access are lost, and who decides when to switch to manual operation? Track whether funding for smaller operators or OT-specific AI guidance follows.
Suggested SLA: Leadership briefing — 30 days; run-through-compromise exercise — 90 days Owner:
Operational Technology Cybersecurity Coalition (17 Nov 2026); Industrial Cyber (18 Nov 2026); Security Boulevard (18 Nov 2026) • Published 17 Nov 2026
Read source