Rune Hillebo Wiinberg & Johan Callmyr
Connected product? EN 18031 may be more relevant than you think
A connected product does not need to look particularly high-tech to face cybersecurity requirements. It could be a wearable device. A connected toy. A piece of industrial equipment. A consumer product communicating through Wi-Fi or another radio technology. If a device contains radio functionality and communicates with the internet – directly or indirectly – cybersecurity requirements under the Radio Equipment Directive may be relevant.
Why EN 18031 matters
Since 1 August 2025, the cybersecurity requirements introduced through the Radio Equipment Directive Delegated Act apply to affected products.
For manufacturers, that makes one question particularly important: Does this apply to our product?
The EN 18031 series addresses cybersecurity requirements connected to Articles 3.3 (d), 3.3 (e) and 3.3 (f) of the Radio Equipment Directive Delegated Act. The standards cover different types of cybersecurity risks.
Understanding the difference is a useful first step.

EN 18031-1 – protecting networks
EN 18031-1 addresses general cybersecurity requirements for internet-connected radio equipment. In simplified terms, it focuses on protecting networks and preventing connected equipment from harming the network or misusing network resources.
This can be relevant to a wide range of products because connectivity is now present in everything from consumer products to industrial equipment.
The question is therefore not necessarily whether the product looks like a traditional IT device. The important question is what it connects to and how it communicates.
EN 18031-2 – protecting privacy and personal data
The second part focuses on personal data and privacy.
It is relevant to radio equipment that processes personal, traffic or location data and includes categories such as internet-connected radio equipment, childcare devices, toys and wearable equipment. That creates another dimension for manufacturers.
Cybersecurity is not only about preventing someone from taking control of a product. It can also be about protecting the information the product collects, processes or communicates.
As more everyday products become connected, that distinction becomes increasingly important.
EN 18031-3 – protecting against fraud
The third part addresses fraud. It focuses on internet-connected radio equipment that processes money, monetary value or virtual currency.
Here, cybersecurity and financial risk become directly connected. A vulnerability is no longer only a technical issue. It may potentially enable financial abuse.
Which requirements apply to you?
The answer depends on the product.
What does it connect to? What information does it process? Does it handle personal information? Does it enable financial transactions?
Those questions help determine which parts of the standard series are relevant.
For companies with large product portfolios, the assessment can become more complicated. Different products may have different functionality and therefore fall under different requirements. This makes a structured product-by-product assessment valuable.
What if cybersecurity was not part of the original design?
This is where many manufacturers face the real challenge. Products may have been designed years before today's requirements were known. They may use architectures that are difficult to update or contain software components that were not selected with cybersecurity in mind.
Simply knowing that a requirement applies does not automatically reveal the best technical solution.
The first step is understanding the gap between the current product and what is required. From there, manufacturers can prioritize changes and create a practical plan.
For one product, that might involve relatively limited modifications. For another, it could require changes to architecture, software, documentation or development processes.
Turn uncertainty into concrete questions
Cybersecurity legislation and standards can feel complex when approached as acronyms and documents. RED-DA. EN 18031-1. EN 18031-2. EN 18031-3. But behind the terminology are relatively tangible questions.
- What does your product connect to?
- What needs to be protected?
- Which data does it handle?
- What could happen if the product or its communication were compromised?
Once those questions are answered, the technical challenge becomes much easier to define. And that is usually where good cybersecurity work begins: not with an acronym, but with understanding the product.
The cybersecurity requirements introduced through the Radio Equipment Directive Delegated Act (RED-DA) have applied since 1 August 2025. Radio equipment within scope and placed on the EU market from this date must comply with the applicable RED cybersecurity requirements.
For manufacturers, this makes it important to understand which requirements apply to their products and what changes may be needed. Many of the cybersecurity controls relevant to RED-DA are also applicable to the upcoming Cyber Resilience Act (CRA), making the work relevant beyond the immediate requirements.
explore
Explore Cybersecurity Insights
- From cybersecurity requirements to a working medical product – the Ably Medical story
Rune Hillebo Wiinberg & Johan Callmyr

- Cybersecurity doesn’t end when your product leaves R&D
Rune Hillebo Wiinberg & Johan Callmyr

- Connected product? EN 18031 may be more relevant than you think
Rune Hillebo Wiinberg & Johan Callmyr

- Security by design – what does it actually mean for embedded products?
Rune Hillebo Wiinberg & Johan Callmyr

Some Areas of Expertise
About the Authors
Rune Hillebo Wiinberg is Head of Cybersecurity at Prevas and has worked professionally with embedded and secure, connected products since 2007. With experience across energy, medical technology and defense, he advises customers at all levels of the organization, helping bridge business priorities, regulatory requirements and technical product development.
Johan Callmyr is a Software Architect with more than 20 years of experience in C++ and embedded device software. He combines technical expertise with his experience in software architecture, technical leadership, cybersecurity, and development in regulated environments like medtech. As a Software Architect and Software Lead, he helps customers build robust, secure, and safe software solutions for complex products.