Skip to content

Embedded Security & IoT

Hardware-rooted IoT security — Secure Elements, HSMs, and post-quantum crypto. Designed to CRA and NIS2 requirements.

Reviewed by:
Vladimír Vician
Last reviewed:
Last Updated:
Nov 2026
Service Definition
Hardware-rooted IoT security — Secure Elements, HSMs, and post-quantum crypto. Designed to CRA and NIS2 requirements.

Embedded Security & IoT — Managed End-to-End

What is Embedded Security?

Embedded Security involves integrating cryptographic protection directly into hardware using components like Secure Elements, HSMs, and TPMs. It establishes a hardware root of trust that protects devices from tampering, cloning, and cyberattacks, supporting compliance with the EU Cyber Resilience Act and NIS2 Directive for critical infrastructure and IoT.

Embedded security is the practice of building cryptographic protection directly into hardware — using protected key storage in the microcontroller or in a tamper-resistant Secure Element, together with a verified boot chain, to establish a hardware root of trust. Keys held in protected hardware cannot be read out by malware that compromises the application firmware, although such malware may still be able to use them while it runs. Software-only protection cannot offer even that.

Through our partner network, Inovasense manages IoT projects that are secure by design — targeting compliance with the EU Cyber Resilience Act (EU 2024/2847), NIS2 Directive (EU 2022/2555), and ETSI EN 303 645 for consumer IoT; we are open to industrial projects that have to meet IEC 62443.

Why Hardware Security Matters in 2026

The EU Cyber Resilience Act has required manufacturers to report actively exploited vulnerabilities and severe incidents since 11 September 2026, and its main obligations apply from 11 December 2027: products with digital elements in scope need vulnerability handling, a software bill of materials (SBOM) and security updates for a support period of normally at least five years. “Important” Class II products (e.g. firewalls, tamper-resistant microcontrollers) and “critical” products (e.g. smart meter gateways, smartcards and secure elements) require third-party conformity assessment or, where applicable, European cybersecurity certification.

The CRA does not mandate specific technologies, but hardware-rooted security is often an appropriate way to meet its risk-based requirements.

⚠ Hardware decisions shape CRA and RED compliance.

We don't patch software — we implement physical Hardware Root of Trust on Common Criteria-certified secure elements where the product's risk assessment calls for it. A firmware update cannot add protected key storage that the hardware does not have.

Book a Compliance Gap Analysis →
  • Tamper-resistant key storage — The secure element is designed so that keys never leave it; certified parts are evaluated against physical and side-channel attacks
  • Secure (verified) boot — Every firmware stage is cryptographically verified before it runs, so modified firmware does not start
  • Physical attack resistance — Active mesh shields, voltage glitch detectors, and light sensors detect and respond to physical intrusion attempts
  • Lifecycle security — Secure provisioning, key rotation, certificate management, and end-of-life decommissioning managed through hardware
  • Post-quantum readiness — Hybrid key exchange (ML-KEM + X25519) and digital signatures (ML-DSA) protecting against future quantum threats

Security Architecture Stack

Hardware Root of Trust

Projects integrate certified security ICs from leading European manufacturers (STMicroelectronics, Infineon, NXP) to ensure hardware sovereignty:

ComponentProductsCertificationPost-quantum cryptography
Secure ElementsSTMicroelectronics STSAFE-A110, Infineon OPTIGA Trust M, NXP EdgeLock SE050CC EAL5+ (STSAFE-A110); CC EAL6+ (OPTIGA Trust M, SE050)Classical algorithms only; no PQC support stated by the vendors
TPM ModulesSTMicroelectronics ST33 (TPM 2.0), Infineon SLB 9672TCG TPM 2.0; FIPS 140 validation depends on part and firmware (SLB 9672: FIPS 140-2)SLB 9672: firmware update protected by a post-quantum signature (XMSS)
Java CardSTMicroelectronics ST31 / STPay, NXP JCOP4CC EAL6+, EMVCoDepends on the card platform
Secure MCUsSTM32H5 / STM32U5 (TrustZone), NXP LPC55SPSA Certified Level 3 (STM32U585, STM32H573); Level 2 (LPC55S1x)Software libraries
Secure EnclavesSTM32MP2 (TrustZone)PSA Certified Level 3 RoT Component (STM32MP25x)Software libraries

Cryptographic Implementation

  • Symmetric: AES-128/256-GCM (hardware accelerated), ChaCha20-Poly1305
  • Asymmetric: ECC P-256/P-384, Ed25519/Ed448, RSA-3072/4096
  • Post-Quantum (NIST standards): ML-KEM-768/1024 (key encapsulation), ML-DSA-65/87 (digital signatures), SLH-DSA (stateless hash-based signatures)
  • Hybrid schemes: X25519 + ML-KEM for TLS 1.3, ECDSA + ML-DSA for firmware signing
  • Hashing: SHA-256, SHA-3, SHAKE-256, HMAC for message authentication
  • Key management: HKDF derivation, X.509v3 certificate chains, PKCS#11 interfaces, DICE (Device Identifier Composition Engine)

Secure Boot & Firmware Protection

Secure boot implementations follow the ARM PSA (Platform Security Architecture) model:

  1. Immutable bootloader — Stored in ROM, cryptographically verifies the next stage using Ed25519 or ML-DSA
  2. Chain of trust — Each boot stage authenticates the next; root of trust anchored in hardware fuses
  3. Runtime integrity — Memory protection units (MPU) and TrustZone enforce process isolation
  4. Secure OTA updates — Signed firmware packages (SUIT manifest) with atomic rollback on verification failure
  5. SBOM integration — Automated Software Bill of Materials generation for CRA compliance

