808bits

Vocera Cryptographic Module v3.0

FIPS 140-2 certificate #2619 · Vocera Communications, Inc. · data as of 2026-10-21

Vocera Cryptographic Module v3.0, from Vocera Communications, Inc., holds FIPS 140-2 certificate #2619 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. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number2619
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware-Hybrid
EmbodimentMulti-Chip Stand Alone
VendorVocera Communications, Inc. · website
Software versions3.0
Hardware versions88W8787; Firmware Version: 3.0

Module description

Quoted from the NIST CMVP entry for this certificate.

Vocera B3000n Badge is a wearable hands-free voice-controlled device that provides easy-to-use and instantaneous communication on a wireless LAN network. The Vocera Cryptographic Module, embedded in the B3000n Badge, ensures protected communications using industry-standard secure wireless communication protocols.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (6)

AlgorithmCAVP certificates
AES3531, 3532
CVL586
DRBG888
HMAC2257
RSA1815
SHS2912

Other algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 of encryption strength; non-compliant less than 112 bits of encryption strength); MD5; HMAC-MD5

Tested configurations

  • Vocera Embedded Linux Version 3.0 running on a B3000n badge (single-user mode)

Validation history

DateTypeLab
2016-04-19InitialDXC Technology

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-04-19

Source documents