Call us on: +44 (0)121 295 5400

test page

🚨 EN 18031 Emergency Compliance Triage

Quick assessment of your product's compliance risk for EU market launch

1

What type of product are you launching?

Select the category that best describes your product:
IoT sensors or monitoring devices
Smart home devices (lighting, heating, security)
Wearables or fitness trackers
Childcare devices or toys
Industrial automation equipment
Medical or healthcare devices
Payment or financial transaction devices
Other internet-connected device
2

What data does your product process?

Select all that apply to your product:
No personal or sensitive data
Only device operational data
Usage patterns or analytics
Personal information (names, contacts, location)
Traffic or location data
Health or biometric data
Financial or payment data
Virtual currencies or monetary value
Data from children under 16
3

Current security implementation

Select all security features that are already implemented:
No specific security measures
Basic passwords only
Access control mechanisms
Multi-factor authentication (2FA)
Secure storage (encryption at rest)
Secure communication (encryption in transit)
Secure firmware updates
Secure boot process
Cryptographic protection
Logging mechanisms
Data deletion mechanism
User notification mechanisms
Parental controls
Comprehensive security architecture
4

Launch timeline and resources

When is your planned EU market launch?
Tomorrow ()
This week
This month
Flexible timing
Do you have access to cybersecurity expertise?
No internal or external expertise
Limited internal knowledge
Access to external experts
Experienced internal team
🚨
CRITICAL RISK: Launch Not Recommended
Your product has critical EN 18031 compliance gaps that must be addressed before launch. Immediate action is required to implement required security measures.
Immediate Actions:
• Notify stakeholders of launch delay immediately
• Contact cybersecurity experts today
• Estimate 3-6 months for proper compliance
• Consider alternative markets while achieving compliance
📄 Download PDF Report Schedule Emergency Consultation
⚠️
HIGH RISK: Emergency Sprint Needed
Your product might achieve EN 18031 compliance with an emergency development sprint, but success is not guaranteed. Key security mechanisms need implementation.
EN 18031 Requirements to Address:
• Implement required authentication mechanisms
• Add secure storage and communication measures
• Ensure proper access controls
• Complete security testing and documentation
Emergency Sprint Requirements:
• Expert cybersecurity consultation within 24 hours
• Dedicated development team for 2-4 weeks
• Comprehensive security testing and documentation
• Fallback plan if sprint fails
📄 Download PDF Report Schedule Consultation
⚡
MODERATE RISK: Rapid Assessment Needed
Your product appears to have some security foundations but needs immediate expert assessment to confirm EN 18031 compliance. Some requirements may need verification.
EN 18031 Verification Needed:
• Confirm authentication mechanisms meet requirements
• Verify secure storage and communication implementations
• Check access control mechanisms
• Validate compliance documentation
Recommended Actions:
• Professional compliance audit within 48 hours
• Complete gap analysis and documentation review
• Consider 1-2 week delay for verification
• Prepare compliance evidence package
📄 Download PDF Report Schedule Consultation
✅
LOW RISK: Likely Compliant
Based on your responses, your product appears to meet EN 18031 requirements. You have appropriate security measures for your data types and product category.
EN 18031 Compliance Check:
• Authentication mechanisms appear adequate
• Security measures appropriate for data types
• Implementation timeline allows for verification
• Expert resources available for final validation
Final Verification Steps:
• Confirm all compliance documentation is complete
• Verify security testing results
• Prepare for potential market surveillance inquiries
• Use security as competitive advantage in marketing
📄 Download PDF Report Schedule Consultation

Simplified IoT Device Requirements Mapper

Configure your IoT device characteristics to determine which cybersecurity requirements apply

How to Use This Tool

  1. Configure Device Characteristics: Select the characteristics that apply to your IoT device from the left panel.
  2. Review Applicable Requirements: The right panel will show which cybersecurity requirements are applicable to your device.
  3. Filter Requirements: Use the filter buttons to view specific types of requirements (All, Applicable, Not Applicable, Exempt).
  4. View Exceptions: Click on individual requirements to see available exceptions and exemptions.
  5. 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

Relevant clause legend
Control which cybersecurity requirement Clauses are shown in the Device Configuration panel. When a Clause appears under a device characteristic, it indicates that the Clause is relevant to that characteristic and might be applicable to the device.
›

Applicable Cybersecurity Requirements

All Clauses
0
Applicable
0
Not Applicable
0
Exempt
0
Complexity Score
0

Loading requirements...