808bits

Vocera Cryptographic Module

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

Vocera Cryptographic Module, from Vocera Communications, Inc., holds FIPS 140-2 certificate #4393 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 configured and initialized as specified in the Security Policy.

Certificate

Certificate number4393
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware
EmbodimentMulti-Chip Stand Alone
VendorVocera Communications, Inc. · website
Firmware versions6.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Vocera C1000 Module is a firmware module that provides the cryptographic primitives (including encryption/decryption, hashing, digital signature functions, and key derivation) needed to support secure communication services to the system.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AESA2059
CVLA2059
ECDSAA2059
HMACA2059
KAS-SSCA2059
KTS
RSAA2059
SHSA2059

Allowed algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 152 bits of encryption strength)

Tested configurations

  • Vocera C1000 Badge running Vocera’s proprietary BadgeOS 6.0 on NXP i.MX 6 processor

Validation history

DateTypeLab
2022-12-15InitialDEKRA Testing and Certification S.A.U

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-12-15

Source documents