808bits

HealthStackIO Platform Cryptographic Module

FIPS 140-2 certificate #2265 · HealthStackIO Inc. · data as of 2026-09-03

HealthStackIO Platform Cryptographic Module, from HealthStackIO Inc., holds FIPS 140-2 certificate #2265 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: When operated in FIPS mode

Certificate

Certificate number2265
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorHealthStackIO Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

Cryptographic layer for HealthStackIO platform

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (10)

AlgorithmCAVP certificates
AES2273
CVL44
DRBG281
DSA709
ECDSA368
HMAC1391
RNG1132
RSA1166
SHS1954
Triple-DES1420

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • CentOS 6.3 on a Dell OptiPlex 755
  • Mac OS X 10.8 on a MacBook Air
  • Microsoft Windows Server 2008 R2 on a Dell OptiPlex 755
  • Red Hat Enterprise Linux 6.3 on a Dell OptiPlex 755
  • SUSE Linux Enterprise 11SP2 on a Dell OptiPlex 755 (single-user mode)

Validation history

DateTypeLab
2014-10-10InitialUL 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: 2014-10-10

Source documents