Home › Technical articles

Đọc bằng tiếng Việt

CIP Security on ControlLogix 5580, CompactLogix 5380: FactoryTalk Policy Manager, zones, conduits, Trusted IP

TDL Industrial Automation · Last updated:

From Rockwell's SECURE-AT001F (December 2025) and the FactoryTalk 6.60 help: what CIP Security does, which controllers, modules and drives support it from which firmware, the roles of Policy Manager, System Services and FactoryTalk Linx, zones, conduits, certificates and Trusted IP, the effect on HMIs and engineering stations, and the deployment order.

CIP Security lets EtherNet/IP devices prove who they are, reject altered data and, if chosen, encrypt it. On Rockwell Automation systems it runs on ControlLogix 5580 from firmware 32.011, CompactLogix 5380 from 34.011 and a short list of modules and drives, and the policy is built in FactoryTalk Policy Manager. This article follows Rockwell's SECURE-AT001F (December 2025) and the 6.60 help: products, software, zones and conduits, HMI and engineering connections, and deployment order. The wider hardening picture is in Rockwell PLC security.

CIP Security: Policy Manager, zones and conduitsAn example after Rockwell's SECURE-AT001F. At the top, the PC zone: the FactoryTalk Directory server running FactoryTalk Policy Manager and System Services, which builds the model and deploys the policy to every secured device, and a workstation running Logix Designer, FactoryTalk Linx and FactoryTalk View. Two certificate conduits link the PC zone to Zone 1 and Zone 2. Zone 1 holds a ControlLogix 5580 at firmware 32.011 or later, a 1756-EN4TR at any firmware, a PowerFlex 755T at 10.001 or later and a PanelView Plus that is not CIP Security-capable and joins through Trusted IP. Zone 2 holds a CompactLogix 5380 at 34.011 or later, a Kinetix 5700 at 11.001 or later, a 1783-CSP proxy and a device without CIP Security on Trusted IP. There is no conduit between Zone 1 and Zone 2, so that traffic is denied. At the bottom, the four steps in Policy Manager: zones, conduits, policies, deploy.CIP Security: Policy Manager, zones and conduitsPC zoneservers and workstationsFactoryTalk Policy Managerwith System Services on theFactoryTalk Directory server; deploys the policyto every secured deviceWorkstationLogix Designer, FactoryTalk Linx andFactoryTalk View; fixed IP addressCertificate conduitCertificate conduitZone 1devices in a zone trust each otherZone 2devices in a zone trust each otherControlLogix 5580firmware 32.011 or laterCompactLogix 5380firmware 34.011 or later1756-EN4TRany firmwareKinetix 5700firmware 11.001 or laterPowerFlex 755Tfirmware 10.001 or later1783-CSPproxy for a device without CIP SecurityPanelView Plusnot CIP Security-capable: Trusted IPOlder devicenot CIP Security-capable: Trusted IPCIP Security-capableNot capable, joins through Trusted IPNo conduit: deniedOrder of work in Policy Manager1 · Zonesgroup devices with thesame needs2 · Conduitstrusted pathsbetween zones3 · Policiescertificate, integrity,encryption4 · Deployshort loss ofconnectivity; back upthe modelBased on Rockwell SECURE-AT001F-EN-P (12/2025, pp. 29–65) and the FactoryTalk Policy Manager 6.60 help(read 15 November 2026). The layout is an example. Figure: drawn by TDL.
Figure 1: CIP Security: Policy Manager, zones and conduits. On a phone, swipe sideways to see the whole figure.

1. What CIP Security does

CIP Security is an ODVA standard for EtherNet/IP that works at the device level (SECURE-AT001F p. 14). It gives three properties (pp. 14–16):

  • Device identity and authentication. Each device proves its identity with an X.509v3 certificate, which Rockwell recommends, or with a pre-shared key. FactoryTalk System Services acts as the certificate authority. A device can hold only one pre-shared key.
  • Data integrity. A keyed hash (HMAC) shows whether a message was changed on the way.
  • Confidentiality. Encryption is optional and is enabled on top of integrity.

TCP traffic is protected with TLS, UDP traffic with DTLS (p. 15). The set of features a device supports is its security profile (p. 16). The CIP Security port is 2221 (pp. 22–23; 1756-UM543).

2. Which controllers and modules support it

SECURE-AT001F (Table 13, pp. 30–33) gives these minimum firmware revisions; the FactoryTalk Linx 6.60 help prints the same values for the products it lists.

