808bits

SR-OS Cryptographic Module

FIPS 140-2 certificate #2786 · Nokia Corporation · data as of 2026-10-21

SR-OS Cryptographic Module, from Nokia Corporation, holds FIPS 140-2 certificate #2786 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. When installed, initialized and configured as specified in the Security Policy Section 9.1

Certificate

Certificate number2786
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware
EmbodimentMulti-Chip Stand Alone
VendorNokia Corporation · website
Firmware versions14.0R4

Module description

Quoted from the NIST CMVP entry for this certificate.

The SR-OS Cryptographic Module (SRCM) provides the cryptographic algorithm functions needed to allow SR-OS to implement cryptography for those services and protocols that require it.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (9)

AlgorithmCAVP certificates
AES4011
CVL835
DRBG1193
DSA1086
ECDSA893
HMAC2616
RSA2058
SHS3309
Triple-DES2198

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); NDRNG

Tested configurations

  • SR-OS on CFP-7750 SR-c12 CFM-XP-B
  • SR-OS on CPM-7750 SR CPM5
  • SR-OS on CPM-7750 SR-a
  • SR-OS on CPM-7750 SR-e
  • SR-OS on CPM-7950 XRS-16 CPM
  • SR-OS on CPM-7950 XRS-20 CPM

Validation history

DateTypeLab
2016-11-07InitialEWA - Canada

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2016-11-07

Source documents