808bits

N-able Cryptographic Module

FIPS 140-2 certificate #4182 · N-able Technologies Inc. · data as of 2026-10-09

N-able Cryptographic Module, from N-able Technologies Inc., holds FIPS 140-2 certificate #4182 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. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #3273

Certificate

Certificate number4182
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorN-able Technologies Inc. · website
Software versions2.2

Module description

Quoted from the NIST CMVP entry for this certificate.

The N-able Cryptographic Module is a standards-based cryptographic engine for N-able Take Control. The module delivers core cryptographic functions which are used in the context of remote control sessions.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AES4750
CKGvendor affirmed
DRBG1631
DSA1273
ECDSA1185
HMAC3164
RSA2594
SHS3893
Triple-DES2524

Tested configurations

  • CentOS 7.3 on a Dell Optiplex 755 with an Intel Celeron 430 processor (single-user mode)

Validation history

DateTypeLab
2022-03-21InitialLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2022-03-21

Source documents