Issue 01 · November 2026Founding edition
Cover story · Global incident watch

When the freezer becomes the target

A campaign against internet-connected refrigeration hit grocery chains, cold stores, military bases and a blood bank in at least a dozen countries. What it teaches every asset owner about forgotten OT.

Advisory roundup14CISA ICS advisories covering 36 CVEs, 6 of them for Siemens products
KEV watch35vulnerabilities confirmed as exploited, 11 rated CVSS 9.0 or higher
GRC deskSecurity levels you can defend in front of an auditor
AwarenessSix habits that close the default-password door
www.cynapse.appThe monthly magazine for critical infrastructure security
Founding edition

Welcome to the first issue of CIPHER, the monthly magazine of CYNAPSE for critical infrastructure security.

CIPHER is the monthly magazine of CYNAPSE for the people who run and protect critical infrastructure. Every issue covers the incidents that shaped the month, the intelligence behind them, and the governance, risk and awareness work that follows. All articles are written by the CIPHER editorial team.

www.cynapse.app

CIPHER · Issue 01 · November 2026Founding edition · 02
In this issue

Why CIPHER

Critical infrastructure security has no shortage of news. What it lacks is a monthly read that connects what happened in the world to the decisions an asset owner, an engineer and a board have to make next.

CIPHER is that read. Every article in it is written by our editorial team. Each issue takes the month's real incidents and intelligence and explains the governance, risk and compliance work that follows, together with awareness material you can hand straight to your teams.

The name carries our brief. The C and I stand for critical infrastructure. The rest is what we cover: the people who run it, the hazards that threaten it, the evidence that proves it is protected and the resilience that keeps it running.

We will keep CIPHER short, factual and useful. If an article does not help you decide or act, it does not belong in these pages.

The CIPHER editorial team

CIPHER is published monthly by CYNAPSE.
Issue 01, November 2026. Founding edition.
Intelligence data in this issue comes from the CISA ICS advisory feed and the CISA Known Exploited Vulnerabilities catalogue as held in the CYNAPSE intelligence database on 16 November 2026. All articles are written by the CIPHER editorial team.

CIPHER · Issue 01 · November 2026Contents · 03
Global incident watch · Cover story

When the freezer becomes the target

This autumn, attackers spent weeks changing the temperatures inside internet-connected refrigeration. The losses were spoiled stock. The lesson reaches every device that runs a physical process and that nobody thinks of as OT.

What happened

Early in November, U.S. federal agencies led by CISA and the FBI, with the Departments of Agriculture, Health and Human Services, and Transportation, issued a joint warning about an ongoing campaign against internet-connected refrigeration and cold-chain monitoring systems. Grocery stores and cold-storage facilities were the main targets.

The warning came after several waves of similar attacks across the United Kingdom and Europe. Freezers and chillers were affected in at least a dozen countries. Units on U.S. military bases were hit, and so were refrigerated stores at a French blood bank, where the tampering was stopped before any blood supply was compromised.

The attackers raised temperatures until food spoiled. The agencies warned that units could also be driven into continuous heating and defrost cycles, with a risk of widespread inventory loss, equipment damage and fire.

Old equipment, open doors

Much of the affected equipment had been connected for remote monitoring and then left on the internet. Some of it no longer received security updates from its vendor. This is the pattern behind almost every OT incident of recent years: a device bought for its physical function, connected for convenience, and forgotten once support ended.

No government has formally attributed the campaign. For an asset owner, the attacker's identity matters less than the exposure that made the attacks possible, and that exposure is under the owner's control.

A controller that changes a temperature is a control system, whoever owns it and whatever it cost.CIPHER editorial
CIPHER · Issue 01 · November 2026Cover story · 04
Cover story · Continued

Why this is an OT story

A refrigeration controller is a small industrial control system. It reads sensors, drives compressors and defrost heaters, and keeps a physical process inside safe limits. When an attacker changes its setpoints, the consequence is physical and immediate. In a pharmacy, a vaccine store or a blood bank, it is also a safety event.

