Digi ConnectCore Security Module
Caveat: When built, installed, protected and initialized as assumed by the Crypto Officer role and as specified in the provided Security Policy. Appendix A of the provided Security Policy specifies the actual distribution tar file containing the source code of this module. There shall be no additions, deletions or alterations to the tar file contents as used during module build. The distribution tar file shall be verified as specified in Appendix A of the provided Security Policy. Installation and protection shall be completed as specified in Appendix A of the provided Security Policy. Initialization shall be invoked as per Section 4 of the provided Security Policy. Any deviation from specified verification, protection, installation and initialization procedures will result in a non FIPS 140-2 compliant module. This validation entry is a non-security relevant modification to Cert. #2398
Certificate
| Certificate number | 3176 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Digi International, Inc. · website |
| Software versions | 1.0 |
Module description
The Digi ConnectCore Security Module provides cryptographic services for Digi International Inc. products.
Security level exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms
Allowed algorithms
EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)
Tested configurations
- Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) without PAA (gcc Compiler Version 7.3.0), Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) with PAA (gcc Compiler Version 7.3.0) (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2018-04-26 | Initial | Acumen Security |
| 2018-06-12 | Update | Acumen Security |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status historical
- Validation dates on record: 2018-04-26, 2018-06-12