Java Card Application Development

Java Card is a secure execution environment running on certified Smart Card ICs (CC EAL6+), enabling tamper-resistant applet deployment for payment, identity, access control, and IoT authentication. Through our partner network, we deliver custom Java Card applications on STMicroelectronics ST31/STPay and NXP JCOP4 platforms, working with certified Smart Card integrators where required.

What We Deliver

  • Custom Applet Development — Secure applets in Java Card 3.1 for payment (EMVCo), transport ticketing, government eID, and corporate access control
  • Payment Solutions — EMV contact/contactless payment applets, tokenization, and STPay-based secure wallet implementations for fintech and banking
  • Identity & Access — PKI-based digital identity, FIDO2/WebAuthn authenticators, and X.509 certificate management on secure elements
  • IoT Device Authentication — Mutual TLS authentication using Java Card-hosted certificates, device attestation, and secure provisioning for fleet management
  • NFC & Contactless — ISO 14443 / ISO 7816 compliant applets for contactless transactions, building access, and smart city infrastructure

Platforms & Certification

PlatformTypeCertificationUse Cases
ST31 / STPay (STMicroelectronics)Secure Smart Card ICCC EAL6+, EMVCoPayment, transport, eID
NXP JCOP4Java Card OS on SECC EAL6+, FIDOIdentity, access control
Infineon SLE 78Security ControllerCC EAL6+Government ID, healthcare

All Java Card solutions include GlobalPlatform compliant secure channel provisioning, applet lifecycle management, and remote applet management (RAM) capabilities.

Wireless Connectivity for IoT

Projects target connectivity solutions matched to each application’s power, range, and bandwidth requirements:

ProtocolRangeData RatePowerBest For
Bluetooth LE (5.4 or later)100m2 MbpsUltra-lowWearables, asset tags, PAwR
LoRaWAN 1.0.415km50 kbpsVery lowEnvironmental monitoring, metering
NB-IoT (Rel-17)Cellular250 kbpsLowWide-area asset tracking
Wi-Fi 7 (802.11be)50m5.8 GbpsMediumReal-time video, gateways
Thread 1.4/Matter30m250 kbpsLowSmart home/building, interop
5G RedCap (Rel-17)Cellular150 MbpsMediumIndustrial IoT, autonomous
DECT NR+ (2024)1km3 MbpsLowPrivate industrial mesh, non-cellular

Ultra-Low Power Design

IoT projects target multi-year battery life through:

  • Sleep mode optimization — Current consumption <500 nA in deep sleep with RTC wake
  • Duty cycling — Intelligent scheduling algorithms reduce active time to <0.1%
  • Energy harvesting — Solar (indoor/outdoor), thermoelectric, and vibration harvesting circuits
  • Power profiling — Actual current consumption is measured at every design stage using analyzers like Otii Arc and PPK2
  • Battery chemistry optimization — LiFePO4 for extreme temperature, solid-state cells for longevity, supercapacitor hybrid topologies

From our projects: the Secure Logistics Smart Tag is a functional prototype of a shipment tag that signs its records in a secure element.

Compliance & Certification (2026)

RegulationEffectiveRequirementHow We Help
EU Cyber Resilience Act (EU 2024/2847)Reporting since 11 Sep 2026; main obligations from 11 Dec 2027Vulnerability handling, SBOM, security updates for the support period (normally at least 5 years)Secure-by-design architecture, automated SBOM, CRA technical file
NIS2 Directive (EU 2022/2555)Oct 2024Supply chain security for essential and important entitiesSecure development lifecycle, incident response plan
IEC 62443OngoingIndustrial automation securityWe are open to projects that have to meet it
ETSI EN 303 645OngoingConsumer IoT security baselineAll 13 provisions: no default passwords, secure storage, minimal attack surface
RED Delegated Act (2022/30)Since 1 Aug 2025; repealed from 11 Dec 2027Cybersecurity for radio equipmentSecure boot, authenticated updates, network protection
GDPR Art. 25OngoingData protection by designPrivacy-preserving architecture, local processing, minimal data collection
EU AI Act (2024/1689)2025–2028 (high-risk: 2 Dec 2027 / 2 Aug 2028)AI system risk classificationConformity assessment support for edge AI-enabled IoT

All security architectures are designed and documented within the European Union. Standard deliverables include threat model documentation (STRIDE/DREAD), security test reports, SBOM, and compliance gap analyses.

Sources & Official References

Guides in this area

Frequently Asked Questions

What is embedded security in IoT?

Embedded security in IoT means anchoring cryptographic protection in hardware: an immutable boot stage and protected key storage in the microcontroller itself, or a dedicated Secure Element or TPM. Keys held in protected hardware cannot be read out by malware that takes over the application firmware, which software-only protection cannot offer. Inovasense manages IoT projects with a hardware root of trust that support the security requirements of the EU Cyber Resilience Act.

Why is hardware security important for IoT devices?

Software-only protection keeps its keys where a successful attack on the firmware can reach them. Hardware security provides a root of trust that protects cryptographic keys, anchors secure boot and helps prevent unauthorized firmware updates. The EU CRA does not prescribe a technology, but for many connected products this is an appropriate way to meet its risk-based requirements.

What is the EU Cyber Resilience Act?

The EU Cyber Resilience Act (CRA, Regulation (EU) 2024/2847) sets cybersecurity requirements for products with digital elements within its scope, including vulnerability handling, an SBOM and security updates for a support period of normally at least five years. Reporting obligations have applied since 11 September 2026; the main obligations apply from 11 December 2027.

Regulatory References (Authority Source)