808bits

XTM 515, XTM 525, XTM 535 and XTM 545

FIPS 140-2 certificate #2046 · WatchGuard Technologies, Inc. · data as of 2026-08-28
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 and the tamper evident seals installed as indicated in the Security Policy. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number2046
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorWatchGuard Technologies, Inc. · website
Hardware versionsNC2AE8 (XTM 515, XTM 525, XTM 535 and XTM 545) with Tamper Evident Seal Kit: SKU WG8566
Firmware versionsFireware XTM OS v11.5.5

Module description

WatchGuard Fireware XTM extensible threat management appliances are built for enterprise-grade performance with blazing throughput and numerous connectivity options. Advanced networking features include clustering, high availability (active/active), VLAN support, multi-WAN load balancing and enhanced VoIP security, plus inbound and outbound HTTPS inspection, to give the strong security enterprises need.

Approved algorithms

AlgorithmCAVP certificate
AES1659, 2180
DSA684
ECDSA339
HMAC974, 1334
RNG1103
RSA1124
SHS1453, 1890
Triple-DES1079, 1380

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); DES; RC4; MD5; TKIP; AES-CCM (non-compliant); Password Based Key Derivation Function (for 128 bit AES key; non-compliant)

Validation history

DateTypeLab
2013-11-18InitialEWA - Canada

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: 2013-11-18

Source documents