Few organisations list these units in their OT asset inventory. They sit with facilities teams, are maintained by contractors and are monitored through a vendor portal. That is exactly why they were reachable.

Facilities systems rarely appear on the control room's wall, until they fail.

The GRC gap

Most risk registers will not have a line for "cold-chain controller compromised". The scenario falls between facilities, IT and operations, and between the safety case and the security case. IEC 62443-3-2 asks for every asset that can affect the process to sit in a zone with a target security level. A unit that spoils product or starts a fire belongs in that analysis.

Questions for your board

  1. Do we know every internet-reachable device that controls a physical process, including facilities equipment?
  2. Which of them are past vendor support, and who owns the decision to replace them?
  3. Would a temperature excursion be caught by an independent alarm, or only by the device under attack?
  4. Is cold-chain loss in our risk register with an owner, a rating and a treatment?

Do this week

  • Remove refrigeration and building controllers from direct internet exposure; reach them through a managed remote access path.
  • Change default and shared passwords on controllers and vendor portals.
  • Apply available patches; plan to retire units that no longer receive updates.
  • Add an independent temperature alarm where product or safety is at stake.

Based on the mitigations in the joint U.S. statement.

12+countries with affected freezers and chillers
5U.S. agencies behind the joint statement
4mitigations in the statement: disconnect, change passwords, patch, retire
CIPHER · Issue 01 · November 2026Cover story · 05
Global incident watch · The month in brief

Two warnings worth reading twice

United Kingdom

NCSC: AI-enabled ransomware against national infrastructure is "highly likely"

The UK National Cyber Security Centre's annual report, State of the Cyber Nation, published on 3 November, judges it is "highly likely AI malware will be used in a ransomware attack on UK critical national infrastructure", possibly within two years.

The argument is not that AI invents new attacks. It is that long-neglected vulnerabilities can now be found and exploited at a scale defenders have not faced before. The government also announced £70 million for a new National Exposure and Real-Time Vulnerability (Nerv) Centre within the NCSC.

Why it matters: exposure management stops being an IT hygiene task and becomes a board-level control. The organisations that know what they expose, and fix it fastest, will be the ones AI-assisted attackers pass over.

United States

Revisited: the water utility lockouts now have a MITRE campaign ID

Utilities were locked out of their own controllers after PLC settings were changed from the internet.

MITRE ATT&CK for ICS now documents the summer's attacks on more than 30 municipal water and wastewater utilities in Minnesota as Campaign C0066. Starting on 27 July, the adversary reached internet-facing Rockwell Automation/Allen-Bradley MicroLogix PLCs and changed their IP addresses and passwords, locking operators out. The FBI and EPA reported similar activity in at least seven states.

The techniques mapped include default credentials, internet-accessible devices, loss of view and loss of control. Attribution remains unconfirmed.

Why it matters: the same exposure pattern as the cold-chain campaign. An ATT&CK ID means you can now map this scenario directly in your threat model and test your controls against it.

The thread that connects them

The refrigeration campaign, the water utility lockouts and the attacks on internet-exposed PLCs described in April's joint advisory AA26-097A share one pattern: devices that control a physical process, reachable from the internet. The published fixes start in the same place: take them off the internet and fix the credentials.

CIPHER · Issue 01 · November 2026Incidents · 06
Intelligence · Advisory roundup

14 ICS advisories, 36 CVEs

Every CISA ICS advisory published between 16 October and 15 November 2026. Check the products you run, then confirm your exposure before you schedule patches.

