EN 18031: the cyber evidence behind CE-marked smart glasses
Network-connected radio equipment sold in the EU must now demonstrate cybersecurity, not just radio safety. The EN 18031 standard family turns RED Article 3.3's legal principles into testable requirements covering network protection, personal-data safeguards and fraud prevention. Here is how eyewear programs actually satisfy them.
From radio safety to product cybersecurity
Commission Delegated Regulation (EU) 2022/30 extended the RED essential requirements to cyber for equipment able to communicate over networks — which includes glasses paired to companion apps and cloud services.
Article 3.3 introduced three protection objectives: 3.3(d) network protection, 3.3(e) protection of personal data and privacy, and 3.3(f) prevention of fraud in electronic transactions. They applied on the European Commission's phased timetable beginning with the August 2024 application date, with the standards-based transition and presumption-of-conformity dates running through 2025.
The practical bridge is EN 18031, the harmonised standard family drafted for exactly these articles. "Harmonised" is the key word for brands: building against its published requirements gives presumption of conformity for the articles it covers, which is dramatically easier than defending a bespoke security argument.
Smart glasses sit inside this regime because they are radio equipment that connects — directly or through the companion phone — to networks, process personal data (pairing, camera, microphone, sometimes location), and increasingly participate in authenticated services.


Class 1, 2 or 3 — which requirements bite
EN 18031 classifies devices by the sensitivity of data and functions they handle. Classification decides which parts of the family are in scope; it is confirmed against the actual firmware and companion-app architecture, never by marketing descriptions.
Network equipment
Devices that primarily connect to networks, where the concern is protecting the network itself: traffic behavior, connection discipline, resilience to compromise that could be turned against infrastructure or other users.
Personal-data devices
Equipment that receives, stores, accesses or processes personal data — triggering the additional privacy-focused requirements, with asset protection built around confidentiality, integrity and user control.
Financial-transaction devices
Devices enabling monetary transactions — payments, virtual currency or wallet functions — carry the fraud-prevention requirements on credential handling and transaction integrity.
A device can sit in more than one class at once — a pair of glasses with a companion account and an in-app purchase path handles both personal data and transaction functions. CYNRIN's kickoff review produces the classification statement that goes into the technical file together with the architecture evidence supporting it.
EN 18031-1, -2 and -3
Three published parts, three job descriptions. The engineering file cites the part editions actually assessed and maps each requirement to the design feature or test result that satisfies it.
General & network protection
- Common security vocabulary, asset inventory and threat-model structure
- Secure configuration, minimization of attack surfaces and unused interfaces
- Securely stored cryptographic credentials and key material
- Update integrity and secure-update mechanisms over device lifetime
- Controlled connection behavior protecting networks from overload/misuse
- Log/telemetry discipline and resilience to denial-of-service style misuse
Personal data & privacy
- Confidentiality and integrity of personal data at rest and in transit
- Access control to functions exposing user data, including companion links
- User control: consent, privacy-relevant indicators and reset/deletion paths
- Protection of camera, microphone and sensor data on wearables
- Secure pairing and authentication to the companion application
- Data-minimization in default configuration and in failure states
Fraud / transactions
- Protection of credentials enabling monetary transactions
- Integrity of transaction-related communication and session handling
- Authentication strength proportional to the payment function
- Secure execution environment expectations for stored secrets
- Anti-abuse around account binding and device identity
- In scope only for configurations that actually enable transactions
The control grid engineering actually builds
Cybersecurity conformance is not a single lab certificate — it is a traceability matrix from requirement to implemented control to evidence. Below are the control families that dominate smart-glasses reviews.
Secure pairing
Authenticated BLE pairing flows, user-visible pairing consent and protection against silent reconnection or impersonation.
Encrypted channels
Companion-app and cloud links over modern TLS with certificate validation; no plaintext leak of personal data.
Storage minimization
Camera and account data handled with least-privilege storage and user-accessible factory reset that actually clears it.
Privacy indicators
Clear recording/activation indicators for camera and microphone — aligned with market expectations and platform behavior.
Secure updates
Authenticated firmware delivery, rollback discipline and a defined update-support period communicated to buyers.
Credential protection
No hard-coded shared secrets, protected storage for keys/tokens, and unique device identity where architecture requires it.
Port minimization
Debug interfaces closed in production builds, charging-port discipline and no exposed unauthenticated services.
Traceability file
Threat model, requirement-to-control mapping, test results and update documentation compiled into the RED technical file.
When cyber evidence enters the program calendar
Classification & architecture review
Device class agreed, companion-app data flows mapped, update strategy and pairing model selected; cyber requirements enter the design spec, not a retrofit checklist.
Security implemented & pre-assessed
Pairing, encryption, key storage, indicators, debug-lock and update path implemented; internal review against the EN 18031 requirement list closes gaps early.
External assessment on pilot units
Assessment runs on production-representative firmware and hardware alongside RED RF/EMC/safety testing, feeding the same technical file.
Update support & change control
The secure-update channel is maintained; security-relevant firmware changes follow the same change-control review that protects the radio certification.
Cybersecurity questions from product teams
Our glasses only connect through the user's phone — are they really "network-connected"?
Is EN 18031 a penetration test certificate?
When did these requirements become mandatory?
Who owns the companion-app evidence — CYNRIN or our brand?
Do camera glasses have extra privacy expectations beyond EN 18031?
Can we launch first and add the cyber evidence later?
RED guide
The directive that Article 3.3 and EN 18031 plug into.
Back to RED 02EU market guide
How cyber evidence sits in the full EU launch file.
Explore 03ODM development
Building security into the platform from EVT rather than retrofitting.
Explore 04Classification request
Share your app architecture; receive the class and parts determination.
StartNot sure which EN 18031 class your glasses fall into?
Send the companion-app data flows and planned services. Engineering returns the classification, the requirement matrix and the evidence split between device and app.
