808bits

CounterTack Sentinel Endpoint Module

FIPS 140-2 certificate #2525 · CounterTack, Inc. · data as of 2026-09-13

CounterTack Sentinel Endpoint Module, from CounterTack, Inc., holds FIPS 140-2 certificate #2525 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

Certificate

Certificate number2525
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorCounterTack, Inc. · website
Software versions3.6.6

Module description

Quoted from the NIST CMVP entry for this certificate.

The Sentinel Endpoint Module installs on target servers and workstations to provide cryptographic functionality for real-time threat detection and response capabilities. Deployed as part of CounterTack's Sentinel platform, the sensor communicates behavioral data to a central cluster, which provides real-time analysis, correlation with external threat intelligence and rapid-response containment that scales even the largest enterprises.

Security level exceptions

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

Approved algorithms (6)

AlgorithmCAVP certificates
AES3508
DRBG875
HMAC2241
RSA1803
SHS2893
Triple-DES1972

Other algorithms

RSA (non-compliant); Diffie-Hellman; EC Diffie-Hellman; MD5; AES GCM (non-compliant); DES; RC4; RIPEMD-160; HMAC-MD5

Tested configurations

  • Windows 7 (64-bit) running on a Sony Vaio Pro (single-user mode)

Validation history

DateTypeLab
2016-01-05InitialUL Verification Services, Inc.

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-01-05

Source documents