AdvisoryProductVendorPublishedCVEs
ICSA-26-307-01Subnet Solutions PowerSYSTEM CenterSubnet Solutions3 Nov2
ICSA-26-316-04Siemens RUGGEDCOM APE1808Siemens30 Oct1
ICSA-26-316-03Siemens Industrial Edge ManagementSiemens30 Oct1
ICSA-26-316-02Siemens Desigo, GridscaleSiemens30 Oct1
ICSA-26-300-01EPICS BaseThe EPICS Community27 Oct4
ICSA-26-302-03Hitachi Energy CoreTec ProductHitachi Energy27 Oct2
ICSA-26-302-02Hitachi Energy TRO600 series productsHitachi Energy27 Oct2
ICSA-26-302-01Siemens Mendix SAML ModuleSiemens26 Oct1
ICSA-26-316-01Siemens Building Automation and Energy ProductsSiemens26 Oct2
ICSA-26-316-05Siemens RUGGEDCOM APE1808Siemens23 Oct2
ICSMA-26-295-01InterSystems Corporation InterSystems IRIS for HealthInterSystems Corporation22 Oct1
ICSA-26-295-01Kiloview E3 NDI EncoderKiloview22 Oct9
ICSA-26-293-03Moxa AIG-302 ThingsPro EdgeMoxa20 Oct2
ICSA-26-293-01HMS Networks PEAK-System PCAN Windows driversHMS Networks20 Oct6

Most advisories

Siemens, with 6 advisories across RUGGEDCOM, Industrial Edge, Desigo, Mendix and building automation products.

Most CVEs in one

Kiloview E3 NDI Encoder: 9 CVEs in a single advisory. Broadcast and AV encoders often sit on operational networks unmanaged.

Energy grid

Hitachi Energy CoreTec and TRO600, and Subnet Solutions PowerSYSTEM Center. Substation teams should review all three.

CIPHER · Issue 01 · November 2026Intelligence · 07
Intelligence · KEV watch

The front door is still the remote access gateway

CISA added 35 vulnerabilities to its Known Exploited Vulnerabilities catalogue between 16 October and 15 November. 11 are rated CVSS 9.0 or higher. The group that should worry OT owners most is the remote access and edge products that sit between the internet and the plant.

35added to KEV in the period
11rated CVSS 9.0 or higher
8in VPN, remote support, firewall or gateway products
CVEProductWeaknessAddedCVSS
CVE-2026-76418Cisco Secure Firewall ASA / FTDRemote Access SSL VPN service29 Oct8.6
CVE-2026-118527Ivanti Connect SecureAuthenticated file upload via predictable filenames30 Oct4.3
CVE-2026-111357Ivanti Connect SecurePrivilege escalation in the dsinvoked broker30 Oct7.0
CVE-2026-19868SonicWall SonicOSSSLVPN authentication enforcement6 Nov7.5
CVE-2026-116606Barracuda Email Security GatewayUnauthenticated authentication bypass10 Nov9.8
CVE-2025-61624Fortinet FortiOSPath traversal16 Oct6.0
CVE-2026-102764BeyondTrust Remote SupportImproper validation in internal components16 Oct9.8
CVE-2026-114625VeloCloud Orchestrator (on-prem)Access to privileged internal functions23 Oct9.9

Why OT owners should care

Vendors and integrators reach plants through exactly these products. One exploited VPN appliance can undo a well-designed zone and conduit model, because it sits on the conduit itself.

Also on the list

Siemens Software Center (CVE-2026-110936), a DLL loading flaw on engineering workstations, and OpenSSH on musl-based Linux without PAM (CVE-2026-123158), common in embedded and appliance builds.

CIPHER · Issue 01 · November 2026Intelligence · 08
GRC desk

Security levels you can defend

Assigning a target security level to a zone takes an afternoon. Proving to an auditor that the zone meets it takes evidence most programmes never collect. Here is the chain that holds up.

Operators, engineers and auditors in one room: the test every security level must pass.

IEC 62443 gives asset owners a clear structure: partition the system into zones and conduits, assess the risk of each, set a target security level (SL-T), then show the achieved level (SL-A) meets it. On paper the structure is simple. In practice the evidence is where assessments fail.

Auditors rarely reject the target level itself. They reject the gap between the target and the proof. A zone marked SL-2 with no record of which foundational requirements were checked, by whom and against what configuration, is an opinion, not an assessment.

Build the chain in four links

1. Scope the zone from the asset inventory. Every asset in the zone should come from a maintained inventory, not a drawing. The cold-chain campaign shows what happens to the assets that never made the list.

