ETG.1800 Gives EtherCAT an IEC 62443-3-3 SL2 Security Blueprint
ETG has released ETG.1800, mapping EtherCAT security measures to IEC 62443-3-3 SL2. We examine the system-level meaning, CRA context and brownfield implications.
On November 19, 2026, the EtherCAT Technology Group (ETG) published version 1.0 of ETG.1800, the EtherCAT Security Profile. ETG says the profile maps existing EtherCAT capabilities and related process measures to the system requirements of IEC 62443-3-3 at Security Level 2 (SL2), without changing the underlying communication technology. For machine builders and end users, the important point is not a new protocol feature. It is a documented way to connect network design, device configuration and lifecycle controls to a recognized industrial cybersecurity framework.
What ETG.1800 actually contains
ETG describes ETG.1800 as a two-part profile. Part 1 defines the system under consideration, the assessment approach, threat and risk considerations, and three representative application scenarios. Part 2 identifies EtherCAT-related security measures and explains how inherent functions, configurable controls and lifecycle processes can contribute to an IEC 62443-3-3 assessment.
The specification references existing EtherCAT documents rather than reproducing every function. That distinction matters in engineering work: ETG.1800 is a profile and assessment structure, not a replacement for device manuals, network design rules, security policies or the IEC standard itself. The downloadable release is listed as version 1.0.0 dated November 16, while ETG's public announcement is dated November 19.
SL2 is a system target, not a logo for every device
ETG's headline claim is that the profile fulfils the applicable IEC 62443-3-3 requirements for SL2. IEC 62443-3-3 defines system security requirements around seven foundational areas, including identification and authentication, use control, system integrity, restricted data flow, event response and resource availability. The standard also expects a risk assessment to determine an appropriate target security level for the specific zones and conduits.
That means an EtherCAT component does not become “SL2 certified” merely because it is installed on a network designed with ETG.1800. A project still needs a defined system boundary, asset inventory, threat model, target security level, configuration evidence and compensating controls where necessary. Device capability, engineering-tool access, controller hardening, physical access, remote maintenance and the surrounding IT/OT architecture remain part of the result.
Why the profile matters for brownfield EtherCAT systems
Many installed EtherCAT machines were designed primarily around deterministic control, topology and commissioning speed. Replacing every field device to add a new security mechanism would be expensive and could introduce functional risk. ETG's approach is therefore relevant to brownfield plants because it organizes measures that can be applied with currently available technology and combines technical controls with lifecycle processes.
In practice, engineers should first identify which devices are essential to safe and stable operation, how engineering access reaches the EtherCAT master, and where the machine network connects to other zones. Physical topology alone is not a security boundary. Access paths through service laptops, remote-support gateways, virtualization hosts and higher-level Ethernet interfaces need to be included in the system model.
Existing equipment such as the Beckhoff EL1918-2200 TwinSAFE EtherCAT terminal or the Omron GX-JC06 EtherCAT junction slave illustrates the diversity of field devices found in real installations. Those product pages are installed-base references only; they are not evidence that either item, by itself, meets ETG.1800 or any particular security level. The same caution applies to newer architectures that combine CODESYS control and EtherCAT motion on an edge-AI computer: consolidating workloads changes the attack surface and the evidence required for hardening.
CRA timing raises the value of documented engineering
The profile also arrives during implementation of the European Cyber Resilience Act (CRA). The European Commission states that incident and actively exploited vulnerability reporting obligations began on September 11, 2026, while the Act's main product requirements apply from December 11, 2027. ETG positions ETG.1800 as a foundation that can support product and system work before full application.
However, IEC 62443 alignment is not automatically the same as CRA conformity. The CRA places obligations on manufacturers of products with digital elements, including cybersecurity risk assessment, vulnerability handling, support-period information and technical documentation. Suppliers will still need to determine the applicable product classification, conformity-assessment route and evidence for the exact hardware and software placed on the EU market.
Engineering and procurement checks
- Define the system under consideration: document the EtherCAT master, slaves, engineering station, gateways, remote access and adjacent networks.
- Set the target from risk: do not adopt “SL2” as a default label without assessing hazards, exposure and credible attackers.
- Record versions: capture controller firmware, device revisions, EtherCAT configuration files, engineering-tool versions and security settings.
- Verify lifecycle support: ask vendors how vulnerabilities are reported, triaged and corrected, and how long each product will receive security support.
- Test recovery: maintain known-good configurations and prove that a controller, master or engineering workstation can be restored without silently changing timing or safety behavior.
- Request evidence: require suppliers to identify which ETG.1800 measures they support and what remains the integrator's responsibility.
Editorial assessment
ETG.1800 is useful because it gives EtherCAT stakeholders a common structure for discussing security controls that were previously scattered across device features, network design and operating procedures. Its value will depend on implementation detail and auditable evidence. The profile should reduce ambiguity, but it does not remove the need for project-specific risk assessment, secure engineering practices or independent conformity work.
Sources: EtherCAT Technology Group press release, November 19, 2026; European Commission Cyber Resilience Act overview; IEC 62443-3-3 publication overview.