What happens when manufacturers add remote access and new digital technologies without a security baseline?

Why Uncontrolled Remote Access Changes the Attack Surface

Remote access changes the manufacturer’s trust boundary because it creates paths from external networks into environments that often mix business systems, production applications, and operational technology. Without a security baseline, those paths are frequently too broad, too persistent, or too poorly monitored. That is why the real issue is not the technology itself, but the absence of minimum controls for authentication, segmentation, logging, and vendor oversight. Guidance from ISO/IEC 27002:2022 Information Security Controls is useful here because it frames remote connectivity as something that must be governed, not merely enabled. In practice, many security teams discover the weakness only after a remote support channel, contractor path, or plant integration link has already been used in ways nobody intended.

What the Baseline Needs to Cover in a Manufacturing Environment

A security baseline gives manufacturers a consistent minimum for how new digital tools are introduced, connected, and supervised. In practical terms, that means access should be limited, authenticated, logged, and periodically reviewed; critical systems should not inherit default trust just because they are connected; and the organisation should know which assets are internet-reachable, vendor-managed, or able to influence production. A baseline also forces clear ownership, which matters because manufacturing environments often span IT, engineering, maintenance, and suppliers.

For environments that expose credentials, service connections, or automated access paths, the OWASP Non-Human Identity Top 10 is relevant because machine-to-machine access can quietly become the weakest control plane when it is not inventoried or governed. That becomes especially important when robotics, IoT platforms, analytics pipelines, or remote monitoring tools use persistent tokens, embedded secrets, or vendor integrations. The baseline should also define what is allowed to connect to operational assets, what must be segmented, and what evidence is required before a system is put into service. Where that does not exist, organisations tend to treat each deployment as a special case, which is how control gaps accumulate across plants and suppliers.

• Define approved remote access methods and ban ad hoc pathways.
• Require strong authentication, least privilege, and session logging for every external connection.
• Inventory connected assets, including machine services and vendor-managed endpoints.
• Separate production-impacting systems from general business connectivity.

Where manufacturers skip these steps, the baseline breaks down because connectivity is added faster than governance can keep up.

When Digital Modernisation Makes Old Assumptions Fail

Tighter connectivity often increases operational convenience, but it also raises the cost of each assumption the organisation no longer verifies. A plant may deploy robotics, IoT sensors, analytics dashboards, or remote maintenance tools under the assumption that they are “just extensions” of existing systems, when in fact they introduce new access paths, new dependencies, and new failure modes. That is especially true when legacy equipment was never designed for direct exposure or frequent authentication changes.

One common edge case is where security controls exist on paper but are not aligned across the full lifecycle of the new technology. For example, a vendor may secure its own platform while the manufacturer leaves local access, certificate management, or privileged service accounts unmanaged. Another edge case is a mixed IT and OT environment, where control expectations differ and teams disagree about acceptable downtime or patch windows. Industry consensus is strong that these environments need explicit governance, but there is less consensus on the exact control stack for every plant, so organisations should treat the baseline as a minimum operational standard rather than a fixed architecture.

The practical test is whether the new technology can be removed, disabled, or isolated without disrupting production control. If that answer is unclear, the modernisation effort is ahead of the security model.

Risk and Threat Considerations

The material risk is not simply “more technology equals more exposure.” It is that remote access and connected devices create trust relationships that attackers can abuse and operators may not fully observe. Once a remote pathway or unmanaged machine connection reaches a production-adjacent system, the boundary between business systems and operational systems becomes much easier to cross.

Failure mechanism: Weak authentication, excessive standing access, poor network segmentation, unmanaged third-party credentials, or insufficient logging can let an attacker or abusive insider move from a low-value entry point into higher-impact systems. In connected manufacturing, that can turn a support tool, vendor portal, or device management path into an indirect route to critical applications or operational processes.

Impact: The result can be production interruption, unsafe process behaviour, corrupted data, unauthorised changes to equipment or schedules, and delayed detection because the access path looked legitimate. Over time, that also erodes confidence in suppliers, maintenance workflows, and the reliability of digital transformation itself.

Practitioner Guidance

What to prioritise: Treat remote access and new connected technologies as a governance change, not a deployment detail. The first question is whether the organisation can prove who can connect, what they can reach, and how that access is removed when it is no longer needed.

What to verify: Before trusting the environment, confirm that every external or machine-mediated access path is inventoried, approved, logged, and bounded by segmentation. Also verify that production-impacting systems have an owner who can explain the recovery implications if the new technology fails or is disabled.

Common mistake: Teams often secure the new platform itself while leaving the integration paths, service accounts, and remote support channels outside the baseline. That creates a false sense of control because the weakest entry point is usually the connection between systems, not the system being modernised.

Practitioner takeaway: In manufacturing, the baseline must arrive before the connectivity scales, because once remote access becomes normalised it is far harder to separate convenience from exposure.

Related resources from NHI Mgmt Group

• How should security teams replace traditional MFA without creating new access friction?
• How should security teams automate database access without creating new privilege creep?
• How should security teams automate identity lifecycle management without creating new access risk?
• How should security teams reduce OT remote access risk without blocking maintenance work?