Technical documentation
Example: Lumo Smart Plug · model LSP-2 · firmware 2.4.1
Manufacturer: Example Devices Ltd, Unit 4, 12 Harbour Road, Tallinn, Estonia. Prepared under Article 31 and Annex VII of Regulation (EU) 2024/2847 (Cyber Resilience Act). Keep for at least 10 years after placing on the market or for the support period, whichever is longer (Art. 13(13)).
| Item | Value |
|---|---|
| Product category | Default category (not listed in Annex III or IV) |
| Conformity assessment route | Choose one: internal control (module A, Annex VIII Part I); EU-type examination (module B) followed by conformity to type based on internal production control (module C); full quality assurance (module H); or a European cybersecurity certification scheme where available. (Art. 32(1)) |
| Placed on the market | 1 March 2025 |
| End of support period | March 2030 |
| Document version | 27 October 2026 |
1. General description (Annex VII, (1))
(a) Intended purpose
Wi-Fi smart plug for home use. Switches mains appliances up to 16 A and measures energy use. Controlled from a mobile app through the manufacturer's cloud, or locally on the home network.
Essential functions: switching the load on and off, schedules, energy metering, over-the-air firmware updates
(b) Software versions affecting compliance
Firmware/software version 2.4.1. Identification scheme: serial number printed on the rating label and shown in the app under Device info.
(c) Photographs and illustrations
[to complete: reference to photographs of external features, marking and internal layout]
(d) User information and instructions
See the document "Information and instructions for users" (Annex II), attached as Appendix A.
2. Design, development and vulnerability handling (Annex VII, (2))
(a) System architecture
Single Wi-Fi SoC running lwIP and mbedTLS on an RTOS. A bootloader verifies the signed firmware image. The app talks to the cloud API over TLS; the cloud relays commands over MQTT.
(b) Vulnerability handling
Software bill of materials: 6 components, maintained in CycloneDX 1.5 format (Appendix C).
| Component | Version | Supplier | Identifier |
|---|---|---|---|
| openssl | 1.1.1k | OpenSSL Project | pkg:generic/openssl@1.1.1k |
| zlib | 1.2.11 | zlib | pkg:generic/zlib@1.2.11 |
| busybox | 1.33.0 | BusyBox | pkg:generic/busybox@1.33.0 |
| lwip | 2.1.2 | lwIP | pkg:generic/lwip@2.1.2 |
| mbedtls | 2.16.0 | Mbed TLS | pkg:generic/mbedtls@2.16.0 |
| lumo-local-api | 2.4.1 | Example Devices Ltd | pkg:generic/lumo-local-api@2.4.1 |
Coordinated vulnerability disclosure policy: Appendix B, published at https://example.com/security. Contact for vulnerability reports: security@example.com.
Secure distribution of updates: Firmware images are signed with ECDSA P-256; the bootloader rejects unsigned images. Updates install automatically at night unless the user postpones them in the app.
Vulnerability monitoring: last scan 29 September 2026 (example data): 7 known vulnerabilities in components, 3 critical, 1 on the CISA known-exploited list. Whether each finding is present and exploitable in this build, and its remediation, is recorded under Annex I, Part I, (2)(a) and Part II, (2) in section 3.
(c) Production and monitoring
[to complete: production and monitoring processes and their validation]
3. Cybersecurity risk assessment (Annex VII, (3); Art. 13(2)-(4))
Known or foreseeable circumstances that may lead to significant cybersecurity risks: Use on an open Wi-Fi network; exposing the local control port to the internet through port forwarding; reusing the default pairing code.
Application of the essential requirements, Annex I Part I:
| Ref | Requirement | Status | How the product meets it |
|---|---|---|---|
| Part I, (1) | Products shall be designed, developed and produced to ensure an appropriate level of cybersecurity based on the risks. | In progress | Threat model drafted for cloud, app and local interfaces. |
| Part I, (2)(a) | Be made available on the market without known exploitable vulnerabilities. | Open | [to complete: how the product meets this] |
| Part I, (2)(b) | Be made available with a secure by default configuration, unless otherwise agreed for tailor-made products, including the possibility to reset the product to its original state. | Evidence attached | Unique pairing code per device; local port closed until paired; factory reset by 10-second button press. |
| Part I, (2)(c) | Ensure vulnerabilities can be addressed through security updates, including, where applicable, automatic security updates installed within an appropriate timeframe and enabled as a default setting, with a clear and easy-to-use opt-out, user notification of available updates and the option to temporarily postpone them. | Evidence attached | Signed OTA updates, automatic by default, user can postpone for 7 days. |
| Part I, (2)(d) | Ensure protection from unauthorised access by appropriate control mechanisms, including but not limited to authentication, identity or access management systems, and report on possible unauthorised access. | Open | [to complete: how the product meets this] |
| Part I, (2)(e) | Protect the confidentiality of stored, transmitted or otherwise processed data, personal or other, e.g. by encrypting relevant data at rest or in transit by state of the art mechanisms, and by using other technical means. | Open | [to complete: how the product meets this] |
| Part I, (2)(f) | Protect the integrity of stored, transmitted or otherwise processed data, commands, programs and configuration against any manipulation or modification not authorised by the user, and report on corruptions. | Open | [to complete: how the product meets this] |
| Part I, (2)(g) | Process only data, personal or other, that are adequate, relevant and limited to what is necessary for the intended purpose (data minimisation). | Open | [to complete: how the product meets this] |
| Part I, (2)(h) | Protect the availability of essential and basic functions, also after an incident, including through resilience and mitigation measures against denial-of-service attacks. | Open | [to complete: how the product meets this] |
| Part I, (2)(i) | Minimise the negative impact by the product itself or connected devices on the availability of services provided by other devices or networks. | Open | [to complete: how the product meets this] |
| Part I, (2)(j) | Be designed, developed and produced to limit attack surfaces, including external interfaces. | Open | [to complete: how the product meets this] |
| Part I, (2)(k) | Be designed, developed and produced to reduce the impact of an incident using appropriate exploitation mitigation mechanisms and techniques. | Open | [to complete: how the product meets this] |
| Part I, (2)(l) | Provide security-related information by recording and monitoring relevant internal activity, including access to or modification of data, services or functions, with an opt-out mechanism for the user. | Open | [to complete: how the product meets this] |
| Part I, (2)(m) | Allow users to securely and easily remove, on a permanent basis, all data and settings and, where such data can be transferred to other products or systems, ensure this is done in a secure manner. | Open | [to complete: how the product meets this] |
Vulnerability handling requirements, Annex I Part II:
| Ref | Requirement | Status | How the manufacturer meets it |
|---|---|---|---|
| Part II, (1) | Identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies. | Open | [to complete: how the product meets this] |
| Part II, (2) | In relation to the risks posed, address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, provide new security updates separately from functionality updates. | Open | [to complete: how the product meets this] |
| Part II, (3) | Apply effective and regular tests and reviews of the security of the product. | Open | [to complete: how the product meets this] |
| Part II, (4) | Once a security update has been made available, share and publicly disclose information about fixed vulnerabilities (description, affected product, impacts, severity, remediation guidance); disclosure may be delayed in duly justified cases where security risks outweigh the benefits, until users have had the possibility to apply the patch. | Open | [to complete: how the product meets this] |
| Part II, (5) | Put in place and enforce a policy on coordinated vulnerability disclosure. | Evidence attached | Policy published at example.com/security. |
| Part II, (6) | Take measures to facilitate the sharing of information about potential vulnerabilities in the product and its third-party components, including by providing a contact address for reporting vulnerabilities. | Open | [to complete: how the product meets this] |
| Part II, (7) | Provide mechanisms to securely distribute updates so that vulnerabilities are fixed or mitigated in a timely manner and, where applicable for security updates, in an automatic manner. | Open | [to complete: how the product meets this] |
| Part II, (8) | Ensure that security patches or updates addressing identified security issues are disseminated without delay and, unless otherwise agreed for a tailor-made product, free of charge, accompanied by advisory messages giving users the relevant information, including on potential action to be taken. | Open | [to complete: how the product meets this] |
4. Support period (Annex VII, (4); Art. 13(8))
Support period ends March 2030. Basis: Expected use time of comparable smart plugs is 5 to 7 years. The Wi-Fi SoC vendor supports the SDK until 2031.
5. Standards and specifications applied (Annex VII, (5))
Standards and specifications applied: [to complete: harmonised standards applied, and other specifications or solutions adopted]
6. Test reports (Annex VII, (6))
[to complete: list of test reports (penetration test, fuzzing, update test)]
7. EU declaration of conformity (Annex VII, (7))
See Appendix D.
8. Software bill of materials (Annex VII, (8))
Provided to market surveillance authorities on reasoned request. File: example-lumo-smart-plug-sbom.cdx.json.
Appendices: A. Information and instructions for users · B. Coordinated vulnerability disclosure policy · C. SBOM (CycloneDX) · D. EU declaration of conformity
Prepared with Readymark from information you entered. Review before signing; this is not legal advice.