Cradlepoint Cryptographic Module

Certificate

Approved Algorithms (33)

Derived Review-Risk Graph (review prompts, not findings)

flowchart LR
  %% Deterministic review-risk graph for Cradlepoint Cryptographic Module
  %% Review prompts and evidence gaps, NOT vulnerability findings.
  subgraph CMVP["CMVP-disclosed clues"]
    C3["[low] Self-test / status surface<br/>(referenced in text)<br/><i>Self-Test<br/>Status Output</i>"]
    C5["[low] Protocol / secure-channel<br/>references (may be KDF<br/>names, not a live channel)<br/><i>TLS<br/>HTTPS<br/>library named: openssl</i>"]
    C6["[low] Operating system / runtime<br/>referenced (boundary<br/>membership not asserted)<br/><i>operating system<br/>kernel<br/>application</i>"]
  end
  subgraph Inference["Derived inference"]
    I3["Possible only, some<br/>services may process input<br/>before, or without,<br/>operator authentication."]
    I5["Possible only, a protocol<br/>is referenced, but whether<br/>it is a live channel or<br/>only a KDF/algorithm name<br/>is unconfirmed."]
    I6["Possible only, a<br/>runtime/OS is referenced,<br/>but its membership in the<br/>cryptographic boundary is<br/>not established."]
  end
  subgraph Risk["Reviewer question"]
    R3["Can unauthenticated<br/>services leak state,<br/>consume resources, or<br/>transition security state?"]
    R5["If a live TLS/SSH/IKE<br/>channel exists, could<br/>library CVEs apply, or is<br/>this only a<br/>KDF/documentation name?"]
    R6["If the OS/runtime is<br/>in-boundary, could its<br/>CVEs be hidden by<br/>firmware-only versioning?"]
  end
  subgraph Evidence["Evidence needed to close"]
    E3["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>pre-auth reachability<br/>matrix · rate limits and<br/>output redaction ·<br/>abuse-case tests"]
    E5["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>library identity and<br/>version ·<br/>certificate-validation<br/>behaviour · protocol-CVE<br/>disposition"]
    E6["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>runtime identity and<br/>config · kernel/runtime<br/>hardening profile ·<br/>patch/backport manifest"]
  end
  C3 --> I3 --> R3 --> E3
  C5 --> I5 --> R5 --> E5
  C6 --> I6 --> R6 --> E6
  classDef clue fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef infer fill:#fff7e6,stroke:#b98500,color:#6b4e00;
  classDef risk fill:#fbe9e9,stroke:#b02a2a,color:#7a1f1f;
  classDef evidence fill:#e6f4ea,stroke:#1e7d34,color:#14532d;
  class C3,C5,C6 clue;
  class I3,I5,I6 infer;
  class R3,R5,R6 risk;
  class E3,E5,E6 evidence;

flowchart LR
  %% Deterministic clue tier for Cradlepoint Cryptographic Module
  %% confidence: high = structured record field; medium = structured but soft; low (dashed) = bare keyword hit, context unverified
  subgraph CMVP["CMVP-disclosed clues (deterministic)"]
    C3["[low] Self-test / status surface (referenced in text)<br/><i>Self-Test<br/>Status Output</i><br/>src: text:keyword"]
    C5["[low] Protocol / secure-channel references (may be KDF names, not a live channel)<br/><i>TLS<br/>HTTPS<br/>library named: openssl</i><br/>src: text:keyword"]
    C6["[low] Operating system / runtime referenced (boundary membership not asserted)<br/><i>operating system<br/>kernel<br/>application</i><br/>src: text:keyword"]
  end
  classDef clueHigh fill:#eef3f9,stroke:#2f6fb0,stroke-width:2px,color:#1f3a5f;
  classDef clueMedium fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef clueLow fill:#f7f7f7,stroke:#999,stroke-dasharray:4 4,color:#444;
  class C3,C5,C6 clueLow;

Security Policy, page by page

Ericsson Enterprise Wireless Solutions, Inc. Ericsson Cradlepoint Cryptographic Module Software Version: 1.0 FIPS Security Level: 1 Document Version: 0.6 Prepared for: Prepared by: Ericsson Enterprise Wireless Corsec Security, Inc. Solutions, Inc.

1100 W. Idaho Street, Suite 800 12600 Fair Lakes Circle, Suite 210

Boise, ID 83702-5389 Fairfax, VA 22033 United States United States of America Phone: +1 855 813 3385 Phone: +1 703 267 6050 www.cradlepoint.com www.corsec.com

