A hand pointing to the word work safety on a blue background.
Home
Il blog Hilscher

Securing EtherNet/IP: CIP Security with netX 90

Industrial communication is entering a new phase. For years, cybersecurity in factory automation was often treated as an additional feature. With the Cyber Resilience Act (CRA), it becomes part of the product requirement. From 11 December 2027, manufacturers that want to sell connected products in the EU will need to meet defined cybersecurity requirements. This also affects EtherNet/IP-enabled devices. For many manufacturers, CIP Security is therefore moving from an option to a practical requirement.

ODVA, as the overseeing body of the EtherNet/IP protocol, links CIP Security, a network extension for EtherNet/IP, directly to core CRA-related expectations. These expectations encompass secure-by-default behavior, protection against unauthorized access, data confidentiality, and data integrity. At the same time, the organization also makes one point clear: CIP Security is not the whole answer. Every product still needs its own cybersecurity risk assessment, and additional measures around updates, vulnerability handling, logging, and lifecycle processes remain necessary.

That is exactly why CIP Security matters right now. It gives device manufacturers a standardized way to secure EtherNet/IP communication at device level by bringing established security technologies such as Transport Layer Security (TLS), Datagram Transport Layer Security (DTLS) as well as certificates with a public key infrastructure (PKI) into the OT world. The goal is not security for its own sake. The goal is to protect communication without losing interoperability or industrial usability. For product managers, developers, and technical decision-makers, the real question is no longer whether security needs to be integrated into EtherNet/IP products. The real question is how to implement it early enough, reliably enough, and with a realistic development effort.

What CIP Security Adds to EtherNet/IP

CIP Security is a security extension for EtherNet/IP. Its purpose is to protect communication between industrial devices without abandoning the installed technology base of EtherNet/IP. Instead of introducing a completely separate communication model, CIP Security builds on established security mechanisms that are already widely used in IT. ODVA explicitly refers here to standards such as TLS and OpenID Connect, combined with proven encryption methods. 

That is an important point for decision-makers. CIP Security does not reinvent industrial communication. It extends EtherNet/IP with mechanisms that help devices authenticate communication partners, encrypt transmitted data, and protect communication against manipulation. In other words, it brings security functions into a protocol environment that has long been valued for interoperability and industrial usability.

This makes CIP Security relevant far beyond pure protocol discussions. Product managers, developers, and technical sales teams are increasingly faced with the same practical question: how can an EtherNet/IP product remain marketable in a regulatory environment that demands secure-by-design products and traceable cybersecurity measures? CIP Security is part of the answer because it gives manufacturers a standardized way to secure communication at device level.

Four Reasons CIP Security Has Become So Important

1. Secure by Default

The CRA expects products to be delivered in a secure default state. For industrial devices, this is highly relevant because insecure default communication settings create risks long before a machine enters regular operation. ODVA points out that the CIP Security Pull Model supports this requirement by allowing devices to automatically obtain security-related configuration and certificates after deployment. The basic idea is simple: security should not depend on extensive manual intervention after commissioning. It should already be part of the initial device behavior.

Two boxes encircled by two half circles with arrows at the opposite ends.

2. Protection Against Unauthorized Access

A second key requirement is the protection against unauthorized access. In practice, this means that devices need mechanisms to verify who is allowed to communicate with them and under which conditions. According to ODVA, CIP Security addresses this through authentication methods based on certificates and pre-shared keys, using Mutual TLS (mTLS). For more advanced scenarios, additional user authentication and role-based access control can be integrated as well. This makes CIP Security relevant not only for encrypted traffic, but also for controlled access in industrial communication networks.

3. Confidentiality of Transmitted Data

In today’s existing automation systems, data confidentiality holds a lower priority than data reliability and deterministic behavior. That is changing. The CRA explicitly addresses the protection of transmitted data. CIP Security supports this by securing EtherNet/IP communication with TLS and DTLS with AES encryption, an established standard. This reduces the risk that communication can be read or intercepted on the network. Since CIP Security only secures data in transit ODVA explicitly stresses that encryption for stored data remains responsibility of the manufacturer.

4. Integrity of Transmitted Data

Confidentiality alone is not enough. Industrial communication also has to ensure that transmitted data remains unchanged and trustworthy. Commands, configuration data, and process values must arrive exactly as intended. CIP Security supports this requirement through integrity protection with TLS and DTLS, with all cipher suites defined by the EtherNet/IP extension. It is important to also mention here, that CIP Security applies to data in transit. Manufacturers remain responsible to ensure data integrity at rest.

What CIP Security Does Not Cover on Its Own

For all its importance, CIP Security should not be misunderstood as a shortcut to full CRA compliance. The CRA also requires vulnerability handling processes, technical documentation, end-user documentation, secure development practices, and mechanisms for updates and security advisories. In addition, every product needs its own cybersecurity risk assessment. The regulation does not support a one-size-fits-all interpretation.

This distinction is important for a realistic discussion. CIP Security helps manufacturers secure EtherNet/IP communication in key areas that matter for CRA readiness. It does not replace product-level responsibilities such as secure firmware updates, logging, incident handling, SBOM management, or product-specific threat assessment. A credible cybersecurity strategy for industrial devices therefore needs both: a secure communication layer and a structured product security process around it.

Implement CIP Security with netX

For developers and product managers the main question is: How can I implement CIP Security into my device? To answer this question in a practical approach, Hilscher has developed a CIP Security evaluation bundle for the EtherNet/IP Adapter firmware stack of the netX 90 communication controller. 
The evaluation bundle is intended for customers and evaluators who want to:

  • Explore CIP Security functionality on EtherNet/IP
  • Evaluate configuration workflows and certificate handling
  • Establish secure Class 1 and Class 3 communication
  • Test interoperability with standard EtherNet/IP engineering tools
  • Upgrade existing netX 90 devices to CIP Security (under certain prerequisites)

The package contains the firmware, supporting tools, documentation, and a demo application to help users to get started quickly. 
Are you interested in getting started with EtherNet/IP? Get in touch with our team to explore your options.

Related links

A hologram of a cyber security writing in blue. Two people can be seen blurily behind the hologram.

Attacks on industrial systems are steadily increasing and becoming more sophisticated. At the same time, regulatory requirements like CRA and NIS 2 for secure operations and device protection are gaining traction. We help you operate your devices securely and prepare them for the future. Schedule a free consultation with our experts today! 

A photo of the male and female customer support phone operator with different internationality

Customer Center / Sales Hilscher Gesellschaft für Systemautomation mbH

You've got questions? We've got the answers!

Newsletter Form

Fieldset

Stay Up to Date

In our newsletter we inform you regularly about our latest products, solutions as well as participation in events such as exhibitions and conferences. In this way, we offer exciting insights into the world of Hilscher and automation technology. Sign up now!

Fieldset