808bits

Catbird vSecurity Crypto Module v1.0

FIPS 140-2 certificate #1760 · Catbird Networks, Inc. · data as of 2026-10-09

Catbird vSecurity Crypto Module v1.0, from Catbird Networks, Inc., holds FIPS 140-2 certificate #1760 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1760
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorCatbird Networks, Inc. · website
Software versionsv1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

Catbird is the industry pioneer in security and compliance for virtualized environments, a four-time Best of Show Finalist at VMworld and a Gartner Group Cool Vendor 2011. Catbird's comprehensive protection includes monitoring and enforcement of PCI, NIST, HIPAA, FISMA, DIACAP and other requirements in virtual environments. Maintaining regulatory and corporate compliance in the new data center and eliminating uncertainty over secure virtualization, Catbird's protection keeps Tier-1 application deployment plans on track.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Design Assurance: Level 3

Approved algorithms (10)

AlgorithmCAVP certificates
AES1922
CVL14
DRBG166
DSA609
ECDSA274
HMAC1157
RNG1010
RSA991
SHS1688
Triple-DES1252

Other algorithms

EC Diffie-Hellman; RSA (encrypt/decrypt)

Tested configurations

  • CentOS 6.0 running on Intel Core i5 with PAA (single-user mode)

Validation history

DateTypeLab
2012-07-27InitialUL 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: 2012-07-27

Source documents