Anyone who can reach a Logix controller on TCP 44818 with a compatible tool may be able to change its logic unless the controller and network are configured to prevent it. Rockwell Automation's security advisories set out the customer-side mitigations: the mode switch, CIP Security, Security Authority binding and network isolation. ControlLogix, CompactLogix and GuardLogix controllers, with Studio 5000 Logix Designer and the FactoryTalk software suite, run a large share of manufacturing, utilities and process plants. This guide sets out how identity and access work across that stack, which settings Rockwell documents for hardening, and how to detect unauthorised changes. It is for OT engineers, control system integrators and security teams responsible for Rockwell environments, and goes deeper than the general PLC Security Guide.
This is an independent guide from NHI Mgmt Group, based on Rockwell Automation's public documentation as of November 2026. It is not sponsored or reviewed by Rockwell Automation. Product features change, so confirm settings against Rockwell Automation's current documentation.
Key takeaways
- Put the mode switch in RUN. Rockwell lists it as the first mitigation in its Logix controller advisory for most controller families; leave it in REM or PROG only during planned engineering work.
- CIP Security is the real fix for controller authentication. Deployed through FactoryTalk Policy Manager, it gives device authentication, integrity and optional confidentiality on EtherNet/IP; proxies and newer communication modules cover controllers without native support.
- FactoryTalk Security decides who may do what. Securable actions such as Controller: Modify Mode, Project: Download and Firmware: Update should be granted to named groups, with projects bound to one Security Authority.
- Computers and services are identities too. FactoryTalk computer accounts, Linx servers, AssetCentre agents and OPC gateways all hold access to controllers and need owners and least privilege.
- Detect change, not just intrusion. Component change detection, the Controller Log, syslog from CIP Security devices and FactoryTalk AssetCentre audit are how you find an unexpected download.
How identity and access work in Rockwell Logix and FactoryTalk
Access to a Logix controller passes through several independent layers. Hardening means configuring each one, because an attacker will use whichever is weakest.
| Layer | What it controls | Where it is configured | Known limitation |
|---|---|---|---|
| Network reachability | Who can send CIP traffic to TCP 44818 | Firewalls, Stratix switch ACLs, VLANs, CPwE zones | Flat cell networks let any host reach any controller |
| Controller mode switch | Whether the controller accepts program changes | Physical key switch on the controller | Left in REM, remote tools can change mode and download |
| CIP Security | Device authentication, integrity, confidentiality on EtherNet/IP | FactoryTalk Policy Manager with FactoryTalk System Services | Needs supported firmware or a proxy; not on by default |
| FactoryTalk Security | Which users and computers may perform securable actions in Rockwell software | FactoryTalk Administration Console, FactoryTalk Directory | Enforced by Rockwell software; pair with CIP Security and network isolation so that other tools cannot reach the controller |
| Security Authority binding (SAID) | Ties a project and controller to one FactoryTalk Directory | Logix Designer project security settings | Losing the SAID backup means losing access to secured projects |
| Tag and source protection | External read and write per tag, protection of routines and Add-On Instructions | Tag External Access and Constant attributes, License Source Protection | Legacy Source Key protection is not recommended by Rockwell |
Rockwell's advisory guidance shows why the layers matter: FactoryTalk Security governs Rockwell software, so the controller itself is protected by the mode switch, CIP Security, Security Authority binding combined with CIP Security, and restricting TCP 44818 from outside the industrial zone. Confirm with Rockwell which controller families and software versions each advisory covers.
Admin roles and privileged access
FactoryTalk Security is the central authority for authentication and authorisation across FactoryTalk software, and Logix Designer enforces its permissions. The Logix 5000 Controllers Security manual (1756-PM016) lists the securable actions that matter most:
| Securable action | Risk if granted widely | Who should hold it |
|---|---|---|
| Controller: Modify Mode | Remote change from RUN to PROGRAM stops the process | Named controls engineers, during approved changes |
| Project: Download | Replaces running logic | Named controls engineers via change control |
| Routine: Modify Logic | Online edits to running code | Controls engineers; not operators or maintenance |
| Firmware: Update | Firmware change or downgrade | Small group, with signed firmware only |
| Nonvolatile Memory: Load and Store | Overwrites the stored image that loads at power-up | Controls engineers |
| Controller: Secure, Unsecure, Lock, Unlock | Removes protections | Security administrators only |
| Tag: Write Value | Changes setpoints and process values | Operators for operational tags only, via the HMI |
- Build groups, not individual grants: create user groups (operators, maintenance, controls engineers, security administrators) and computer accounts, assign permissions to groups, and use system policies for password length, complexity and expiry. Rockwell's System Security Design Guidelines (SECURE-RM001) also advise removing all users from the default directory permission list once groups are in place.
- Use the Network Directory with Active Directory: avoid local passwords, manage users centrally, and host the FactoryTalk Network Directory on a dedicated Windows Server, not on a domain controller or alongside other FactoryTalk software.
- Bind projects to one Security Authority: with "use only the selected security authority" set, Logix Designer checks that the FactoryTalk Directory ID matches the one stored in the project; otherwise only Guest User permissions apply. Keep Guest permissions minimal, and back up the SAID.
- Keep engineering privilege on engineering workstations: dedicate workstations to operator or engineering roles, minimise local administrator rights, restrict USB media, and join them to the domain. See the Engineering Workstation Security Guide.
- Remote engineering access: route it through an approved remote access path with multi-factor authentication and session approval. For the Stratix 4300 remote access router, Rockwell documents two-factor authentication and outbound-only connections on TCP 443, 80 or 5935. See the OT Remote Access Guide.
Integrations, API tokens and service accounts
Much of the access to a Rockwell controller does not come from a person at a laptop. These non-human identities are often the least reviewed.
- FactoryTalk computer accounts: FactoryTalk Security grants permissions to computers as well as users. Scope computer accounts so an HMI station cannot download projects.
- FactoryTalk Linx and Linx Gateway: Linx is the communications service that delivers controller data to FactoryTalk applications and Studio 5000; Linx Gateway exposes tag data to OPC UA and OPC Classic clients, with access controlled by FactoryTalk Security. Treat each OPC client connection as an identity with read or write scope, and deny write unless required.
- Historians and MES connectors: service accounts that read tags at scale. Give them read-only permissions and set tag External Access to Read Only (or None) for anything they do not need.
- FactoryTalk AssetCentre agents: agents poll controllers for backups and change detection. Do not use agent hosts as engineering workstations, as SECURE-RM001 advises.
- License services: CodeMeter network license sharing uses TCP and UDP 22350; Rockwell's manual sets "Default action" to Deny and "Access Control Mode" to Basic. Restrict which hosts may reach it.
- Windows service accounts: FactoryTalk services, SQL Server for AssetCentre and OPC servers run under Windows accounts. Use managed or dedicated accounts, not domain administrators, and vault their passwords. See the Service Account Security Guide and the Identity for OT Environments Guide.
Logging and detection
Rockwell provides several detection sources. Combine controller-side evidence with network monitoring, because activity from tools other than FactoryTalk software will not appear in FactoryTalk audit logs.
| Source | What it records | Notes |
|---|---|---|
| Component change detection | Signature change in a tracking group of tags, I/O modules or routines | Logix Designer v30 and later; tracked state shown on the Security tab in Controller Properties |
| Controller Log | Controller events such as mode changes and downloads | Named by Rockwell as a detection option where supported |
| Syslog from CIP Security devices | Security events defined by FactoryTalk Policy Manager event policy | Collector must support RFC 5424 |
| FactoryTalk AssetCentre | Audit of user actions, tamper detection, scheduled backups and difference reports | Size the log so rolling product logs do not overwrite events; watch for overflow |
| Network monitoring | CIP traffic to 44818, unexpected programming sessions, malformed CIP | Rockwell's PN1633 advisory provides Snort rules that flag CIP traffic not conforming to the ODVA specification |
Alerts worth building: a controller leaving RUN mode outside a change window; a download or online edit from a host that is not an approved engineering workstation; any CIP connection to a controller from outside its cell or the IDMZ; firmware update events; and change-detection signature changes without a matching change ticket. ATT&CK for ICS techniques to map against are Change Operating Mode (T0858), Program Download (T0843), Modify Program (T0889), Modify Parameter (T0836) and Modify Firmware (T1693). See the OT Network Security Monitoring Guide.
Metrics: percentage of controllers with the key switch in RUN; percentage of controllers communicating over CIP Security; controllers bound to a Security Authority; change-detection alerts reconciled to tickets within one shift; hosts able to reach TCP 44818 from outside the industrial zone (target zero).
Hardening baseline
Roll these out in order, testing each step on a non-production controller or a planned outage first, and keeping a verified backup of every project before changes.
- Isolate the network: follow Rockwell and Cisco's Converged Plantwide Ethernet (CPwE) architecture with IEC 62443 zones and an industrial DMZ where all traffic terminates and EtherNet/IP control traffic stays inside the Industrial Zone. Block TCP 44818 from outside the industrial zone and never expose controllers to the internet. See the OT Network Segmentation Guide.
- Set the mode switch to RUN: make it the normal state, record the position at each shift or audit, and control the physical keys.
- Configure FactoryTalk Security: Network Directory, Active Directory groups, securable action permissions per group, password policy, and Security Authority binding for every project.
- Restrict tag access: leave External Access at None unless a tag must be read or written externally; set Constant on configuration values that should never change; enable serial number matching so a project cannot be downloaded to the wrong controller.
- Protect source and integrity: use License Source Protection rather than legacy Source Key, and High Integrity Add-On Instructions with signatures where safety or regulation requires them.
- Deploy CIP Security: use FactoryTalk Policy Manager (with FactoryTalk System Services 6.20 or later) to define zones and policies. Start with integrity and authentication, add confidentiality where performance allows. For controllers without native support, Rockwell suggests the 1783-CSP CIP Security Proxy or the 1756-EN4TR module.
- Patch and verify firmware: download only from Rockwell's official portal, verify signatures with Microsoft SignTool, update with ControlFLASH or ControlFLASH Plus, and track advisories. Apply Rockwell's security updates promptly; Rockwell publishes them on its Security Advisories page. For the 1756-EN2x and EN3x communication modules, Rockwell's PN1633 advisory gives minimum firmware (for example EN2* 11.004 or later) and notes that signed firmware cannot be reverted to unsigned. See the OT Patch Management Guide.
- Reduce features: disable unused capabilities and CIP objects (PN1633 names the Email and Socket objects), and harden Stratix switches with port security, ACLs, unused ports disabled and SSH, HTTPS and SNMPv3 for management.
- Turn on detection: change detection, syslog, AssetCentre audit and backups, then verify by making a controlled change and confirming every source records it.
Rollback: keep the pre-change project, FactoryTalk Directory backup and SAID backup. CIP Security policies can be removed from Policy Manager to restore unsecured communication if a production line is affected, but plan this with the integrator, since devices must agree on policy to communicate.
Small site vs large estate: a single-line plant may start with segmentation, RUN mode, FactoryTalk Security groups and AssetCentre-style backups. A multi-site manufacturer should standardise a Network Directory per site, Policy Manager templates for CIP Security, and central collection of syslog and change-detection events.
Framework mapping
| Control | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 | IEC 62443-3-3 theme |
|---|---|---|---|
| FactoryTalk Security groups and securable actions | AC-2, AC-3, AC-6 | PR.AA-05 | Use control |
| CIP Security device authentication | IA-3, SC-8 | PR.DS-02 | Identification and authentication control, system integrity |
| Mode switch, change control, change detection | CM-3, SI-7 | PR.PS-01, DE.CM-09 | System integrity |
| Signed firmware, ControlFLASH | CM-14, SI-7 | PR.PS-02 | System integrity |
| Disable unused features and CIP objects | CM-7 | PR.PS-01 | Restricted data flow |
| Syslog, AssetCentre audit | AU-6 | DE.CM-09 | Timely response to events |
Common misconfigurations
- Key switch left in REM: convenient for engineering, but it lets remote tools change mode and download. This is the setting Rockwell asks customers to change first.
- FactoryTalk Security treated as sufficient: it governs Rockwell software. Pair it with network isolation and CIP Security so the controller itself is protected, not only the engineering tools.
- Default directory permissions kept: broad default groups still granted every action, so any domain user can download.
- Tags exposed for convenience: External Access set to Read/Write on every tag so an HMI or historian "just works", letting any connected client change setpoints.
- Controllers reachable from the enterprise or internet: flat networks or remote access tools that bridge straight to the cell. Rockwell's security advisories ask customers to keep control systems off the internet, behind firewalls and isolated from enterprise networks.
- Infostealer exposure of engineering credentials: engineering and integrator credentials stolen from workstations give an attacker legitimate access paths.
Practitioner checklist
- Confirm no controller or FactoryTalk server is reachable from the internet, and block TCP 44818 from outside the industrial zone.
- Set every controller key switch to RUN and record the position at each audit.
- Move to a FactoryTalk Network Directory with Active Directory groups, remove broad default permissions, and bind every project to one Security Authority.
- Restrict Controller: Modify Mode, Project: Download and Firmware: Update to named engineering groups.
- Review tag External Access and set unused tags to None and fixed values to Constant.
- Plan CIP Security with FactoryTalk Policy Manager, using proxies or EN4TR modules for controllers without native support.
- Inventory computer accounts, OPC clients, historian and AssetCentre service accounts, and reduce them to least privilege.
- Apply firmware fixes from Rockwell advisories (including PN1633 for EN2x and EN3x modules) using signed firmware.
- Enable change detection, syslog and AssetCentre audit, and test that a controlled change raises an alert.
Standards and references
- Rockwell Automation: System Security Design Guidelines Reference Manual (SECURE-RM001)
- Rockwell Automation: Logix 5000 Controllers Security Programming Manual (1756-PM016)
- Rockwell Automation: PN1633, Vulnerabilities in Select Communication Modules
- Rockwell Automation: Security Advisories
- MITRE ATT&CK for ICS: Program Download
- NIST: SP 800-53 Rev. 5
Related NHI Mgmt Group resources: PLC Security Guide · EtherNet/IP and CIP Security Guide · Engineering Workstation Security Guide · OT and ICS Identity and Access Guide · IEC 62443 Guide