808bits

LogRhythm

12 FIPS 140 certificates · 0 active · data as of 2026-10-21

LogRhythm holds 12 FIPS 140 certificates in NIST's Cryptographic Module Validation Program, covering LogRhythm. None are active: all 12 are historical or revoked.

5 certificates went historical at the FIPS 140-2 sunset. Every FIPS 140-2 validation still active moved to the historical list on 2026-09-21. What that means and the full list.
CertModuleStandardStatusLevelValidated
4300LogRhythm 7.8.0 AI Engine ServerFIPS 140-2historical12022-09-12
4290LogRhythm 7.8.0 System Monitor AgentFIPS 140-2historical12022-08-31
4289LogRhythm 7.8.0 Platform ManagerFIPS 140-2historical12022-08-31
4288LogRhythm 7.8.0 ConsoleFIPS 140-2historical12022-08-31
4275LogRhythm 7.8.0 Data ProcessorFIPS 140-2historical12022-08-08
3493LogRhythm FIPS Object Module for OpenSSLFIPS 140-2historical12019-07-17
2454LogRhythm FIPS Object ModuleFIPS 140-2historical12015-09-30
1817LogRhythm 6.0.4 or 6.3.4 Event ManagerFIPS 140-2historical12012-10-11
1808LogRhythm 6.0.4 or 6.3.4 Log ManagerFIPS 140-2historical12012-10-02
1807LogRhythm 6.0.4 or 6.3.4 ConsoleFIPS 140-2historical12012-10-02
1806LogRhythm 6.0.4 or 6.3.4 Windows System Monitor AgentFIPS 140-2historical12012-10-02
1805LogRhythm 6.0.4 or 6.3.4 AI Engine ServerFIPS 140-2historical12012-10-02

NIST records the vendor as free text, so one company can appear under several spellings. Those are grouped here. Corporate families are not: a product line can change owner, and the certificates stay with the registration that earned them. The nShield modules run from nCipher Corporation through Thales to Entrust, and this tracker keeps those as three vendors because that is how NIST holds them.