Smart eyewear OEM/ODM manufacturer · Shenzhen, China +86 19835872450 sales@cynrin.com
RED ARTICLE 3.3 · CYBERSECURITY STANDARDS

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.

LEGAL ORIGIN

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.

Smart glasses mainboard with radio, processor and security-relevant components
Engineering design review where firmware security configuration is assessed
STEP 1 · CLASSIFICATION

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.

Glasses relevance: the always-present baseline; pairing and data-transfer behavior are assessed here even when the device only connects through the phone.

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.

Typical smart-glasses fit: companion-account pairing, camera/microphone data, contact lists, location and usage telemetry place connected eyewear squarely in this class for most programs.

Financial-transaction devices

Devices enabling monetary transactions — payments, virtual currency or wallet functions — carry the fraud-prevention requirements on credential handling and transaction integrity.

Glasses relevance: base camera/audio programs are not in class 3; products that enable payment or wallet flows through the companion service must address part 3 scope.

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.

STEP 2 · THE STANDARDS

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.

EN 18031-1

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
EN 18031-2

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
EN 18031-3

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
STEP 3 · WHERE IT SHOWS UP IN THE PRODUCT

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.

IDENTITY

Secure pairing

Authenticated BLE pairing flows, user-visible pairing consent and protection against silent reconnection or impersonation.

DATA IN TRANSIT

Encrypted channels

Companion-app and cloud links over modern TLS with certificate validation; no plaintext leak of personal data.

DATA AT REST

Storage minimization

Camera and account data handled with least-privilege storage and user-accessible factory reset that actually clears it.

SENSORS

Privacy indicators

Clear recording/activation indicators for camera and microphone — aligned with market expectations and platform behavior.

MAINTENANCE

Secure updates

Authenticated firmware delivery, rollback discipline and a defined update-support period communicated to buyers.

KEYS

Credential protection

No hard-coded shared secrets, protected storage for keys/tokens, and unique device identity where architecture requires it.

SURFACE

Port minimization

Debug interfaces closed in production builds, charging-port discipline and no exposed unauthenticated services.

EVIDENCE

Traceability file

Threat model, requirement-to-control mapping, test results and update documentation compiled into the RED technical file.

TIMING

When cyber evidence enters the program calendar

KICKOFF · REQUIREMENTS LOCK

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.

EVT–DVT · BUILD CONTROLS

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.

PVT · FORMAL EVIDENCE

External assessment on pilot units

Assessment runs on production-representative firmware and hardware alongside RED RF/EMC/safety testing, feeding the same technical file.

POST-LAUNCH · LIFETIME

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.

EN 18031 FAQ

Cybersecurity questions from product teams

Our glasses only connect through the user's phone — are they really "network-connected"?
Yes. The delegation covers radio equipment able to communicate via networks, including equipment whose data path runs through a companion phone to internet services. BLE pairing plus a companion app that contacts cloud services puts the product inside the scope; the architecture review determines which device class applies and which EN 18031 parts are in scope, not the marketing description of the connection.
Is EN 18031 a penetration test certificate?
No. It is a harmonised requirements standard: conformity is demonstrated through a combination of design documentation, threat analysis, implemented controls and test evidence, rather than a single pass/fail pentest certificate. Security testing supports the file, but the bulk of evidence is a traceability matrix showing each requirement is met by a defined control — which is why security must be designed in at EVT.
When did these requirements become mandatory?
The obligations in Commission Delegated Regulation (EU) 2022/30 applied on the Commission's phased timetable starting 1 August 2024, with the standards-transition and presumption-of-conformity dates for the EN 18031 family running through 2025. The exact article/standard status for a specific shipment month is confirmed in the kickoff certification plan against the current Official Journal listings; market-surveillance practice treats firmware configuration, not launch announcement dates, as the reference point.
Who owns the companion-app evidence — CYNRIN or our brand?
It is split by ownership. CYNRIN is responsible for the embedded firmware, BLE behavior, device-side data handling and update mechanisms it develops; the brand (or its app vendor) owns the companion application and cloud service evidence — server-side access controls, privacy policy, consent flows, account security. EN 18031-2 evidence combines both sides, and the program plan lists which documents each party supplies.
Do camera glasses have extra privacy expectations beyond EN 18031?
Recording indicators and privacy behavior also face member-state expectations and platform/retailer policies even beyond the standard text; the 3.3(e) requirements formalize data protection at the device level while GDPR governs the wider processing by brand and app. Programs review indicator design, recording signals and data-retention defaults with the brand's privacy counsel — see the wellness/medical boundary page for adjacent claim hygiene.
Can we launch first and add the cyber evidence later?
Not safely. Placing radio equipment on the EU market presumes conformity against all applicable essential requirements, and post-launch retrofit of secure pairing, update channels or debug-port lockdown can require hardware or firmware changes that invalidate existing test evidence. Building the EN 18031 matrix at kickoff is by far the cheaper path, consistent with how ODM programs sequence certification.

Not 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.

Chat on WhatsApp
Your experience on this site will be improved by allowing cookies.