808bits

Sophos Cryptographic Module

FIPS 140-2 certificate #4100 · Sophos Limited · data as of 2026-10-09

Sophos Cryptographic Module, from Sophos Limited, holds FIPS 140-2 certificate #4100 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. No assurance of the minimum strength of generated keys.

Certificate

Certificate number4100
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSophos Limited · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Sophos Cryptographic Module is a general-purpose cryptographic library incorporated into the Sophos Firewall systems to provide FIPS 140-2 validated cryptography for the protection of sensitive information.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Physical Security: N/A
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (10)

AlgorithmCAVP certificates
AESA1398
CKGvendor affirmed
DRBGA1398
DSAA1398
ECDSAA1398
HMACA1398
KAS-SSC
RSAA1398
SHSA1398
Triple-DESA1398

Allowed algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • Sophos Firewall Operating System (SFOS) 18.5 running on XGS 3100 with AMD Ryzen Embedded V1780B with PAA
  • Sophos Firewall Operating System (SFOS) 18.5 running on XGS 3100 with AMD Ryzen Embedded V1780B without PAA (single user mode)

Validation history

DateTypeLab
2021-12-13InitialAcumen 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
  • Validation dates on record: 2021-12-13

Source documents