808bits

IBM Security SiteProtector System Cryptographic Module

FIPS 140-2 certificate #2563 · IBM Security · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When installed, initialized and configured as specified in the Security Policy Section 3. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2563
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorIBM Security · website
Software versions3.1.1

Module description

SiteProtector is a centralized management system that unifies management and analysis for network, server, and desktop protection agents and small networks or appliances. The SiteProtector is used as the central controlling point for IBM ISS appliances deployed on the network.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES3279
CVL462
DRBG737
ECDSA632
HMAC2076
RSA1676
SHS2717
Triple-DES1866

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides 112 or 128 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #462, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength)

Tested configurations

  • Microsoft Windows Server 2012 R2 Standard running on IBM Security SP 4001 with Intel Core i7-2600 @ 3.4GHz (1-CPU / 4-core) processor (single-user mode)

Validation history

DateTypeLab
2016-02-17InitialCOACT INC CAFE LAB

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-02-17

Source documents