The Extensible Authentication Protocol (EAP) framework is designed to support secure connections for embedded devices. HCC provides support for many “flavors” of EAP and the framework easily extends to include other protocols. Commonly used algorithms include EAPOL, EAP-TLS, EAP-IKEv2, and EAP-MD5.
EAP is used for device authentication and supports many types of secure access. It provides a basic request/response protocol framework over which specific security algorithms can be implemented. This approach gives developers a way to ensure that industrial, medical, and transport IoT devices that join a network are authenticated. This helps to create a robust and secure network.
HCC’s EAP components are fully compliant with all relevant RFCs and come with a full test suite to verify correct operation on the target system. The EAP framework is developed according to HCC’s MISRA coding standard and provides a high degree of reliability on any embedded target. When used with HCC’s MISRA-compliant networking stack, engineers can develop a secure, high quality IoT application quickly and with confidence. HCC's EAP components are compatible with third party TLS implementations, including Mbed TLS as well as other free versions.
HCC is committed to ensuring that security problems caused by issues related to software quality are eliminated. HCC’s EAP framework is available with full MISRA compliance reports and additional life-cycle evidence, including high-level design and functional specification, are supplied on request.
To help ensure seamless connectivity of secure networking, HCC has also joined the Wi-SUN Alliance™ as an adopter member. The Wi-SUN Alliance seeks to advance seamless connectivity by promoting the IEEE 802.15.4g™ standard-based interoperability for global regional markets. HCC’s EAP framework passes Wi-SUN interoperability tests and conforms fully to Wi-SUN certification requirements.
- Conforms to the HCC Advanced Embedded Framework.
- Complies with the HCC MISRA-compliant TCP/IP stack.
- Supports third party TLS solutions, including Mbed TLS and other free versions
- Designed for integration with both RTOS and non-RTOS based systems.
- EAPOL implementation complies with RFC 3748.
- EAP MD5-Challenge implementation complies with RFC 2284.
- EAP-TLS implementation complies with RFC 5216.