Abstract This is a non-proprietary Cryptographic Module Security Policy for the Ericsson Cradlepoint Cryptographic Module (version: 1.0) from Ericsson Enterprise Wireless Solutions, Inc. (Ericsson). This Security Policy describes how the Ericsson Cradlepoint Cryptographic Module meets the security requirements of Federal Information Processing Standards (FIPS) Publication 140-3, which details the U.S. and Canadian government requirements for cryptographic modules. More information about the FIPS 140-3 standard and validation program is available on the National Institute of Standards and Technology (NIST) and the Canadian Centre for Cyber Security (CCCS) Cryptographic Module Validation Program (CMVP) website at http://csrc.nist.gov/groups/STM/cmvp. This document also describes how to run the module in its Approved mode of operation. This policy was prepared as part of the Level 1 FIPS 140-3 validation of the module. The Ericsson Cradlepoint Cryptographic Module is referred to in this document as Cradlepoint Cryptographic Module or the module. References This document deals only with operations and capabilities of the module in the technical terms of a FIPS 140-3 cryptographic module security policy. More information is available on the module from the following sources:

• The Ericsson website www.cradlepoint.com contains information on solutions from Ericsson’s Cradlepoint product line.
• The search page on the CMVP website (https://csrc.nist.gov/Projects/cryptographic-module-validationprogram/Validated-Modules/Search) can be used to locate and obtain vendor contact information for technical or sales-related questions about the module. Document Organization ISO/IEC 19790 Annex B uses the same section naming convention as ISO/IEC 19790 section 7 - Security requirements. For example, Annex B section B.2.1 is named “General” and B.2.2 is named “Cryptographic module specification,” which is the same as ISO/IEC 19790 section 7.1 and section 7.2, respectively. Therefore, the format of this Security Policy is presented in the same order as indicated in Annex B, starting with “General” and ending with “Mitigation of other attacks.” If sections are not applicable, they have been marked as such in this document. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

Ericsson is a global leader in cloud-delivered 4G and 5G wireless network edge solutions. Ericsson’s NetCloud™ Ericsson’s NetCloud for Branch makes it easy to accelerate connecting to the Internet and critical applications from anywhere. Designed for traditional medium branches or locations requiring flexible connectivity, reliable performance, and simplified management, this all-in-one, compact endpoint includes full-featured routing, security, and Wi-Fi without needing extra hardware or complicated configurations. The Ericsson Cradlepoint Cryptographic Module version 1.0 is a cryptographic library as part of the NetCloud operating system (OS) kernel that provides cryptographic services for Ericsson endpoints. The module offers symmetric encryption/decryption, digital signature generation/verification, hashing, cryptographic key generation, random number generation, message authentication, and SSP establishment functions to secure dataat-rest/data-in-flight and to support secure communications protocols (including TLS 3 1.2). The Ericsson Cradlepoint Cryptographic Module is validated at the FIPS 140-3 section levels shown in Table 1. The module has an overall security level of 1.

1 WAN – Wide Area Network

2 IoT – Internet of Things

3 TLS – Transport Layer Security

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

2. Cryptographic Module Specification The Ericsson Cradlepoint Cryptographic Module (version 1.0) is a software module with a multi-chip standalone embodiment. The module is designed to operate within a modifiable operational environment.

The module was tested and found to be compliant with FIPS 140-3 requirements on the environment listed in Table

2. Table 2 – Tested Operational Environments Each test environment includes a Qualcomm 802.11ax SoC 4 with four ARM Cortex-A processing cores. These processing cores support the ARMv8 Cryptography Extensions. The Cryptography Extensions include A64, A32, and T32 instructions for accelerating AES and SHA implementations. The module is designed to utilize the extended instruction sets when available. The vendor affirms the module’s continued validation compliance when operating on the environments listed in Table
3. Table 3 – Vendor-Affirmed Operational Environments The cryptographic module maintains validation compliance when operating on any general-purpose computer (GPC) provided that the GPC uses any single-user operating system/mode specified on the validation certificate,

4 SoC – System on a Chip

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

or another compatible single-user operating system. The CMVP makes no statement as to the correct operation of the module or the security strengths of the generated keys when ported to an operational environment not listed on the validation certificate. The sections below describe the module boundary, modes of operation, and algorithm implementations.

Validation certificates for each Approved security function are listed in Table 4 below. Table 4 – Approved Algorithm Validation Certificates

5 This table includes vendor-affirmed algorithms that are approved but CAVP testing is not yet available.

6 PUB – Publication

7 CBC – Cipher Block Chaining

8 CTR – Counter

9 ECB – Electronic Code Book

11 CVL – Component Validation List

12 TLS – Transport Layer Security

No part of the TLS protocol, other than the KDF, has been tested by the CAVP and CMVP.

14 No part of the TLS protocol, other than the KDF, has been tested by the CAVP and CMVP.

15 DRBG – Deterministic Random Bit Generator

17 ECDSA – Elliptic Curve Digital Signature Algorithm

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

18 KAS – Key Agreement Scheme

19 Key agreement method complies with FIPS 140-3 Implementation Guidance D.F, scenario 2(1).

20 Key agreement method complies with FIPS 140-3 Implementation Guidance D.F, scenario 2(1).

21 KAS-ECC-SSC – Key Agreement Scheme - Elliptic Curve Cryptography - Shared Secret Computation

22 KAS-FFC-SSC – Key Agreement Scheme - Finite Field Cryptography - Shared Secret Computation

KTS – Key Transport Scheme

24 Per FIPS 140-3 Implementation Guidance D.G, AES in any Approved mode with HMAC is an Approved key transport technique.

25 DES – Data Encryption Standard

26 Per FIPS 140-3 Implementation Guidance D.G, Triple DES in any Approved mode with HMAC is an Approved key transport technique.

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

The vendor affirms the following cryptographic security methods:

• Cryptographic key generation
• In compliance with section 4 of NIST SP 800-133rev2, the module uses its Approved DRBG to generate random values and seeds used for asymmetric key generation. The generated seed is an unmodified output from the DRBG. The module implements the non-Approved but allowed algorithms shown in Table 5 below.

28 RSA – Rivest Shamir Adleman

29 PSS – Probabilistic Signature Scheme

30 SHS – Secure Hash Standard

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

Table 5 – Non-Approved Algorithms Allowed in the Approved Mode of Operation The module does not implement any non-Approved algorithms allowed in the Approved mode of operation for which no security is claimed. The module does not implement any non-Approved algorithms not allowed in the Approved mode of operation.

As a software cryptographic module, the module has no physical components. Therefore, the physical perimeter of the cryptographic module is defined by each host device on which the module is installed. Figure 1 below illustrates a block diagram of a typical general-purpose computer (GPC) and the module’s physical perimeter. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

Hardware                               Network                           DVD RAM Management                              Interface HDD Clock                                                         SCSI/SATA Generator                                                      Controller LEDs/LCD CPU                                                                              Serial I/O Hub Audio Cache                 PCI/PCIe Slots                                                       USB BIOS Power               Graphics                                             PCI/PCIe Interface             Controller                                            Slots External Power Supply KEY: BIOS – Basic Input/Output System               PCIe – PCI express Plaintext Data             CPU – Central Processing Unit                  HDD – Hard Disk Drive Encrypted Data             SATA – Serial Advanced Technology Attachment   DVD – Digital Video Disc Control Input              SCSI – Small Computer System Interface         USB – Universal Serial Bus Status Output              PCI – Peripheral Component Interconnect        RAM – Random Access Memory Physical Perimeter         LED – Light Emitting Diode                     LCD – Liquid Crystal Display Figure 1 – GPC Block Diagram The module’s cryptographic boundary consists of all functionalities contained within the module’s compiled source code. This comprises: •    libcrypto.so (cryptographic primitives library file) •    libssl.so (TLS protocol library file) •    libcrypto.hmac (an HMAC 31 digest file for libcrypto integrity checking) •    libssl.hmac (an HMAC digest file for libssl integrity checking) The cryptographic boundary is the contiguous perimeter that surrounds all memory-mapped functionality provided by the module when loaded and stored in the host device’s memory. The module is entirely contained within the physical perimeter. Figure 2 shows the logical block diagram of the module executing in memory, its location with respect to the operating system and other supporting applications, and its interactions with surrounding software components, as well as the host platform’s physical perimeter and module’s cryptographic boundary .

31 HMAC – Keyed-Hash Message Authentication Code

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

libssl               libssl.hmac Calling Application KEY:                                                       libcrypto            libcrypto.hmac Cryptographic Boundary Physical Perimeter Operating System Data Input Data Output Control Input Control Output Status Output                          CPU           Memory            Storage            Ports System Calls Host Device Figure 2 – Module Block Diagram (with Cryptographic Boundary)

The module only implements one mode of operation, the Approved mode, in which the Approved and allowed cryptographic functions are available. The module transitions to the Approved mode of operation automatically after the module completes its pre-operational self-tests. No configuration is necessary for the module to operate and remain in the Approved mode. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

FIPS 140-3 defines the following logical interfaces for cryptographic modules: As a software library, the cryptographic module has no direct access to any of the host platform’s physical ports, as it communicates only to the calling application via its well-defined API. A mapping of the FIPS-defined interfaces and the module’s interfaces can be found in Table 6. Note that the module does not output control information, Table 6 – Ports and Interfaces Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

4. Roles, Services, and Authentication The sections below describe the module’s authorized roles, services, and operator authentication methods.

The module supports a Crypto Officer that authorized operators can assume. The CO role performs cryptographic initialization or management functions and general security services. The module also supports the following role(s):

• User
• The User role performs general security services, including cryptographic operations and other approved security functions. The module does not support multiple concurrent operators. The calling application that loaded the module is its only operator. Table 7 below lists the supported roles, along with the services (including input and output) available to each role. Table 7
• Roles, Service Commands, Input and Output

32 MAC – Message Authentication Code

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

The module does not support authentication methods; operators implicitly assume an authorized role based on the service selected.

Descriptions of the Approved services available to the authorized roles are provided in Table 8 below. The module is an integrated component of Ericsson’s NetCloud OS and offers crypto functions to applications installed on the Cradlepoint devices. While the module includes implementations of non-Approved security functions that can be called by other Ericsson modules, all such invocations will return failure codes to the caller. This effectively limits the service offerings to Approved services only. As allowed for this scenario per section C.H of FIPS 140-3 Implementation Guidance, the module provides indicators for the use of Approved services through a combination of an explicit indication (via a global FIPS mode indicator) and an implicit indication (via the API return value of the service). The keys and Sensitive Security Parameters (SSPs) listed in the table indicate the type of access required using the following notation:

• G = Generate: The module generates or derives the SSP.
• R = Read: The SSP is read from the module (e.g., the SSP is output).
• W = Write: The SSP is updated, imported, or written to the module.
• E = Execute: The module uses the SSP in performing a cryptographic operation.
• Z = Zeroize: The module zeroizes the SSP. Table 8
• Approved Services Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

*Per FIPS 140-3 Implementation Guidance 2.4.C, the Show Status, Zeroize, and Show Versioning Information services do not require a service indicator. The module does not support a non-Approved mode of operation and offers no non-Approved services. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

5. Software/Firmware Security All software components within the cryptographic boundary are verified using an Approved integrity technique implemented within the cryptographic module itself. The module implements an HMAC SHA2-256 for the integrity test of each library file; failure of the integrity check for either library file will cause the module to enter a critical error state. The module’s integrity check is performed automatically at module instantiation (i.e., when the module is loaded into memory for execution) without action from the module operator. The CO can initiate the pre-operational tests and conditional CASTs on demand by re-instantiating the module or issuing the FIPS_selftest() API command. The Ericsson Cradlepoint Cryptographic Module is not delivered to end-users as a standalone offering. Rather, it is a pre-built integrated component of Ericsson’s solutions. Ericsson does not provide end-users with any mechanisms to directly access the module, its source code, its APIs, or any information sent to/from the module. Thus, end-users have no ability to independently load the module onto target platforms. No configuration steps are required to be performed by end-users, and no end-user action is required to initialize the module for operation. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

6. Operational Environment The Ericsson Cradlepoint Cryptographic Module comprises a software cryptographic library that executes in a modifiable operational environment. The cryptographic module has control over its own SSPs. The process and memory management functionality of the host device’s OS prevents unauthorized access to plaintext private and secret keys, intermediate key generation values and other SSPs by external processes during module execution. The module only allows access to SSPs through its well-defined API. The operational environment provides the capability to separate individual application processes from each other by preventing uncontrolled access to CSPs and uncontrolled modifications of SSPs regardless of whether this data is in the process memory or stored on persistent storage within the operational environment. Processes that are spawned by the module are owned by the module and are not owned by external processes/operators. Please refer to section 2.1 of this document for a list/description of the applicable operational environments. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

7. Physical Security The cryptographic module is software module and does not include physical security mechanisms. Therefore, per ISO/IEC 19790:2021 section 7.7.1, requirements for physical security are not applicable. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

8. Non-Invasive Security This section is not applicable. There are currently no approved non-invasive mitigation techniques referenced in ISO/IEC 19790:2021 Annex F. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

The module supports the keys and other SSPs listed Table 9 and Table 10 below. Table 9 – Keys Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

Table 10 – Other SSPs Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

The module implements the following Approved DRBG:

• Counter-based DRBG This DRBG is used to generate random values at the request of the calling application. Outputs from this DRBG are also used as seeds in the generation of asymmetric key pairs. The module implements the following non-Approved DRBGs (which are only available in the non-Approved mode of operation):
• Hash-based DRBG (non-compliant)
• HMAC-based DRBG (non-compliant)
• ANSI X9.31 RNG (non-Approved) There is no mechanism within the module’s cryptographic boundary for the persistent storage of SSPs. The module stores DRBG state values for the lifetime of the DRBG instance. The module uses SSPs passed in on the stack by the calling application and does not store these SSPs beyond the lifetime of the API call. 33The module relies on entropy input received from the calling application, which is outside of the cryptographic boundary. Thus, there is no assurance of Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

As a software cryptographic module, there is no mechanism within the module boundary for the persistent storage of keys and CSPs. Maintenance, including protection and zeroization, of any keys and CSPs that exist outside the module’s cryptographic boundary are the responsibility of the end-user. For the zeroization of keys in volatile memory, module operators can unload the module from memory or reboot/power-cycle the host device.

The cryptographic module’s entropy scheme follows the scenario given in FIPS 140-3 Implementation Guidance 9.3.A, section 2(b). The module invokes a GET command to obtain entropy for random number generation (the module requests 256 bits of entropy from the calling application per request), and then passively receives entropy from the calling application while having no knowledge of the entropy source and exercising no control over the amount or the quality of the obtained entropy. The calling application and its entropy sources are located within the physical perimeter of the module’s operational environment but outside its cryptographic boundary. Thus, there is no assurance of the minimum strength of the generated SSPs. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

10. Self-Tests Both pre-operational and conditional self-tests are performed by the module. Pre-operational tests are performed between the time the cryptographic module is instantiated and before the module transitions to the operational state. Conditional self-tests are performed by the module during module operation when certain conditions exist. The following sections list the self-tests performed by the module, their expected error status, and the error resolutions.

The module performs the following pre-operational self-test(s):

• Software integrity test for libcrypto (using an HMAC SHA2-256 digest)
• Software integrity test for libssl (using an HMAC SHA2-256 digest) If both pre-operational self-tests complete successfully, then the module sets an internal flag to indicate that it is in the Approved mode.

The module performs the following conditional self-tests:

• Conditional cryptographic algorithm self-tests (CASTs)
• AES ECB encrypt KAT34 (128-bit length)
• AES ECB decrypt KAT (128-bit length)
• Triple-DES ECB encrypt KAT (3-Key)
• Triple-DES ECB decrypt KAT (3-Key)
• CTR_DRBG generate/instantiate/reseed KAT (256-bit AES, with derivation function)
• PBKDF2 KAT
• DSA sign KAT (2048-bit; SHA2-256)
• DSA verify KAT (2048-bit; SHA2-256)
• ECDSA sign KAT (P-224 and K-233 curves; SHA2-256)
• ECDSA verify KAT (P-224 and K-233 curves; SHA2-256)
• RSA verify KAT (2048-bit; SHA2-256; PKCS#1.5 scheme)
• RSA sign KAT (2048-bit; SHA2-256; PKCS#1.5 scheme)
• HMAC KATs (SHA-1, SHA2-224, SHA2-256, SHA2-384, SHA2-512)
• SHA-1 KAT
• SHA-2 KATs (SHA2-224, SHA2-256, SHA2-384, SHA2-512)
• FFC DH Shared Secret “Z” Computation KAT (2048-bit)
• ECC CDH Shared Secret “Z” Computation KAT (P-224 curve)
• TLS 1.2 KDF KAT

34 KAT – Known Answer Test

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

To ensure all CASTs are performed prior to the first operational use of the associated algorithm, all CASTs are performed during the module’s initial power-up sequence. The SHA and HMAC KATs are performed prior to the pre-operational software integrity test; all other CASTs are executed after the successful completion of the software integrity test.

• Conditional pair-wise consistency tests (PCTs)
• DSA sign/verify PCT
• ECDSA sign/verify PCT
• RSA sign/verify PCT
• DH key generation PCT
• ECDH key generation PCT

The module reaches the critical error state when any self-test fails. Upon test failure, the module immediately terminates the calling application’s API call with a returned error code and sets an internal flag, signaling the error condition. For any subsequent request made by the calling application for cryptographic services, the module will return a failure indicator, thereby disabling all access to its cryptographic functions, sensitive security parameters (SSPs), and data output services while the error condition persists. To recover, the module must be re-instantiated by the calling application. If the pre-operational self-tests complete successfully, then the module can resume normal operations. If the module continues to experience self-test failures after reinitializing, then the module will not be able to resume normal operations, and the CO should contact Ericsson Enterprise Wireless Solutions, Inc. for assistance. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

11. Life-Cycle Assurance The sections below describe how to ensure the module is operating in its validated configuration, including the following:

• Procedures for secure installation, initialization, startup, and operation of the module
• Maintenance requirements
• Administrator and non-Administrator guidance Operating the module without following the guidance herein (including the use of undocumented services) will result in non-compliant behavior and is outside the scope of this Security Policy.

The module is distributed as a package containing the binaries and HMAC digest files that the Crypto Officer is to install onto a target platform specified in section 6 or one where portability is maintained.

This module is designed to support vendor applications, and these applications are the sole consumers of the cryptographic services provided by the module. No end-user action is required to initialize the module for operation; the calling application performs any actions required to initialize the module. The pre-operational integrity test and cryptographic algorithm self-tests are performed automatically via a DEP when the module is loaded for execution, without any specific action from the calling application or the end-user. End-users have no means to short-circuit or bypass these actions. Failure of any of the initialization actions will result in a failure of the module to load for execution.

No startup steps are required to be performed by end-users.

There are no specific management activities required of the CO role to ensure that the module runs securely. However, if any irregular activity is noticed or the module is consistently reporting errors, then Ericsson Customer Support should be contacted. The following list provides additional guidance for the CO: • The fips_post_status() API can be used to determine the module’s operational status. A non-zero return value indicates that the module has passed all pre-operational self-tests and is currently in the Approved mode. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

• The CO can initiate the pre-operational self-tests and conditional CASTs on demand for periodic testing of the module by re-instantiating the module or issuing the FIPS_selftest() API command.
• The OpenSSL_version() API can be used to obtain the module’s versioning information. This information will include the module name and version, which can be correlated with the module’s validation record.

The following list provides additional policies for non-administrators:

• The module uses PBKDF2 option 1a from section 5.4 of NIST SP 800-132. The iteration count shall be selected as large as possible, as long as the time required to generate the resultant key is acceptable for module operators. The minimum iteration count shall be 1000. The length of the password/passphrase used in the PBKDF shall be of at least 20 characters, and shall consist of lower-case, upper-case, and numeric characters. The upper bound for the probability of guessing the value is estimated to be 1/6220 = 10-36, which is less than 2-112. Keys derived from passwords/passphrases, as shown in NIST SP 800-132, may only be used in storage applications.
• The cryptographic module’s services are designed to be provided to a calling application. Excluding the use of the NIST-defined elliptic curves as trusted third-party domain parameters, all other assurances from FIPS PUB 186-4 (including those required of the intended signatory and the signature verifier) are outside the scope of the module and are the responsibility of the calling application.
• The module performs assurances for its key agreement schemes as specified in the following sections of NIST SP 800-56Arev3:
• Section 5.5.2 (for assurances of domain parameter validity)
• Section 5.6.2.1 (for assurances required by the key pair owner) The module includes the capability to provide the required recipient assurance of ephemeral public key validity specified in section 5.6.2.2.2 of NIST SP 800-56Arev3. However, since public keys from other modules are not received directly by this module (those keys are received by the calling application), the module has no knowledge of when a public key is received. Invocation of the proper module services to validate another module’s public key is the responsibility of the calling application. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

12. Mitigation of Other Attacks This section is not applicable. The module does not claim to mitigate any attacks beyond the FIPS 140-3 Level 1 requirements for this validation. Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

Appendix A. Acronyms and Abbreviations Table 11 provides definitions for the acronyms and abbreviations used in this document. Table 11 – Acronyms and Abbreviations Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

Ericsson Cradlepoint Cryptographic Module ©2026 Ericsson Enterprise Wireless Solutions, Inc.

Prepared by: Corsec Security, Inc.

12600 Fair Lakes Circle, Suite 210

Fairfax, VA 22033 United States of America Phone: +1 703 267 6050 Email: info@corsec.com Web: www.corsec.com