HPE Juniper Networking
Junos® OS Evolved Juniper Express 5 MACsec
Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
Document Version: 1.0
Last update: 2026-05-04
Prepared by: Prepared for:
atsec information security corporation HPE Juniper Networking
4516 Seton Center Pkwy, Suite 250 1133 Innovation Way
Austin, TX 78759 Sunnyvale, CA 94089
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 2
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
www.atsec.com www.hpe.com/
Table of Contents
1.1 Overview ............................................................................................................................................................5
1.2 Security Levels....................................................................................................................................................5
1.3 Additional Information......................................................................................................................................5
2 Cryptographic Module Specification........................................................................................................................7
2.1 Description .........................................................................................................................................................7
2.2 Tested and Vendor Affirmed Module Version and Identification ..................................................................8
2.3 Excluded Components .......................................................................................................................................9
2.4 Modes of Operation............................................................................................................................................9
2.5 Algorithms..........................................................................................................................................................9
2.6 Security Function Implementations................................................................................................................10
2.7 Algorithm Specific Information ......................................................................................................................10
2.7.1 AES GCM IV .............................................................................................................................................10
2.8 RBG and Entropy .............................................................................................................................................11
2.9 Key Generation ................................................................................................................................................11
2.10 Key Establishment..........................................................................................................................................11
2.11 Industry Protocols..........................................................................................................................................11
3 Cryptographic Module Interfaces...........................................................................................................................12
3.1 Ports and Interfaces..........................................................................................................................................12
4 Roles, Services, and Authentication .......................................................................................................................13
4.1 Authentication Methods..................................................................................................................................13
4.2 Roles..................................................................................................................................................................13
4.3 Approved Services............................................................................................................................................13
4.4 Non-Approved Services ...................................................................................................................................15
4.5 External Software/Firmware Loaded...............................................................................................................15
5 Software/Firmware Security ...................................................................................................................................15
5.1 Integrity Techniques........................................................................................................................................15
5.2 Initiate on Demand ..........................................................................................................................................15
6 Operational Environment .......................................................................................................................................16
6.1 Operational Environment Type and Requirements .......................................................................................16
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 3
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
6.2 Configuration Settings and Restrictions..........................................................................................................16
7 Physical Security .....................................................................................................................................................17
8 Non-Invasive Security.............................................................................................................................................18
9 Sensitive Security Parameters Management ..........................................................................................................19
9.1 Storage Areas....................................................................................................................................................19
9.2 SSP Input-Output Methods .............................................................................................................................19
9.3 SSP Zeroization Methods.................................................................................................................................19
9.4 SSPs...................................................................................................................................................................20
10 Self-Tests................................................................................................................................................................21
10.1 Pre-Operational Self-Tests.............................................................................................................................21
10.2 Conditional Self-Tests....................................................................................................................................21
10.3 Periodic Self-Test Information ......................................................................................................................22
10.4 Error States .....................................................................................................................................................22
10.5 Operator Initiation of Self-Tests....................................................................................................................22
11 Life-Cycle Assurance.............................................................................................................................................23
11.1 Installation, Initialization, and Startup Procedures......................................................................................23
11.2 Administrator Guidance ................................................................................................................................23
11.2.1 Verification of the Module Installation .................................................................................................23
11.3 End of Life ......................................................................................................................................................23
12 Mitigation of Other Attacks..................................................................................................................................24
Appendix A. Glossary and Abbreviations .............................................................................................................25
Appendix B. References.........................................................................................................................................26
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 4
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
List of Tables
Table 1: Security Levels................................................................................................................................................5
Table 2: Tested Module Identification – Software, Firmware, Hybrid (Executable Code Sets) ...............................8
Table 3: Tested Module Identification – Hybrid Disjoint Hardware.........................................................................8
Table 4: Tested Operational Environments - Software, Firmware, Hybrid ..............................................................9
Table 5: Modes List and Description ...........................................................................................................................9
Table 6: Approved Algorithms...................................................................................................................................10
Table 7: Security Function Implementations............................................................................................................10
Table 8: Ports and Interfaces......................................................................................................................................12
Table 9: Roles..............................................................................................................................................................13
Table 10: Approved Services......................................................................................................................................14
Table 11: Storage Areas ..............................................................................................................................................19
Table 12: SSP Input-Output Methods .......................................................................................................................19
Table 13: SSP Zeroization Methods...........................................................................................................................20
Table 14: SSP Table 1 .................................................................................................................................................20
Table 15: SSP Table 2 .................................................................................................................................................20
Table 16: Pre-Operational Self-Tests.........................................................................................................................21
Table 17: Conditional Self-Tests ................................................................................................................................21
Table 18: Pre-Operational Periodic Information......................................................................................................22
Table 19: Conditional Periodic Information .............................................................................................................22
Table 20: Error States .................................................................................................................................................22
List of Figures
Figure 1: Block Diagram...............................................................................................................................................8
Figure 2: Juniper Express 5 processor ........................................................................................................................17
Figure 3: Packet Transport Router Model PTX10002-36QDD.................................................................................17
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 5
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
1 General
1.1 Overview
This document is the non-proprietary FIPS 140-3 Security Policy for the Junos®
OS Evolved Juniper Express 5
MACsec Cryptographic Module Version 1.0. It contains the security rules under which the module must
operate and describes how this module meets the requirements as specified in FIPS PUB 140-3 (Federal
Information Processing Standards Publication 140-3) for a Security Level 1 software-hybrid module.
This Security Policy has a one-to-one mapping to SP 800-140B starting with Section B.2.1 named “General” that
maps to Section 1 in this document and ending with Section B.2.12 named “Mitigation of other attacks” that
maps to Section 12 in this document.
This Non-Proprietary Security Policy may be reproduced and distributed, but only whole and intact and
including this notice. Other documentation is proprietary to their authors.
1.2 Security Levels
The following sections describe the cryptographic module and how it conforms to the FIPS 140-3 specification
in each of the required areas.
Section Title Security Level
1 General 1
2 Cryptographic module specification 1
3 Cryptographic module interfaces 1
4 Roles, services, and authentication 1
5 Software/Firmware security 1
6 Operational environment 1
7 Physical security 1
8 Non-invasive security N/A
9 Sensitive security parameter management 1
10 Self-tests 1
11 Life-cycle assurance 1
12 Mitigation of other attacks N/A
Overall Level 1
Table 1: Security Levels
1.3 Additional Information
In preparing the Security Policy document, the laboratory formatted the vendor-supplied documentation for
consolidation without altering the technical statements therein contained. The further refining of the Security
Policy document was conducted iteratively throughout the conformance testing, wherein the Security Policy
was submitted to the vendor, who would then edit, modify, and add technical contents. The vendor would also
supply additional documentation, which the laboratory formatted into the existing Security Policy, and
resubmitted to the vendor for their final editing.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 6
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 7
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
2 Cryptographic Module Specification
2.1 Description
Purpose and Use:
The Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0 (hereafter referred to as
“the module”) is a software-hybrid module.
The module is composed of the MACsec blocks in hardware (contained in the Juniper Networks®
Express 5
processor), which provides AES GCM and XPN algorithm implementations for encrypting and decrypting
MACsec traffic, and a device driver in software, which provides the functionality to comply with FIPS 140-3
requirements (i.e. integrity test, self-tests), as well as the API to configure the hardware component.
The module is also bound to the following cryptographic modules:
• Junos®
OS Evolved Kernel Cryptographic Module Version 2.1, which provides the integrity check
utility that is invoked by the module to check the integrity of the module’s software component.
• Junos®
OS Evolved OpenSSL Cryptographic Module Version 3.0, which provides the HMAC
implementation utilized by the kernel integrity check utility.
Sections of this Security Policy which refer to information from the bound modules, also known as the Existing
Validated Modules (or EVMs) are marked by [EVM] as per IG 1.A Resolution 5.
Module Type: Software-hybrid
Module Embodiment: Multi-Chip Standalone
Cryptographic Boundary:
The diagram below shows the components that comprise the cryptographic module (in yellow), its
cryptographic boundary (enclosed by dotted dark red boxes), and the interfaces with the operational
environment. Green lines indicate the flow of data between the cryptographic module and its external
interfaces.
Components in white are only included in the diagram for informational purposes. They are not included in the
cryptographic boundary and are therefore not part of the module’s validation.
Tested Operational Environment’s Physical Perimeter (TOEPP):
The tested operating environment’s physical perimeter is the general-purpose computer on which the module is
running.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 8
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Figure 1: Block Diagram
2.2 Tested and Vendor Affirmed Module Version and Identification
Tested Module Identification – Software, Firmware, Hybrid (Executable Code Sets):
Package or File Name Software/
Firmware
Version
Features Integrity
Test
/usr/lib64/libmacsecx1.so and /usr/lib64/.libmacsecx1.so.hmac on
Juniper Networks® Packet Transport Router Model PTX10002-
36QDD
1.0 N/A HMAC-
SHA2-256
Table 2: Tested Module Identification – Software, Firmware, Hybrid (Executable Code Sets)
Tested Module Identification – Hybrid Disjoint Hardware:
Model and/or Part Number Hardware Version Firmware Version Processors Features
Juniper Express 5 MACsec block JTAG ID 10622761 N/A Juniper Express 5 N/A
Table 3: Tested Module Identification – Hybrid Disjoint Hardware
Tested Operational Environments - Software, Firmware, Hybrid:
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 9
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Operating
System
Hardware Platform Processors PAA/PAI Hypervisor or
Host OS
Version(s)
Junos® OS
Evolved
24.4R2
Juniper Networks® Packet
Transport Router Model
PTX10002-36QDD
Intel® Xeon®
D-1749NT
Yes N/A 1.0
Table 4: Tested Operational Environments - Software, Firmware, Hybrid
2.3 Excluded Components
The module does not have any excluded components.
2.4 Modes of Operation
Modes List and Description:
Mode
Name
Description Types of
Services
Status Indicator
Approved
mode
Automatically
entered whenever
an approved service
is requested
Approved macsecx1_drv_tx_reg_port_config_rd() and
macsecx1_drv_rx_reg_ port_config_rd() API functions
return 1 in bit corresponding to the Juniper Express 5
MACsec block for authenticated encryption and decryption
services, respectively.
Table 5: Modes List and Description
Mode Change Instructions and Status:
The module supports only the approved mode of operation. When the module starts up successfully, after
passing all the pre-operational self-tests and conditional cryptographic algorithm self-tests (CASTs), the module
is operating in the approved mode of operation.
2.5 Algorithms
Approved Algorithms:
Algorithm CAVP Cert Properties Reference
AES-GCM A7007 Direction - Decrypt, Encrypt
IV Generation - External
Key Length - 128, 256
Tag Length - 128
IV Length - IV Length: 96
Payload Length - Payload Length: 128, 256, 120, 248
AAD Length - AAD Length: 128, 256, 120, 0
SP 800-38D
AES-XPN A7007 Direction - Decrypt, Encrypt
Key Length - 128, 256
Payload Length - Payload Length: 128, 256, 120, 248
AAD Length - AAD Length: 128, 256, 120, 0
SP 800-38D
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 10
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Algorithm CAVP Cert Properties Reference
Tag Length - 128
IV Generation - External
Salt Generation - External
HMAC-SHA2-256 A7243 MAC - MAC: 256
Key Length - Key Length: 112-524288 Increment 8
FIPS 198-1
Table 6: Approved Algorithms
The HMAC-SHA2-256 implementation is provided by the bound Junos®
OS Evolved OpenSSL Cryptographic
Module.
2.6 Security Function Implementations
Name Type Description Properties Algorithms
Authenticated
symmetric encryption
BC-
Auth
Authenticated symmetric encryption
(implemented in Juniper Express 5
MACsec blocks)
AES-GCM:
(A7007)
AES-XPN:
(A7007)
Authenticated
symmetric decryption
BC-
Auth
Authenticated symmetric decryption
(implemented in Juniper Express 5
MACsec blocks)
AES-GCM:
(A7007)
AES-XPN:
(A7007)
Integrity test MAC [EVM] Integrity test utilizing
cryptographic functionality from bound
OpenSSL module
HMAC-SHA2-
256: (A7243)
Table 7: Security Function Implementations
2.7 Algorithm Specific Information
2.7.1 AES GCM IV
The AES GCM IV generation is compliant with IEEE 802.1AE and shall only be used for the MACsec protocol
to be compliant with FIPS 140-3 IG C.H, provision 1.c (“MACsec protocol IV generation”).
In line with the MACsec protocol, the IV has a length of 96 bits and it is constructed externally by
concatenating:
• For AES-128-GCM and AES-256-GCM: the 64-bit Secure Channel Identifier (SCI) and the 32-bit
packet number (PN);
• For AES-128-XPN and AES-256-XPN: the 32-bit Short Secure Channel Identifier (SSCI), the 64-bit
extended packet number (XPN) and a 96-bit salt.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 11
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Each appliance plays the role of either the Peer or the Authenticator in the context of the MACsec protocol. No
Authentication Server is involved, and thus there are no configuration instructions for the link between the
Authenticator and the Authentication Server.
When supporting the MACsec protocol in the approved mode, the module should only be used together with
the same appliance or other appliances that are also FIPS 140-3 validated and operating in the approved mode.
In addition, the link between the Peer and the Authenticator should be secured to prevent the possibility for an
attacker to introduce foreign equipment into the local area network.
In case the module's power is lost and then restored, the key used for AES-GCM or AES-XPN encryption or
decryption shall be redistributed.
2.8 RBG and Entropy
This module does not support random bit generation and does not contain an entropy source.
2.9 Key Generation
The module does not provide key generation mechanisms.
2.10 Key Establishment
The module does not provide key establishment mechanisms.
2.11 Industry Protocols
The module is part of the Juniper Packet Transport Router Model PTX10002-36QDD, which supports MACsec
using static connectivity association key (CAK) security mode. In this mode, a pre-shared key (PSK) is
exchanged between the devices on each end of the point-to-point Ethernet link.
No parts of the MACsec protocol other than the AES-GCM implementation are tested by CAVP or CMVP.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 12
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
3 Cryptographic Module Interfaces
3.1 Ports and Interfaces
Physical Port Logical
Interface(s)
Data That Passes
Network ports Data Input Decrypted/encrypted data received from network ports
Network ports Data Output Encrypted/decrypted data sent to network ports
N/A Control Input API function calls
N/A Data Input API input parameters (including keys) via API, status information
from Juniper Express 5 MACsec blocks via /dev/pfe[0-3]
N/A Control
Output
Juniper Express 5 MACsec block configuration parameters
N/A Data Output Keys for use in Juniper Express 5 MACsec blocks
Juniper Express 5
MACsec block
registers
Control Input Juniper Express 5 MACsec block configuration parameters
Juniper Express 5
MACsec block
registers
Data Input Keys for use in Juniper Express 5 MACsec blocks
Juniper Express 5
MACsec block
registers
Status Output Status information regarding the Juniper Express 5 MACsec
blocks
N/A Status Output API return codes, API output parameters for status output.
Power supply port for
JE5 chip
Power N/A
Table 8: Ports and Interfaces
Network ports and the power supply port correspond to the Juniper Express 5 processor where the MACsec
blocks are contained.
All output via the data output and control output interfaces are inhibited when the module is performing self-
tests or zeroization, or when the module is in the error state.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 13
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
4 Roles, Services, and Authentication
4.1 Authentication Methods
The module does not support authentication.
4.2 Roles
The Crypto Officer role is implicitly and always assumed by the operator of the module. The module does not
support concurrent operators.
Name Type Operator Type Authentication Methods
Crypto Officer Role Crypto Officer None
Table 9: Roles
4.3 Approved Services
The table below shows the services available in the Approved mode. For each service, the table lists the
associated cryptographic algorithm(s), the role to perform the service, the cryptographic keys or SSPs involved,
and their access type(s). The following convention is used to specify access rights to an SSP:
• 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.
Name Descripti
on
Indicator Inputs Outputs Security
Functions
SSP
Acces
s
Authenticat
ed
symmetric
encryption
Perform
AES
encryptio
n in
Juniper
Express 5
MACsec
blocks
macsecx1_drv_tx_reg_port_conf
ig_rd() returns 1 in bit
corresponding to the Juniper
Express 5 MACsec block.
Plaintext
, IV, AES
key
Ciphertext,
MAC tag
Authenticat
ed
symmetric
encryption
Crypt
o
Offic
er
- AES
key:
W,E
Authenticat
ed
symmetric
decryption
Perform
AES
decryptio
n in
Juniper
Express 5
MACsec
blocks
macsecx1_drv_rx_reg_
port_config_rd() returns 1 in bit
corresponding to the Juniper
Express 5 MACsec block.
Cipherte
xt, MAC
tag, IV,
AES key
Plaintext
or Fail
Authenticat
ed
symmetric
decryption
Crypt
o
Offic
er
- AES
key:
W,E
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 14
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Name Descripti
on
Indicator Inputs Outputs Security
Functions
SSP
Acces
s
Show status Return
the
module
status
from the
MACsec
device
driver
None None Module
status
None Crypt
o
Offic
er
Self-test Perform
the
CASTs
(in
Juniper
Express 5
MACsec
blocks)
and the
integrity
test (on
the
MACsec
device
driver)
None None Pass/fail Authenticat
ed
symmetric
encryption
Authenticat
ed
symmetric
decryption
Integrity
test
Crypt
o
Offic
er
Zeroization Zeroize
all SSPs
in Juniper
Express 5
MACsec
blocks
None Port
group ID
Pass/fail None Crypt
o
Offic
er
- AES
key:
Z
Show
module
name and
version
Return
module
name and
version
informati
on from
the
MACsec
device
driver
None None Module
name/versi
on
None Crypt
o
Offic
er
Table 10: Approved Services
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 15
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
4.4 Non-Approved Services
The module does not implement any non-approved services.
4.5 External Software/Firmware Loaded
The module does not support the loading of external software/firmware.
5 Software/Firmware Security
5.1 Integrity Techniques
[EVM] The integrity of the module is ensured with the HMAC-SHA-256 value stored in the corresponding
/usr/lib64/.libmacsecx1.so.hmac file that is computed at build time for the shared library. During Pre-
Operational Self-Tests, the module invokes the fips_chk_hmac utility provided by the bound Kernel module
(and whose cryptographic functionality is provided by the bound OpenSSL module) to calculate the HMAC
value of the shared library, and then compares it with the prestored value. If the two HMAC values do not
match, the test fails and the module enters the error state.
The integrity of the fips_chk_hmac utility itself is performed before the integrity tests of the module, and
ensured with the HMAC-SHA2-256 value stored in the corresponding .hmac file that is computed at build time
of the utility. The fips_chk_hmac utility calculates the HMAC value, and then compares it with the prestored
value. If the two HMAC values do not match, the test fails and the module enters the error state.
The fips_chk_hmac utility uses a key hardcoded into the bound Kernel module to calculate HMAC values
during the integrity test.
5.2 Initiate on Demand
Integrity tests are performed as part of the Pre-Operational Self-Tests, and can be invoked by reloading the
module which will cause the module to run the power-up tests again.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 16
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
6 Operational Environment
6.1 Operational Environment Type and Requirements
Type of Operational Environment: Modifiable
6.2 Configuration Settings and Restrictions
The module shall be installed as stated in Section 11.1. If properly installed, the operating system provides
process isolation and memory protection mechanisms that ensure appropriate separation for memory access
among the processes on the system. Each process has control over its own data and uncontrolled access to the
data of other processes is prevented.
Instrumentation tools like the ptrace system call, gdb and strace utilities, userspace live patching, as well as
other tracing mechanisms offered by the Linux environment such as ftrace or systemtap, shall not be used in
the operational environment. The use of any of these tools implies that the cryptographic module is running in
a non-tested operational environment.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 17
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
7 Physical Security
The Juniper Express 5 processor (an ASIC silicon) is the hardware containing the MACsec blocks that constitute
the hardware component of the module. The embodiment of the chip is a single chip consisting of production-
grade components. The coating is a standard sealing coat applied over the single chip. The module provides no
additional physical security techniques.
Figure 2: Juniper Express 5 processor
The module inherits the physical characteristics of the host running it. Figure 3 illustrates the Juniper
Networks® Packet Transport Router Model PTX10002-36QDD that represents the testing platform and
includes the hardware component of the cryptographic module. The router includes three Juniper Express 5
ASIC chips to provide forwarding traffic and supporting MACsec for its 36 multi-rate ports.
Figure 3: Packet Transport Router Model PTX10002-36QDD
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 18
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
8 Non-Invasive Security
This module does not implement any non-invasive security mechanism and therefore this section is not
applicable.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 19
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
9 Sensitive Security Parameters Management
9.1 Storage Areas
Storage Area
Name
Description Persistence
Type
RAM Temporary storage for SSPs used by the module as part of service
execution.
Dynamic
Table 11: Storage Areas
The module does not perform persistent storage of SSPs. The SSPs are temporarily stored in the RAM in
plaintext form; the module does not support storage of any cryptographically protected SSP.
SSPs are provided to the module by the calling process and are destroyed when released by the appropriate
zeroization function calls.
9.2 SSP Input-Output Methods
Name From To Format
Type
Distribution
Type
Entry
Type
SFI or
Algorithm
API input
parameters
Operator calling
application
(TOEPP)
Cryptographic
module
Plaintext Manual Electronic
Table 12: SSP Input-Output Methods
The module only supports SSP entry from the calling application running on the same operational
environment. This corresponds to manual distribution, electronic entry/output (“CM Software to/from App via
TOEPP Path”) per FIPS 140-3 IG 9.5.A Table 1. There is no entry of cryptographically protected SSPs.
SSPs are transmitted between the disjoint module components via a path within the operational environment.
Communication between the module components is considered controlled communications.
The module does not output any SSPs.
9.3 SSP Zeroization Methods
Zeroization
Method
Description Rationale Operator Initiation
Wipe and
Free memory
block
allocated
Zeroizes the SSPs
contained within
the cipher handle.
Memory occupied by SSPs is
overwritten with zeroes and
then it is released, which
renders the SSP values
irretrievable. The completion
of the zeroization routine
By calling the cipher related
zeroization API:
macsecx1_drv_port_tx_sa_delete() for
AES keys
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 20
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Zeroization
Method
Description Rationale Operator Initiation
indicates that the zeroization
procedure succeeded.
Automatic Automatically
zeroized by the
module when no
longer needed
Memory occupied by SSPs is
overwritten with zeroes,
which renders the SSP values
irretrievable.
N/A
Module Reset De-allocates the
volatile memory
used to store SSPs
Volatile memory used by the
module is overwritten within
nanoseconds when power is
removed.
By unloading and reloading the
module
Table 13: SSP Zeroization Methods
The RAM occupied by SSPs is allocated by regular memory allocation operating system calls. The module calls
internally the appropriate zeroization functions (i.e. memset) to zeroize any intermediate values used to
configure the MACsec blocks and before returning to the calling application. The zeroization functions
overwrite the memory occupied by SSPs with “zeros” and deallocate the memory with the regular memory
deallocation operating system call.
The module can also zeroize registers when a MACsec block is no longer used via the
macsecx1_drv_port_tx_sa_delete() function. The completion of this function will indicate that the zeroization
of the SSPs included in the MACsec block finished successfully. It is the responsibility of the application acting
as the Crypto Officer to call this function when the MACsec block is no longer needed.
9.4 SSPs
Name Description Size - Strength Type -
Category
Generated
By
Established
By
Used By
AES
key
AES key 128, 256 bits -
128, 256 bits
Symmetric
key - CSP
Authenticated
symmetric
encryption
Authenticated
symmetric decryption
Table 14: SSP Table 1
Name Input - Output Storage Storage
Duration
Zeroization Related
SSPs
AES
key
API input
parameters
RAM:Plaintext Wipe and Free memory block
allocated
Module Reset
Table 15: SSP Table 2
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 21
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
10 Self-Tests
The module performs pre-operational and conditional cryptographic algorithm self-tests automatically when
the module is loaded into memory. These self-tests ensure that the firmware component of the module is not
corrupted and that the cryptographic algorithms work as expected. While the module is executing the pre-
operational and the conditional cryptographic algorithm self-tests, services are not available, and all input and
output are inhibited. The module is not available for use by the calling application until the self-tests are
completed successfully. If any of the self-tests fail, an error message is returned and the module transitions to
error state.
10.1 Pre-Operational Self-Tests
Algorithm or
Test
Test Properties Test Method Test Type Indicator Details
HMAC-SHA2-
256
HMAC-SHA2-
256
MAC tag
verification
SW/FW
Integrity
Module becomes
operational
[EVM]
Table 16: Pre-Operational Self-Tests
The module performs a pre-operational software integrity test automatically when the module is powered on
before the module transitions into the operational state. The details of the integrity test are specified in Section
5.1.
10.2 Conditional Self-Tests
The table below lists the cryptographic algorithm self-tests (CASTs). The CASTs include the KATs for the
integrity mechanism that is run prior to performing the integrity test.
Each KAT includes comparison of the calculated output with the expected known answer, hard coded as part of
the test vectors used in the test. Data output through the data output interface is inhibited during the self-tests.
If the values do not match, the KAT fails and the module transitions to the error state.
Algorithm or
Test
Test
Properties
Test
Method
Test
Type
Indicator Details Conditions
AES-GCM
(A7007) -
Encryption
128, 256-bit
keys,
encrypt
KAT CAST Module
becomes
operational
Authenticated
symmetric
encryption
Test runs at
power-on before
integrity test
AES-GCM
(A7007) -
Decryption
128-256-bit
keys,
decrypt
KAT CAST Module
becomes
operational
Authenticated
symmetric
decryption
Test runs at
power-on before
integrity test
HMAC-SHA2-
256 (A7243)
SHA2-256 KAT CAST Module
becomes
operational
[EVM] MAC
computation
Test runs at
power-on before
integrity test
Table 17: Conditional Self-Tests
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 22
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
10.3 Periodic Self-Test Information
Algorithm or Test Test Method Test Type Period Periodic Method
HMAC-SHA2-256 MAC tag verification SW/FW Integrity On Demand Manually
Table 18: Pre-Operational Periodic Information
Algorithm or Test Test Method Test Type Period Periodic Method
AES-GCM (A7007) - Encryption KAT CAST On Demand Manually
AES-GCM (A7007) - Decryption KAT CAST On Demand Manually
HMAC-SHA2-256 (A7243) KAT CAST On Demand Manually
Table 19: Conditional Periodic Information
On-demand self-tests can be invoked by powering off and reloading the module which cause the module to run
the pre-operational and conditional cryptographic algorithm self-tests.
10.4 Error States
When the module fails any pre-operational or conditional self-test, the module will enter the Error state. Any
further cryptographic operation is inhibited, and data and control output are inhibited. The calling application
can obtain the module state by calling the macsecx1_drv_fips_kat_ok() and the
macsecx1_drv_integrity_chk_ok() API functions. The function will return a boolean code indicating whether
the CAST or the integrity tests passed or failed.
The Crypto Officer can recover from the Error state by restarting the hardware platform on which the module
is running.
Name Description Conditions Recovery
Method
Indicator
Error General-
purpose error
state
Failure of
CAST
Failure of
integrity
tests
Power
cycle
macsecx1_drv_fips_kat_ok() returns false (CAST
failure), macsecx1_drv_integrity_chk_ok() returns
false (integrity test failure)
Table 20: Error States
10.5 Operator Initiation of Self-Tests
The operator can initiate the pre-operational self-tests and the cryptographic algorithm self-tests by powering
off and subsequently reloading the module.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 23
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
11 Life-Cycle Assurance
11.1 Installation, Initialization, and Startup Procedures
The binary of the module is contained in the base Junos Evolved installation image. The Crypto Officer shall
follow this Security Policy to configure the operational environment and install the module to be operated as a
FIPS 140-3 validated module.
11.2 Administrator Guidance
11.2.1 Verification of the Module Installation
The module is already pre-installed on the image file (junos-evo-install-ptx-fixed-x86-64-24.4R2-S1.3-EVO).
The crypto officer is responsible for verifying the correct installation of the module by executing the following
command:
show macsec_drv version
Verify that the command returns the following name and version of the software and hardware components of
the module, which matches the versions shown in Table 2 and Table 3:
Junos OS Evolved MACsec Cryptographic Driver, version 1.0 : ASIC JTAG ID 10622761
11.3 End of Life
As the module does not persistently store SSPs, secure sanitization of the module consists of unloading the
module. This will zeroize all SSPs in volatile memory.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 24
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
12 Mitigation of Other Attacks
The module does not implement any additional mitigation mechanism.
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 25
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Appendix A. Glossary and Abbreviations
AES Advanced Encryption Standard
AES-NI Advanced Encryption Standard New Instructions
API Application Program Interface
CAVP Cryptographic Algorithm Validation Program
CBC Cipher Block Chaining
CMVP Cryptographic Module Validation Program
CSP Critical Security Parameter
ECB Electronic Code Book
EE Electronic Entry
FIPS Federal Information Processing Standards Publication
GCM Galois Counter Mode
HMAC Hash Message Authentication Code
IG Implementation Guidance
KAT Known Answer Test
MD Manual Distribution
NIST National Institute of Science and Technology
PAA Processor Algorithm Acceleration
PCT Pair-wise Consistency Test
SHA Secure Hash Algorithm
SCI Secure Channel Identifier
SSCI Short Secure Channel Identifier
Junos®
OS Evolved Juniper Express 5 MACsec Cryptographic Module Version 1.0
FIPS 140-3 Non-Proprietary Security Policy
HPE Juniper Networking o +1 408 745 2000 26
1133 Innovation Way f +1 408 745 2100
Sunnyvale, CA 94089
www.hpe.com
Appendix B. References
FIPS 140-3 FIPS PUB 140-3 - Security Requirements For Cryptographic Modules
March 2019
https://doi.org/10.6028/NIST.FIPS.140-3
FIPS 140-3 IG Implementation Guidance for FIPS 140-3 and the Cryptographic Module Validation
Program
April 2026
https://csrc.nist.gov/Projects/cryptographic-module-validation-program/fips-140-3-ig-
announcements
SP 800-38D Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM)
and GMAC
November 2007
https://doi.org/10.6028/NIST.SP.800-38D
IEEE 802.1AE MAC Security (MACsec)
December 2018
https://1.ieee802.org/security/802-1ae/