The Nokia 7750 SR & 7250 IXR, SROS 24.10.R3, MACsec platforms (herein referred to as the TOE) is a network device with the high-performance, scale and flexibility supporting service providers, web scale and enterprise networks. The TOE utilizes Nokia’s SR operating system version 24.10.R3. The following table lists all the TOE’s models that have been evaluated.
\r\nTable 2 – TOE’s hardware platforms
\r\n| \r\n Platform (part number) \r\n | \r\n\r\n CPU \r\n | \r\n\r\n Speed \r\n | \r\n\r\n Core \r\n | \r\n
| \r\n 7750 SR-1 CPM in: \r\n-7750 SR-1 (FP4) \r\n | \r\n\r\n Marvell OCTEON III CN7360 (MIPS64) \r\n | \r\n\r\n 1.8GHz \r\n | \r\n\r\n 16 \r\n | \r\n
| \r\n 7750 SR-1 CPM in: | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7750 SR-1x CPM in: | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7750 SR-1se CPM \r\n | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7250 IXR-R6d/dl CPIOM \r\n | \r\n\r\n AMD EPYC3255 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7750 SR-2se CPM-2se \r\n | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7250 IXR-e CPM (Small) \r\n | \r\n\r\n Intel Atom C3708 (Goldmont) \r\n | \r\n\r\n 1.7GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7250 IXR-R4 CPM \r\n | \r\n\r\n Marvell OCTEON III CN7340 (MIPS64) \r\n | \r\n\r\n 1.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7250 IXR-R6 CPIOM \r\n | \r\n\r\n Marvell OCTEON III CN7360 (MIPS64) \r\n | \r\n\r\n 1.5GHz \r\n | \r\n\r\n 16 \r\n | \r\n
| \r\n 7750 SR-2s CPM \r\n | \r\n\r\n Marvell OCTEON III CN7360 (MIPS64) \r\n | \r\n\r\n 1.8GHz \r\n | \r\n\r\n 16 \r\n | \r\n
| \r\n 7750 SR-14s/7s CPM-s v2 (SR-s CPM-2S) \r\n | \r\n\r\n Marvell OCTEON III CN7890 (MIPS64) \r\n | \r\n\r\n 1.8GHz \r\n | \r\n\r\n 48 \r\n | \r\n
| \r\n 7750 SR-7/SR-12/SR-12e SR CPM5 \r\n | \r\n\r\n Marvell OCTEON II CN6645 (MIPS64) \r\n | \r\n\r\n 1.5GHz \r\n | \r\n\r\n 10 \r\n | \r\n
The TOE Description section provides an overview of the TOE architecture, including physical boundaries, security functions, and relevant TOE documentation and references.
\r\n\r\nThe TOE is a network device that is composed of hardware and software and offers a scalable solution to the end users. It satisfies all the criterion to meet the collaborative Protection Profile for Network Devices, Version 3.0e [CPP_ND_V3.0E], Functional Package for Secure Shell (PKG_SSH_V1.0) and PP-Module for MACsec Ethernet Encryption, Version 1.0 [MOD_MACsec_V1.0].
\r\n\r\nThe TOE portfolio delivers high-performance, scaling and flexibility to support a full array of IP and MPLS services and functions for service providers, web scale and enterprise networks. The Nokia 7750 SR & 7250 IXR portfolios include a wide range of physical platforms that share a mutual architecture and feature set. This allows Nokia customers to select the platform that best addresses their unique business goals and fulfills their scale, density, space, power, and value-added service requirements. The Nokia 7750 SR & 7250 IXR portfolios are chassis-based routers.
\r\nThe Nokia 7750 Service Router (SR) portfolio consists of hardware platforms intended for use in IP edge and core networking environments. The portfolio includes the 7750 SR-s and 7750 SR series appliance families. The following Table 3 lists the specifically evaluated Nokia platforms:
\r\nTable 3 – Nokia 7750 SR Platforms
\r\n| \r\n Platforms (part number) \r\n | \r\n\r\n CPU \r\n | \r\n\r\n Speed \r\n | \r\n\r\n Core \r\n | \r\n
| \r\n 7750 SR-1 CPM in: \r\n-7750 SR-1 (FP4) \r\n | \r\n\r\n Marvell OCTEON III CN7360 (MIPS64) \r\n | \r\n\r\n 1.8GHz \r\n | \r\n\r\n 16 \r\n | \r\n
| \r\n 7750 SR-1 CPM in: | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7750 SR-1x in: | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7750 SR-1se CPM \r\n | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7750 SR-2se CPM-2se \r\n | \r\n\r\n AMD EPYC3251 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7750 SR-2s CPM \r\n | \r\n\r\n Marvell OCTEON III CN7360 (MIPS64) \r\n | \r\n\r\n 1.8GHz \r\n | \r\n\r\n 16 \r\n | \r\n
| \r\n 7750 SR-14s/7s CPM-s v2 \r\n | \r\n\r\n Marvell OCTEON III CN7890 (MIPS64) \r\n | \r\n\r\n 1.8GHz \r\n | \r\n\r\n 48 \r\n | \r\n
| \r\n 7750 SR-7/SR-12/SR-12e SR CPM5 \r\n | \r\n\r\n Marvell OCTEON II CN6645 (MIPS64) \r\n | \r\n\r\n 1.5GHz \r\n | \r\n\r\n 10 \r\n | \r\n
The Nokia 7250 IXR portfolio is purpose-built for access and aggregation in mobile anyhaul, fixed-mobile convergence, and mission-critical enterprise applications. They offer compact, temperature-hardened platforms with advanced timing, security and quality of service features. The Nokia 7250 IXR portfolio includes the following appliance families: The 7250 IXR-R, IXR-e, IXR-X and 7250 IXR-s platforms. The following Table 4 lists the specifically evaluated Nokia 7250 IXR platforms:
\r\nTable 4 – Nokia 7250 IXR Platforms
\r\n| \r\n Platforms (part number) \r\n | \r\n\r\n CPU \r\n | \r\n\r\n Speed \r\n | \r\n\r\n Core \r\n | \r\n
| \r\n 7250 IXR-R6d/dl CPIOM \r\n | \r\n\r\n AMD EPYC3255 (ZEN) \r\n | \r\n\r\n 2.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7250 IXR-e (Small) CPM \r\n | \r\n\r\n Intel Atom C3708 (Goldmont) \r\n | \r\n\r\n 1.7GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7250 IXR-R4 CPM \r\n | \r\n\r\n Marvell OCTEON III CN7340 (MIPS64) \r\n | \r\n\r\n 1.5GHz \r\n | \r\n\r\n 8 \r\n | \r\n
| \r\n 7250 IXR-R6 CPIOM \r\n | \r\n\r\n Marvell OCTEON III CN7360 (MIPS64) \r\n | \r\n\r\n 1.5GHz \r\n | \r\n\r\n 16 \r\n | \r\n
The TOE supports a full array of network functions and services. Every Nokia 7750 series routing appliance is a whole routing system that provides a variety of high-speed interfaces (only Ethernet is within scope of this evaluation) for various scales of networks and various network applications. The TOE utilizes a common Nokia SR operating system, features, and technology for compatibility across all platforms.
\r\nNokia SR OS is mainly responsible for all the functionalities and services provided by the routers. The routers can be accessed either via a local console or via a network connection that is protected using the SSH protocol. Each time a user accesses the routers, either via local console terminal connection or from the network remotely using SSH, the user must ensure to successfully authenticate itself with the correct credentials.
\r\nThe TOE also supports MACsec functionality between compatible Nokia MACsec peer devices using the Media Dependent Adapter (MDA). On the evaluated configuration, the TOE permits only EAPOL (PAE EtherType 88-8E), MACsec frames (EtherType 88-E5), and MAC control frames (EtherType is 88-08) and discards others.
\r\nThe TOE’s provides AES-GCM MACsec encryption. The MACsec feature is powered by one or more of the network processor chips listed in Table 5:
\r\nTable 5 – TOE’s MACsec PHYs
\r\n| \r\n Network Chip \r\n | \r\n\r\n Vendor \r\n | \r\n
| \r\n BCM82399 \r\n | \r\n\r\n Broadcom \r\n | \r\n
| \r\n BCM81392 \r\n | \r\n|
| \r\n BCM81394 \r\n | \r\n|
| \r\n BCM81343 \r\n | \r\n|
| \r\n VSC8258 \r\n | \r\n\r\n Microsemi \r\n | \r\n
| \r\n VSC8490 \r\n | \r\n|
| \r\n VSC8584 \r\n | \r\n|
| \r\n E5 \r\n | \r\n\r\n Nokia \r\n | \r\n
The MDAs are pluggable adapter cards. They provide physical interface connectivity to the devices. MDAs can be different in terms of connectivity and density configuration settings. Additionally, the MDA modules vary by chassis. Regardless, they provide the same functionality and security for the related chassis. MDAs support ethernet and multiservice interfaces. For this evaluation, the following Table 6. lists the TOE platforms and their compatible MDA card, in addition to the MACsec PHY:
\r\nTable 6 – MDA and MACsec cards used in the TOE's MACsec capable appliances
\r\n| \r\n TOE platforms \r\n | \r\n\r\n MACsec card \r\n | \r\n\r\n MACsec embedded (network processor) | \r\n
| \r\n 7750 SR-1se CPM \r\n | \r\n\r\n ms36-800g-qsfpdd \r\n | \r\n\r\n Nokia E5 \r\n | \r\n
| \r\n 7750 SR-1-48D CPM \r\n | \r\n\r\n m48-400g-qsfpdd-1 \r\n | \r\n|
| \r\n 7750 SR-1x-92S CPM \r\n | \r\n\r\n m80-200g-sfpdd+12-800g-qsfpdd-1x \r\n | \r\n|
| \r\n 7750 SR-1-92S CPM \r\n | \r\n\r\n m80-200g-sfpdd+12-400g-qsfpdd-1 \r\n | \r\n|
| \r\n 7750 SR-1-24D CPM \r\n | \r\n\r\n m24-800g-qsfpdd-1 \r\n | \r\n|
| \r\n 7750 SR-1x-48D CPM \r\n | \r\n\r\n m48-800g-qsfpdd-1x \r\n | \r\n|
| \r\n 7750 SR-1-46S CPM \r\n | \r\n\r\n m40-200g-sfpdd+6-800g-qsfpdd-1 \r\n | \r\n|
| \r\n 7750 SR-2se CPM \r\n | \r\n\r\n x2-s36-800g-qsfpdd-18.0t \r\n | \r\n\r\n Nokia E5 \r\n | \r\n
| \r\n x2-s18-800g-qsfpdd \r\n | \r\n||
| \r\n x2-s36-800g-qsfpdd-12.0t \r\n | \r\n||
| \r\n mse24-200g-sfpdd \r\n | \r\n||
| \r\n mse6-800g-cfp2-dco \r\n | \r\n||
| \r\n mse14-800g+4-400g \r\n | \r\n||
| \r\n m36-800g-qsfpdd \r\n | \r\n||
| \r\n mse6-800g-qsfpdd \r\n | \r\n||
| \r\n m36-400g-qsfp112 \r\n | \r\n||
| \r\n 7250 IXR-R6d/R6dl CPIOM \r\n | \r\n\r\n m20-10g-sfp+ \r\n | \r\n\r\n VSC8258 \r\n | \r\n
| \r\n m18-25g-sfp28 \r\n | \r\n\r\n BCM81392 and BCM81394 \r\n | \r\n|
| \r\n m1-400g-qsfpdd+1-100g-qsfp28 \r\n | \r\n\r\n BCM81343 \r\n | \r\n|
| \r\n m46-10g-sfp+ \r\n | \r\n\r\n VSC8258 \r\n | \r\n|
| \r\n m2-cfp2 \r\n | \r\n\r\n BCM81343 \r\n | \r\n|
| \r\n m32-1g-csfp \r\n | \r\n\r\n VSC8584 \r\n | \r\n|
| \r\n m80-1g-csfp \r\n | \r\n\r\n VSC8584 \r\n | \r\n|
| \r\n m2-100g-qsfp28+16-10g-sfp+ \r\n | \r\n\r\n BCM81392 and VSC8258 \r\n | \r\n|
| \r\n 7750 SR-14s/7s CPM-s v2 (SR-s CPM-2S) \r\n | \r\n\r\n x2-s36-800g-qsfpdd-18.0t \r\n | \r\n\r\n Nokia E5 \r\n | \r\n
| \r\n x2-s18-800g-qsfpdd \r\n | \r\n||
| \r\n x2-s36-800g-qsfpdd-12.0t \r\n | \r\n||
| \r\n ms16-sdd+4-qsfp28-b \r\n | \r\n\r\n BCM81343 \r\n | \r\n|
| \r\n ms8-sdd+2-qsfp28-b \r\n | \r\n\r\n BCM81343 \r\n | \r\n|
| \r\n mse24-200g-sfpdd \r\n | \r\n\r\n Nokia E5 \r\n | \r\n|
| \r\n mse6-800g-cfp2-dco \r\n | \r\n||
| \r\n mse14-800g+4-400g \r\n | \r\n||
| \r\n m36-800g-qsfpdd \r\n | \r\n||
| \r\n mse6-800g-qsfpdd \r\n | \r\n||
| \r\n m36-400g-qsfp112 \r\n | \r\n||
| \r\n 7750 SR-2s CPM \r\n | \r\n\r\n ms16-sdd+4-qsfp28-b \r\n | \r\n\r\n BCM81343 \r\n | \r\n
| \r\n ms8-sdd+2-qsfp28-b \r\n | \r\n\r\n BCM81343 \r\n | \r\n|
| \r\n 7750 SR-7 & SR-12 & SR-12e SR CPM5 \r\n | \r\n\r\n me16-25gb-sfp28+2-100gb-qsfp-b \r\n | \r\n\r\n BCM81343 \r\n | \r\n
| \r\n 7750 SR-1 CPM \r\n | \r\n\r\n me16-25gb-sfp28+2-100gb-qsfp-b \r\n | \r\n\r\n BCM81343 \r\n | \r\n
| \r\n 7250 IXR-R6 CPIOM \r\n | \r\n\r\n m10-10g-sfp+ \r\n | \r\n\r\n VSC8258 \r\n | \r\n
| \r\n m20-1g-csfp \r\n | \r\n\r\n VSC8584 \r\n | \r\n|
| \r\n m6-10g-sfp++1-100g-qsfp28 \r\n | \r\n\r\n BCM82399 and VSC8258 \r\n | \r\n|
| \r\n m4-10g-sfp++1-100g-cfp2 \r\n | \r\n\r\n BCM82399 and VSC8258 \r\n | \r\n|
| \r\n m6-10g-sfp++4-25g-sfp28 \r\n | \r\n\r\n BCM82399 and VSC8258 \r\n | \r\n|
| \r\n 7250 IXR-R4 CPM \r\n | \r\n\r\n m10-10g-sfp+ \r\n | \r\n\r\n VSC8258 \r\n | \r\n
| \r\n m20-1g-csfp \r\n | \r\n\r\n VSC8584 \r\n | \r\n|
| \r\n m6-10g-sfp++1-100g-qsfp28 \r\n | \r\n\r\n BCM82399 and VSC8258 \r\n | \r\n|
| \r\n m4-10g-sfp++1-100g-cfp2 \r\n | \r\n\r\n BCM82399 and VSC8258 \r\n | \r\n|
| \r\n m6-10g-sfp++4-25g-sfp28 \r\n | \r\n\r\n BCM82399 and VSC8258 \r\n | \r\n|
| \r\n 7250 IXR-e CPM (small) \r\n | \r\n\r\n m14-10g-sfp++4-1g-tx \r\n | \r\n\r\n VSC8490 \r\n | \r\n
Some TOE models, such as the 7250 IXR-R4 and 7250 IXR-R6, can be equipped with an MDA that includes two types of MACsec PHYs. These MDAs use both PHYs to handle MACsec protocols, resulting in certain ports on the MDA card using different PHYs for MACsec traffic encryption.
\r\nThe MACsec Key Agreement (MKA) protocol uses the Connectivity Association Key (CAK) to derive a Key Encryption Key (KEK), which secures the distribution of transient session keys called Secure Association Keys (SAKs). SAKs and other MKA parameters are required to sustain communication over secure channel and to perform encryption and other MACsec security functions. SAKs, along with other essential control information, are distributed in MKA protocol control packets, also referred to as MKPDUs. MACsec can be deployed in two modes:
\r\nIn the evaluated configuration, MACsec is configured individually on a point-to-point Ethernet link. A pair of MACsec devices can be connected via bridge or a direct connection. To enable secure MACsec communication, devices use the pre-shared Connectivity Association Key (CAK) to authenticate each other and execute the MACsec Key Agreement (MKA) protocol. MKA negotiates and distributes transient Secure Association Keys (SAKs), which are then used to encrypt/decrypt data traffic over the MACsec-secured channel.
\r\nIn order to determine an authorized peer, both devices must first exchange an MKA frame, and these devices must agree upon a shared key and MACsec cipher suite in order to set up both receive and transmit Security Associations (SA). Once the connections are established, the MACsec frames will be transmitted between devices. Figure 1 depicts the TOE boundary.
\r\n\r\nFigure 1 – TOE Boundary Diagram
","evaluation_configuration":"In the evaluated configuration, the TOE consists of the platforms as stated in Section 1.3 of the ST. The TOE supports secure connectivity with another IT environment device as stated in Table 7.
\r\nTable 7 – IT Environment Components
\r\n| \r\n Components \r\n | \r\n\r\n Required (Y/N) \r\n | \r\n\r\n Protocols used \r\n | \r\n\r\n Usage \r\n | \r\n
| \r\n Audit server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n TLS \r\n | \r\n\r\n The audit server supports Syslog over TLS v1.2 to receive audit events securely from the TOE. \r\n | \r\n
| \r\n LDAP server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n TLS \r\n | \r\n\r\n This server will provide the authentication mechanism to authenticate users. \r\n | \r\n
| \r\n RADIUS Server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n TLS \r\n | \r\n\r\n This server will provide the authentication mechanism to authenticate users. \r\n | \r\n
| \r\n MACsec peer \r\n | \r\n\r\n Yes \r\n | \r\n\r\n MACsec \r\n | \r\n\r\n This peer is required to test MACsec functionality. \r\n | \r\n
| \r\n Management workstation with console access/SSH client \r\n | \r\n\r\n Yes \r\n | \r\n\r\n CLI-SSH \r\n | \r\n\r\n This includes any IT \r\nEnvironment Management workstation with console access and an SSH client. \r\n | \r\n
| \r\n Certificate Authority server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n HTTP \r\n | \r\n\r\n The Certificate Authority server is used for issuing, generation and management of X509 certificates to be used with the TOE. \r\n | \r\n
The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Nokia 7750 SR & 7250 IXR, SROS 24.10.R3, MACsec platforms of Evaluation (TOE) was evaluated is described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 5. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 rev 5. The product, when delivered and configured as identified in the Common Criteria Administrator Guidance, satisfies all of the security functional requirements stated in the Nokia 7750 SR & 7250 IXR, SROS 24.10.R3, MACsec platforms Security Target. The project underwent CCEVS Validator review. The evaluation was completed in September 2025. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"The TOE implements the following security functional requirements:
\r\nEach of these security functionalities are listed in more detail in the sections below.
\r\nThe TOE generates audit events for all start-up and shut-down functions and all auditable events as specified in Table 20 in the ST. Audit events are also generated for management actions specified in FAU_GEN.1. The TOE is capable of storing audit events locally and exporting them to an external audit server using Syslog protocol over TLS v1.2 protocol. The TOE uses the Syslog protocol over TLS to transmit audit events in real-time, as they are generated, to an external audit server. Each audit record includes the date and time of the event, the event type, the identity of the subject, and any relevant event data.
\r\nThe TOE provides cryptographic support for the services described in the tables below. The related CAVP validation details are provided in Table 8. The operating system is SROS version 24.10.R3 running on TiMOS SMP version 2.5. The TOE leverages Nokia SR Cryptographic Module (SRCM) version 5 which is based on OpenSSL v3.1 library for its cryptographic functionality and incorporates the FIPS module 3.1.6-nokia.1.0 as its FIPS provider, to provide its cryptographic functionality.
\r\n\r\n
Table 8: TOEs CAVP Algorithm references
\r\n| \r\n SFRs \r\n | \r\n\r\n Algorithm in ST \r\n | \r\n\r\n Implementation Name \r\n | \r\n\r\n CAVP Alg \r\n | \r\n\r\n CAVP Cert \r\n | \r\n
| \r\n FCS_CKM.1 \r\n | \r\n\r\n RSA schemes using cryptographic key sizes of [2048, 3072 and 4096 bits] that meet the following: FIPS PUB 186-4, “Digital Signature Standard (DSS)”, Appendix B.3 or FIPS PUB 186-5, \"Digital Signature Standard (DSS)\", A.1. \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n RSA KeyGen (FIPS186-5) \r\n | \r\n\r\n A5455 \r\n | \r\n
| \r\n ECC schemes using ‘NIST curves’ [P-256, P-384, P-521] that meet the following: FIPS PUB 186-4, “Digital Signature Standard (DSS)”, Appendix B.4, or FIPS PUB 186-5, “Digital Signature Standard (DSS)”, Appendix A.2, or ISO/IEC 14888-3, “IT Security techniques - Digital signatures with appendix - Part 3: Discrete logarithm based mechanisms”, Section 6.6. \r\n | \r\n\r\n ECDSA KeyGen (FIPS186-5) \r\n\r\n ECDSA KeyVer (FIPS186-5) \r\n | \r\n\r\n A5455 \r\n | \r\n||
| \r\n FFC Schemes using ‘safe-prime’ groups that meet the following: “NIST Special Publication 800- 56A Revision 3, Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography” and [RFC 3526] \r\n | \r\n\r\n Lab tested using known good implementation \r\n | \r\n\r\n No NIST CAVP, CCTL has performed all assurance/evaluation activities and documented in the ETR and AAR accordingly. \r\n | \r\n||
| \r\n FCS_CKM.2 \r\n | \r\n\r\n RSA-based key establishment schemes that meet the following: RSAES-PKCS1-v1_5 as specified in Section 7.2 of RFC 8017, “Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.2” \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n Lab tested using known good implementation \r\n | \r\n\r\n No NIST CAVP, CCTL has performed all assurance/evaluation activities and documented in the ETR and AAR accordingly. \r\n | \r\n
| \r\n Elliptic curve-based key establishment schemes that meet the following: NIST Special Publication 800-56A Revision 3, “Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography” \r\n | \r\n\r\n KAS-ECC-SSC Sp800-56Ar3 \r\n | \r\n\r\n A5455 \r\n | \r\n||
| \r\n FFC Schemes using “safe-prime” groups that meet the following: ‘NIST Special Publication 800-56A Revision 3, “Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography” and [groups listed in RFC 3526] \r\n | \r\n\r\n Lab tested using known good implementation \r\n | \r\n\r\n No NIST CAVP, CCTL has performed all assurance/evaluation activities and documented in the ETR and AAR accordingly. \r\n | \r\n||
| \r\n FCS_COP.1/DataEncryption \r\n | \r\n\r\n GCM mode and cryptographic key sizes 128 bits, 256 bits that meet: AES as specified in ISO 18033-3 and GCM as specified in ISO 19772 \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n AES-GCM \r\n | \r\n\r\n A5455 \r\n | \r\n
| \r\n CBC mode and cryptographic key sizes 128 bits, 256 bits that meet: AES as specified in ISO 18033-3, CBC as specified in ISO 10116. \r\n | \r\n\r\n AES-CBC \r\n | \r\n|||
| \r\n CTR mode and cryptographic key sizes 128 bits, 256 bits that meet: AES as specified in ISO 18033-3, and CTR as specified in ISO 10116. \r\n | \r\n\r\n AES-CTR \r\n | \r\n|||
| \r\n FCS_COP.1/SigGen \r\n | \r\n\r\n RSA Digital Signature Algorithm using key sizes of 2048, 3072 and 4096 bits that meets FIPS PUB 186-4, “Digital Signature Standard (DSS)”, Section 5.5, using PKCS #1 v2.1 or FIPS PUB 186-5, \"Digital Signature Standard (DSS)\", Section 5.4 using PKCS #1 v2.2 Signature Schemes RSASSA-PSS and/or RSASSA-PKCS1v1_5; ISO/IEC 9796-2, Digital signature scheme 2 or Digital Signature scheme 3 \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n RSA SigGen (FIPS186-5) \r\nRSA SigVer (FIPS186-5) \r\n | \r\n\r\n A5455 \r\n | \r\n
| \r\n ECDSA schemes implementing [P-256, P-384, P-521] curves that meet the following: FIPS PUB 186-4, “Digital Signature Standard (DSS)”, Section 6 and Appendix D, Implementing “NIST Recommended\" curves ; or FIPS PUB 186-5, \"Digital Signature Standard (DSS)\", Section 6 and NIST SP 800-186 Section 3.2.1, Implementing Weierstrass curves; or ISO/IEC 14888-3, \"IT Security techniques - Digital signatures with appendix - Part 3: Discrete logarithm based mechanisms\", Section 6.6. \r\n | \r\n\r\n ECDSA SigGen (FIPS186-5) \r\nECDSA SigVer (FIPS186-5) \r\n\r\n | \r\n|||
| \r\n FCS_COP.1/Hash \r\n | \r\n\r\n SHA-1, SHA-256, SHA-384 and SHA-512 and message digest sizes 160, 256, 384 and 512 bits \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n SHA-1 \r\nSHA2-256 \r\nSHA2-384 \r\nSHA2-512 \r\n | \r\n\r\n A5455 \r\n | \r\n
| \r\n FCS_COP.1/KeyedHash \r\n | \r\n\r\n HMAC-SHA-1, HMAC-SHA-256, HMAC-SHA-384, HMAC-SHA-512 with key sizes 160 bits, 256 bits, 384 bits, 512 bits and message digest 160, 256, 384, 512 bits that meet the following: ISO/IEC 9797-2:2011, Section 7 “MAC Algorithm 2” \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n HMAC-SHA-1 \r\nHMAC-SHA2-256 \r\nHMAC-SHA2-384 \r\nHMAC-SHA2-512 \r\n | \r\n\r\n A5455 \r\n | \r\n
| \r\n FCS_COP.1/CMAC \r\n | \r\n\r\n keyed-hash message authentication with AES-CMAC and key sizes 128, 256 bits and message digest size of 128 bits that meets: NIST SP 800-38B. \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n AES-CMAC \r\n | \r\n\r\n A5455 \r\n | \r\n
| \r\n FCS_COP.1/MACSEC \r\n | \r\n\r\n Encryption and decryption in accordance with AES used in AES Key Wrap and key sizes 128 , 256 bits that meets AES as specified in ISO 18033-3, AES Key Wrap as specified in NIST SP 800-38F. \r\nEncryption and decryption in accordance with GCM and key sizes 128 , 256 bits that meets AES as specified in ISO 18033-3, GCM as specified in ISO 19772. \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n AES-KW \r\nAES-GCM \r\n | \r\n\r\n A5455 \r\n | \r\n
| \r\n FCS_RBG_EXT.1 \r\n | \r\n\r\n CTR_DRBG (AES) in accordance with ISO/IEC 18031:2011 with a minimum of 256-bits \r\n | \r\n\r\n Nokia SR Cryptographic Module (SRCM) version 5.0 \r\n | \r\n\r\n Counter DRBG \r\n | \r\n\r\n A5455 \r\n | \r\n
\r\n
The Broadcom PHY BCM81394 integrates two BCM81392 dies. As a result, each BCM81392 supports half the data rate per channel on the system side and half the number of 100G/10G ports. Additionally, PHY chips from Broadcom, Microsemi (now part of Microchip), and Nokia’s E5 series are used to perform AES-GCM encryption and decryption for the MACsec protocol. These PHYs have undergone CAVP testing by NIST to validate their cryptographic compliance.
\r\n\r\n
Table 9: MACsec PHYs CAVP Algorithm Testing References
\r\n| \r\n Cryptographic Algorithms \r\n | \r\n\r\n CAVPS \r\n | \r\n\r\n Implementation Library \r\n | \r\n\r\n PHY devices \r\n | \r\n\r\n Operational Environment (OE) \r\n | \r\n
| \r\n AES-GCM \r\n | \r\n\r\n AES 3969 \r\n | \r\n\r\n\r\n | \r\n\r\n VSC8258 \r\n | \r\n\r\n Microsemi Intellisec 10G PHY \r\n | \r\n
| \r\n AES 3191 \r\n | \r\n\r\n\r\n | \r\n\r\n VSC8258 \r\n | \r\n\r\n Vitesse Intellisec 10G PHY \r\n | \r\n|
| \r\n AES 3504 \r\n | \r\n\r\n\r\n | \r\n\r\n VSC85xx \r\n | \r\n\r\n Microsemi Intellisec 1G PHY \r\n | \r\n|
| \r\n AES 2781 \r\n | \r\n\r\n\r\n | \r\n\r\n VSC8490/91 \r\n | \r\n\r\n Mentor Graphics Questasim 10.0d \r\n | \r\n|
| \r\n AES 4545 \r\n | \r\n\r\n\r\n | \r\n\r\n BCM82396, \r\nBCM59202, \r\nBCM82399 \r\n | \r\n\r\n AES ECB 128bit & 256bit Encryption/Decryption Engine \r\n | \r\n|
| \r\n C1877 \r\n | \r\n\r\n\r\n | \r\n\r\n BCM81343, BCM81392, BCM81394, \r\nBCM81398 \r\n | \r\n\r\n AES ECB 128bit & 256bit Encryption/Decryption Engine \r\n | \r\n|
| \r\n A5786 \r\n | \r\n\r\n\r\n | \r\n\r\n Nokia E5 \r\n | \r\n\r\n Synopsys VCS 2023.03-SP2 \r\n | \r\n
The TOE supports Role Based Access Control. All users must be authenticated to the TOE prior to carrying out any management actions. The TOE supports password-based authentication and public key-based authentication. Based on the assigned role, a user is granted a set of privileges to access the system.
\r\nThe TOE supports local and remote management of its security functions including:
\r\nPrior to establishing an administration session with the TOE, a banner is displayed to the user. The banner messaging is customizable. The TOE will terminate an interactive session after configurable number of minutes of session inactivity. A user can terminate their local CLI session and remote CLI session by entering the appropriate command at the prompt.
\r\nThe TOE protects all passwords, pre-shared keys, symmetric keys, and private keys from unauthorized disclosure. Pre-shared keys, symmetric keys, and private keys are stored in encrypted format. Passwords are stored as a non-reversible hash value generated using a configurable hash function. The TOE executes self-tests during initial start-up to ensure correct operation and enforcement of its security functions. An administrator can install software updates to the TOE. The TOE internally maintains the date and time.
\r\nThe TOE supports syslog protocol over TLS v1.2 for secure communication to the audit server. The TOE supports TLS v1.2 for secure communication to LDAP and Radius servers for authentication. The TOE supports local CLI and uses SSH v2 for secure remote administration.
","features":[{"id":2434,"feature_name":"Asymmetric Key Generation"},{"id":2635,"feature_name":"Auditing"},{"id":2445,"feature_name":"Certificate Authentication"},{"id":2444,"feature_name":"Certificate Validation"},{"id":2441,"feature_name":"Cryptographic Hashing"},{"id":2435,"feature_name":"Cryptographic Key Establishment"},{"id":2439,"feature_name":"Cryptographic Signature Generation"},{"id":2440,"feature_name":"Cryptographic Signature Verification"},{"id":2437,"feature_name":"DRBG"},{"id":2436,"feature_name":"Key Destruction"},{"id":2442,"feature_name":"Keyed-hash message authentication"},{"id":2457,"feature_name":"MACsec"},{"id":2433,"feature_name":"Network Router"},{"id":2453,"feature_name":"SSH Server"},{"id":2451,"feature_name":"TLS 1.2"},{"id":2450,"feature_name":"TLS Client"}]}