808bits

Alaris™ PC Unit Model 8015

FIPS 140-2 certificate #4227 · BD · data as of 2026-10-09

Alaris™ PC Unit Model 8015, from BD, holds FIPS 140-2 certificate #4227 at overall level 2. 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: The tamper-evident seals installed as indicated in the Security Policy

Certificate

Certificate number4227
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorBD · website
Hardware versionsModel 8015 b/g, Model 8015 a/b/g, Model 8015 a/b/g/n or BD Alaris Model 8015 a/b/g/n with FIPS Kit 49000550
Firmware versions12.1.3

Module description

Quoted from the NIST CMVP entry for this certificate.

The BD Alaris™ PC Unit Model 8015 is a point-of-care unit, which is the main component of the Alaris System. The Alaris System is a modular system intended for adult, pediatric, and neonatal care in a professional healthcare environment. The Alaris System brings a higher level of medication error prevention to the point of patient care.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (5)

AlgorithmCAVP certificates
AES4428
HMAC3560
KTS
RSA2410
SHS3646

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-05-16InitialUL Verification Services, Inc.
2023-02-14UpdateUL 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-05-16, 2023-02-14

Source documents