808bits

7705 SAR-OS SAR-A/M Cryptographic Module (SARCM)

FIPS 140-2 certificate #4671 · Nokia Corporation · data as of 2026-10-09

7705 SAR-OS SAR-A/M Cryptographic Module (SARCM), from Nokia Corporation, holds FIPS 140-2 certificate #4671 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode and when installed, initialized and configured as specified in Sections 9.1 and 9.2 of the Security Policy.

Certificate

Certificate number4671
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorNokia Corporation · website
Software versionsSAR-OS 21.10R5

Module description

Quoted from the NIST CMVP entry for this certificate.

The 7705 SAR-OS SAR-A/M Cryptographic Module (SARCM) provides the cryptographic algorithm functions needed to allow SAR-OS to implement cryptography for those services and protocols that require it.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (11)

AlgorithmCAVP certificates
AESC2073
CKGvendor affirmed
CVLC2073
DRBGC2073
DSAC2073
HMACC2073
KAS
KAS-SSCA3135
RSAC2073
SHSC2073
Triple-DESC2073

Allowed algorithms

NDRNG

Tested configurations

  • SAR-OS 21.10R5 running on a SAR-A with a Cavium Octeon Plus processor
  • SAR-OS 21.10R5 running on a SAR-M with a Cavium Octeon Plus processor

Validation history

DateTypeLab
2023-12-14InitialAcumen Security

Status timeline

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

  • 2026-08-21: first observed by this tracker, status historical at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2023-12-14

Source documents