Identity & Remote Access
Where persistent authority, weak attribution or over-privileged interfaces become the real attack path.
Browse all 11 analyses →Questions this collection helps you examine
- Who can use the engineering or maintenance path, and under what conditions?
- How are privileged sessions bounded, attributed and revoked?
- What remains possible when remote identity services are unavailable?
Each analysis keeps the incident evidence, deployment assumptions and practical decision together. Use the collection to compare cases across sectors.
Analysis, newest first
All decision collections →Node-RED Deployment Security Must Survive a Compromised Workstation and an Offline Plant
Patch the Siemens flaw, then protect flow changes without making emergency recovery dependent on external identity services.
Deploy the Siemens fix, bind flow changes to an approved revision and independent authority, and demonstrate accountable plant-side recovery without bypassing safety interlocks.
Monta Shows Why OCPP Station Identity Must Be Enforced in Deployment
Supporting an authenticated OCPP profile does not prove that deployed stations use it. Migration needs evidence for identity enforcement, fleet compatibility and service recovery.
Close an OCPP migration only when the deployed endpoint rejects unsupported identity claims and operations can provision, revoke and recover legitimate station access under a supported procedure.
CODESYS CVE-2026-79625 Makes Monitoring Authority an Engineering Decision
An authenticated monitoring path can affect data processing. Assess the deployed runtime, client permissions and concurrency before selecting a temporary control or update window.
Assess authenticated monitoring authority against the deployed runtime and concurrent-client configuration. Preserve required plant functions while validating temporary controls and the applicable supplier update.
BeyondTrust: patch the broker, investigate its prior authority
A Remote Support appliance was exploited in two known deployments before public disclosure of CVE-2026-102764. Closing the flaw does not answer which credentials, support sessions and downstream systems were exposed during the earlier window.
Verify the actual patch state, then assess the prior exposure window independently using off-box evidence and the appliance's support-session and permission history.
Third-Party ICS Access Is an Operational Trust Boundary, Not a VPN Problem
New CISA/FBI guidance on ICS integrators shows why secure connectivity is only one control in a wider chain of supplier identity, privilege, data exposure and operational recovery.
Govern ICS integrators as privileged operational identities with bounded, observable and revocable authority, not simply as trusted users of a secure remote-access channel.
Weidmüller Shows Why a Security Router Is a Privileged OT Asset
An unauthenticated command-injection flaw can execute shell commands as root on affected Weidmüller industrial security routers. The deeper lesson is that a boundary device inherits exceptional authority over every conduit it protects.
Treat industrial security routers as privileged OT control-plane assets. Patch the affected Weidmüller firmware, constrain every management channel, and monitor the policy state that defines reachability across the zones the router protects.
Siveillance Shows Why Least Privilege Must Cross the Application Boundary
CVE-2026-3014 lets authenticated users with edit permissions execute code in the Management Server Service context. The privilege question therefore extends from the application role to the service, host and management network.
Apply the Siemens fixed versions, then verify that edit-capable identities, the Management Server Service and the management network are all bounded by least privilege. Treat enclave, PAM, MFA and monitoring as exposure controls, not as product remediation.
Zero Trust in OT Should Mediate Authority, Not Modernise Every PLC
Legacy controllers do not need to speak modern identity protocols for the surrounding architecture to remove implicit trust.
Apply Zero Trust at the mediation layer that controls authority to legacy OT, rather than forcing unsupported controls into the endpoint.
Oldsmar Is a Warning About Standing Remote Authority
The enduring lesson is not a single remote-access product. It is the danger of persistent authority that remains available when nobody is actively using it.
Replace standing remote access with time-bounded, asset-specific authority tied to an operational workflow.
The Connected Vehicle Perimeter Includes Dealer APIs
The Kia research showed how a public identifier and an over-privileged dealer workflow could become an internet-to-vehicle control path.
Model dealer and after-sales backends as part of the vehicle security architecture, with transaction-level authorisation and auditable ownership changes.
The Remote Access Path Nobody Questions Anymore
The risk in industrial remote access is not connectivity itself. It is persistent, weakly attributable trust that can turn a maintenance path into a reusable attack conduit.
Replace persistent network trust with attributable, least-privilege maintenance transactions, but design and test the fallback before removing the legacy path.