Product Minimum firmware
ControlLogix 5580 and ControlLogix 5580 Process controllers 32.011
GuardLogix 5580 controllers 34.011
ControlLogix 5590 controllers 38.011
CompactLogix 5380, CompactLogix 5380 Process and Compact GuardLogix 5380 controllers 34.011
1756-EN4TR EtherNet/IP communication module any
1783-CSP CIP Security Proxy any
Kinetix 5300 / Kinetix 5700 drives 13.003 / 11.001
PowerFlex 755T / 755TS / 6000T drives 10.001 / 11.001 / 9.001
Armor PowerFlex 350 drives 10.001

The ControlLogix 5580 family covers 1756-L81E to 1756-L85E with their K, -NSE, XT and EP versions (1756-UM543). The CompactLogix 5380 manual (5069-UM001N, January 2026) lists 5069-L306ER to 5069-L3100ERM (p. 12) and CIP Security from firmware 34.011 (p. 28).

ControlLogix 5570, CompactLogix 5370 and older controllers are not on the list. SECURE-AT001F says some non-CIP Security Logix controllers can be used through a 1756-EN4TR, and names the retrofit of a ControlLogix 5570 system with a 1756-EN4TR (p. 33). The 1783-CSP proxies a device that is not CIP Security-capable, but the Policy Manager 6.60 help says a CIP Proxy cannot stand in for a controller or an HMI device.

Firmware updates: ControlLogix and CompactLogix firmware update with ControlFLASH Plus.

3. The software: Policy Manager, System Services, Linx

SECURE-AT001F (Table 12, pp. 29–31) lists four packages:

Software Role Minimum version
FactoryTalk Policy Manager creates, deploys and shows the security policies 6.11
FactoryTalk System Services runs in the background and deploys the policies 6.11
FactoryTalk Linx the secure EtherNet/IP client for CIP Security devices 6.11
Studio 5000 Logix Designer not needed to set up CIP Security; it talks to devices through FactoryTalk Linx 32.00.00, or 31.00.00 through a 1756-EN4TR

RSLinx Classic cannot be used for CIP Security (p. 29). Policy Manager and System Services must be installed on the FactoryTalk Directory server, and the network with the secured ports must reach it (p. 35). Newer pages set higher versions: the FactoryTalk Linx 6.60 help asks for Policy Manager and System Services 6.50.00 or later, and the Policy Manager 6.60 release notes pair it with FactoryTalk Linx 6.60, with System Services and the FactoryTalk Services Platform at the same version.

Policy Manager 6.60 also sets OPC UA policies; see FactoryTalk Linx and OPC UA.

4. Zones, conduits, certificates and Trusted IP

A Policy Manager model is built from devices (computers, controllers, modules, HMI panels, CIP Proxy devices, OPC UA clients and servers, drives), zones and conduits.

  • Zone. Devices with the same requirements; each device is in one zone only, and devices in a zone trust each other without a conduit (SECURE-AT001F pp. 17–18).
  • Conduit. A trusted path outside a zone. The 6.60 help allows zone–zone, zone–device, zone–range, device–device and device–range; at least one end must be CIP Security or OPC UA capable.
  • Authentication. With Certificate, devices present certificates and the integrity and encryption settings apply. With Trusted IP, devices are trusted by IP address with no further checks.

The zone settings in the 6.60 help:

Setting Options
Authentication method Certificate (default) or Pre-shared Key
I/O data security Integrity Only (default), Integrity & Confidentiality (Rockwell recommends it), None
Messaging security Integrity Only (default) or Integrity & Confidentiality
Disable port HTTP (80) turns off port 80 on the CIP Security devices of the zone

A device that is not CIP Security-capable can sit in a zone: the secured devices add its IP address to their Trusted IP list, and its connections are not secured (p. 38). Rockwell recommends not connecting such legacy devices, because a hijacked device or a spoofed IP address could get in (p. 21).

Subject Alternative Name writes the device's IP address into its certificate for the client to check. It is on by default from Policy Manager 6.40.00, needs 5580 or 5380 firmware 35.011 or later, and the model must be redeployed when a device's IP address changes (pp. 52–54). Zone design follows IEC 62443 zones and conduits.

5. What changes for HMI, SCADA and engineering connections

  • Engineering stations. Logix Designer reaches a secured controller through FactoryTalk Linx, the secure client. A FactoryTalk Linx computer in a CIP Security zone must keep its IP address; after a change, the 6.60 help says it is no longer allowed to connect to the secured devices.
  • FactoryTalk View. In the SECURE-AT001F example, a PC-zone workstation runs Logix Designer, FactoryTalk Linx and FactoryTalk View and reaches each controller zone through a conduit (pp. 38–43).
  • PanelView Plus. The same example marks PanelView Plus as not CIP Security-capable and lists it under Trusted IP (pp. 38–39, 49), so its connections are not secured.
  • Every client during deployment. Deploying the model resets communication on the devices: a short loss of connectivity (p. 54).

