TLS and DTLS
Client and server protocol support up to TLS 1.3 and DTLS 1.3, subject to build configuration.
wolfSSL Embedded Security Portfolio
A configurable portfolio for TLS/DTLS, cryptographic services and authenticated firmware boot and update workflows across supported embedded platforms.
wolfSSL TLS/DTLSwolfCrypt crypto enginewolfBoot secure bootPlatform integrations
Device security stack
InputsIdentity, keys & policyHardware capabilities
Engineering controlsTLS / DTLSCryptographic servicesBoot & update control
OutputsTLS/DTLS sessionsCryptographic operationsAuthorized firmware
Security component layer inside a product-specific trust and update architecture.
Product security depends on integration, keys, entropy, trust anchors, update operations, application logic and platform integrity—not only the selected library.
wolfSSLEmbedded security
Core capabilities
Core engineering capabilities
Exact capabilities depend on the selected edition, release and deployment environment.
Cryptographic engine
Portable algorithms and APIs for embedded, RTOS and constrained environments.
Hardware acceleration
Use supported MCU, secure-element, TPM or hardware cryptographic capabilities where available.
Secure boot
Authenticate firmware before handover according to the configured boot policy.
Firmware update control
Support authenticated update, recovery and rollback strategies based on target architecture.
Assurance options
Commercial support, selected long-term support and separately scoped validated cryptographic module options.
Implementation workflow
From evaluation to deployment
Validate the technology in the real build, target and reporting environment before wider rollout.
- 01Define threat and trust model
- 02Select component boundary
- 03Configure algorithms and protocols
- 04Port hardware and I/O
- 05Provision keys and certificates
- 06Verify boot, update and failure handling
Confirm the deployment fit
Compatibility depends on the actual toolchain, target environment, integration needs and assurance objectives.
- MCU/MPU, memory and performance constraints
- Protocol and cipher requirements
- Entropy and key-storage architecture
- Secure-element or hardware acceleration interface
- Bootloader, flash and update topology
- Licensing, support and validation boundary
Where the technology adds value
Well suited for
- Connected embedded products
- Resource-constrained TLS/DTLS endpoints
- Products requiring controlled firmware authenticity
- Teams needing portable cryptographic components
Important considerations
- The software components form part of a wider device-security architecture.
- Compliance depends on the complete integration, process and evidence set.
- Secure provisioning requires controlled manufacturing and operational processes.
- Validated-module claims must match the exact certificate and operating environment.
Related capabilities
Extend the software assurance workflow
Explore adjacent capabilities across requirements, verification, testing and embedded security.