IoT Cybersecurity Requirements Mapper Tool
IoT Device Cybersecurity Requirements Mapper
Configure your IoT device characteristics to determine which cybersecurity requirements apply (EN 18031 Series)
How to Use This Tool
- Configure Device Characteristics: Select the characteristics that apply to your IoT device from the left panel.
- Review Applicable Requirements: The right panel will show which cybersecurity requirements are applicable to your device.
- Filter Requirements: Use the filter buttons to view specific types of requirements (All, Applicable, Not Applicable, Exempt).
- View Exceptions: Click on individual requirements to see available exceptions and exemptions.
- Understand Complexity: Review the complexity scores to understand the implementation effort required.
Legal Disclaimer
This tool is for informational purposes only. Always consult experienced technical professionals before starting any product development. The information provided does not constitute legal advice and should not be relied upon as the sole basis for compliance decisions.
Device Configuration
Standard Legend:
Applicability Legend:
Standards & Visibility Controls:
Select which standards to be shown in the Device Configuration panel and display the relevant clauses that are applicable (and not applicable) to the device.
Quick Guide
Our mapper identifies your specific certification path based on the restricted clauses of EN 18031.
Whether your results indicate a Self-Declaration or a Notified Body requirement, the technical file you build now serves as the mandatory foundation for your September 2026 vulnerability reporting and December 2027 CRA compliance.
Technical Logic: How this Assessment Maps to EN 18031 & CRA
Assessment Criteria: This tool evaluates your hardware against the restricted clauses of the EN 18031 series (specifically clauses 6.2.5.1 and 6.2.5.2 regarding password bypass).
Notified Body Trigger: We prioritise the “Safer Pathway” logic. If your product handles childcare data or high-sensitivity biometrics, the tool defaults to Notified Body requirements to mitigate market exclusion risks.
Data Integrity: Calculations for financial transaction security (Part 3) assume a baseline of cryptographic verification as mandated by the August 2025 enforcement.
- For a detailed guide, see our 2026 Compliance Blog
Next Steps for your 2026 Launch
Need a Rapid Compliance Sprint to hit a Q2 2026 window? Contact our Engineering Consultants
Require Electronic Redesign to meet security-by-design standards?
Starting your BOM Monitoring for the September 2026 reporting deadline?