6. Deployment order

From SECURE-AT001F:

  1. Design first. List devices, firmware and data flows; Rockwell generally recommends implementing the security model before downloading the Logix Designer project (p. 36).
  2. Install. Policy Manager and System Services on the FactoryTalk Directory server (p. 35); FactoryTalk Linx on each workstation, with a fixed IP address.
  3. Create zones and assign the devices (pp. 37–41).
  4. Create conduits between zones and devices that must talk (pp. 42–47).
  5. Set the policies: authentication method, integrity and confidentiality, Trusted IP entries (pp. 48–49). CIP Bridging Control (Policy Manager 6.30 or later) can also limit traffic bridged through the backplane (pp. 49–51).
  6. Deploy. Check that every device is reachable, choose the scope (changed ports only is recommended) and the reset option (reset existing connections is recommended) (pp. 54–57). Policies travel only over EtherNet/IP, on the Policy Manager server's network or through a router, not through CIP bridging (pp. 21–22).
  7. Back up the model with the FTSSBackupRestore utility after each deployment (p. 65).

7. Redundancy, Dual-IP and turning it off

  • Dual-IP. In DLR/Linear mode both controller ports share one IP address and both can be secured; in Dual-IP mode only one port and one network can be secured (pp. 33–35).
  • ControlLogix redundancy. Secured programming connections need ControlLogix 5580 firmware 34.011 or later and 1756-EN4TR firmware 4.001 or later; applying the configuration disqualifies the redundant pair (p. 68). Secure connections to I/O devices are not possible in a ControlLogix redundancy system (p. 70). Our checklist: ControlLogix redundancy before FAT.
  • Removing a policy. Move the device to Unassigned or to a zone without CIP Security, or delete it, and deploy again; if Policy Manager cannot reach the device, a factory reset remains (pp. 61–64).
  • Disabling port 2221. FactoryTalk Linx 6.30 or later can disable CIP Security on a device. Turning it back on needs a reset to factory defaults, which on a ControlLogix 5580 clears the application program (pp. 22–23).

Firewall rules: Firewalls for FactoryTalk and Logix systems.

What we check first

This is TDL's practice, not a Rockwell Automation requirement.

  • We list controllers, modules and drives with catalog number and firmware, and mark which stay on Trusted IP.
  • We list every client of the controllers: engineering stations, SCADA servers, PanelView Plus, controller messages, third-party drivers. The Rockwell documents we read do not cover third-party drivers, so we check each vendor's documentation.
  • We check the communication software on each station and the versions of Policy Manager, System Services, FactoryTalk Linx and the Services Platform; RSLinx Classic has to give way to FactoryTalk Linx.
  • We check the Ethernet mode of each controller (Dual-IP or DLR/Linear) and whether it is in a redundant pair.
  • We schedule the first deployment in a shutdown, with a backup of every controller program and of the security model.

How TDL approaches it

TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. Our Rockwell service page lists CIP Security between Logix controllers and the devices that support it as part of OT network hardening. More on these services: Rockwell Automation system integrator in Vietnam, Industrial networks and OT security and Rockwell Automation upgrades.

Frequently asked questions

Which Rockwell controllers support CIP Security?

ControlLogix 5580 from firmware 32.011, GuardLogix 5580 and the CompactLogix 5380 family from 34.011, and ControlLogix 5590 from 38.011, per SECURE-AT001F. The 1756-EN4TR module and the 1783-CSP proxy support it at any firmware.

Is CIP Security configured in Logix Designer?

No. The policy is built and deployed in FactoryTalk Policy Manager, with FactoryTalk System Services in the background. Logix Designer is not needed to set it up and reaches secured controllers through FactoryTalk Linx; RSLinx Classic cannot be used.

What is the difference between Trusted IP and a certificate conduit?

With a certificate, both ends prove their identity and the integrity and encryption settings apply. With Trusted IP, a device is trusted by its IP address only and its connections are not secured. Rockwell intends it for devices that are not CIP Security-capable.

Can a PanelView Plus talk to a controller that has CIP Security?

In Rockwell's example the PanelView Plus is marked not CIP Security-capable and is added under Trusted IP, so it still connects but its connections are not secured. The 1783-CSP proxy cannot be used for HMI devices.

Does deploying a CIP Security policy interrupt the process?

Deployment resets communication on the configured devices, which SECURE-AT001F calls a short loss of connectivity. We schedule the first deployment in a shutdown, with backups of the controller programs and of the security model.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Industrial networks & OT security Rockwell Automation (Allen-Bradley)