2. Tie the target to the risk. Record the threat scenario, the consequence and the likelihood that justify the SL-T. When the scenario changes, as it did this month for refrigeration, the target can be revisited with a reason on file.

3. Map controls to requirements. For each foundational requirement, record which control meets it, where it is implemented and how it was verified. A screenshot is evidence. "Configured as standard" is not.

4. Keep it current. An assessment ages from the day it is signed. Link each requirement to its evidence and a review date, so drift shows up before the audit does.

An achieved security level without evidence is an opinion. The auditor's job is to tell the difference.

Crosswalk once, report many times

The same evidence chain answers more than IEC 62443. Mapped through NIST SP 800-53, one verified control can support ISO/IEC 27001 Annex A, NIST CSF 2.0 and sector requirements such as NERC CIP, without repeating the assessment.

CIPHER · Issue 01 · November 2026GRC desk · 09
Awareness · Brief for operators, technicians and contractors

Six habits that close the default-password door

This year's OT campaigns keep returning to two weaknesses: devices reachable from the internet and passwords nobody changed. These habits are for everyone who touches a controller.

Change it on day one

Never commission a PLC, HMI, controller or gateway with the factory password. Treat "change later" as "never".

One person, one login

Shared accounts hide who changed what. Ask for named accounts, even for contractors and vendors.

Know what faces the internet

If you can reach a device from home without the company VPN, so can anyone else. Report it the same day.

Use the approved remote path

No personal remote tools, modems or port forwards. Remote access goes through the managed gateway and is logged.

Watch for changed settings

Unexpected setpoints, a new IP address or a password that stopped working are incidents, not glitches. Escalate them.

Speak up about old kit

If equipment no longer gets updates from the vendor, tell its owner. Unsupported does not mean safe because it still works.

If you can reach it from the internet, assume someone else already has.

Cut out and pin up
CIPHER awareness series 01
CIPHER · Issue 01 · November 2026Awareness · 10
Perspectives · CIPHER view

Should remote access to OT ever be always on?

The question comes up in every design review. Here are the two positions, and where CIPHER comes down.

The case for

Always on, tightly controlled

Plants run around the clock and so do failures. When a turbine trips at 3 a.m., waiting for someone to approve and enable a connection costs output and sometimes safety.

Supporters argue for control rather than absence: one managed gateway, multi-factor authentication, named accounts, session recording and an alert on every connection. A path that is always there but always watched beats an improvised tunnel opened during a crisis.

The case against

Off by default, on by request

A connection that does not exist cannot be exploited. This month's KEV list is full of the gateways that always-on access depends on, and attackers scan for them continuously.

Enable access per session, for a named person, for a fixed time, with the operator's approval. The delay is minutes. The exposure saved is every hour the door would otherwise stand open.

Where CIPHER stands

Off by default. Keep the managed gateway, the multi-factor authentication and the session recording, but open the path per session with operator approval. Allow standing access only where the risk assessment for that zone shows the delay itself would create an unacceptable safety or availability risk, and record that decision with an owner and a review date.

Questions to settle before you choose

  • What does a 15-minute delay in reaching the site really cost, measured against the consequence of a compromise?
  • Does the target security level of the zone allow persistent external connections at all?
CIPHER · Issue 01 · November 2026Perspectives · 11

Read CIPHER every month

Global incidents, ICS intelligence, GRC guidance and awareness material for the people who run and protect critical infrastructure.

Subscribe

Receive each issue by email on publication day, with the PDF edition in your CYNAPSE account.

Discuss

Take this month's questions to the CYNAPSE Community, where members compare notes between issues.

Learn

The CYNAPSE Knowledge Center and Academy go deeper on every topic covered in these pages.

www.cynapse.appcontact@cynapse.app

CIPHER, Issue 01, November 2026. Published by CYNAPSE. All articles are written by the CIPHER editorial team. Founding edition. Vulnerability figures reflect the CISA ICS advisory feed and KEV catalogue as held in the CYNAPSE intelligence database on 16 November 2026.

CIPHER · Issue 01 · November 2026www.cynapse.app · 12