808bits

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

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

7705 SAR-OS SAR-A/M Cryptographic Module (SARCM), from Nokia Corporation, holds FIPS 140-2 certificate #3331 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. SP 800-56Arev3 transition. 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 number3331
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorNokia Corporation · website
Software versionsSAR-OS Rel 8.0R6

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 (9)

AlgorithmCAVP certificates
AES4657
CKGvendor affirmed
CVL1306
DRBG1573
DSA1232
HMAC3085
RSA2541
SHS3816
Triple-DES2478

Allowed algorithms

Diffie-Hellman (CVL Cert. #1306, key agreement; key establishment methodology provides 112 bits of encryption strength); NDRNG

Tested configurations

  • SAR-OS Rel 8.0R6 running on a SAR-A with a Cavium Octeon Plus processor
  • SAR-OS Rel 8.0R6 running on a SAR-M with a Cavium Octeon Plus processor

Validation history

DateTypeLab
2018-11-21InitialEWA - Canada
2018-12-04UpdateEWA - 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: 2018-11-21, 2018-12-04

Source documents