808bits

Huawei AR1200 and AR2200 Series Routers

FIPS 140-2 certificate #2901 · Huawei Technologies Co., Ltd. · 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 operated in FIPS mode and with the tamper evident seals installed as indicated in the Security Policy. The protocols IKEv1 and SNMP shall not be used when operated in FIPS mode.

Certificate

Certificate number2901
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorHuawei Technologies Co., Ltd. · website
Hardware versionsAR1220E P/N 02350DQJ Version E.5 with [1], AR1220EVW P/N 02350DQL Version F.5 with [1] and AR2220E P/N 02350DQM Version E.6 with [1]; Tamper Evident Seals P/N 4057-113016 [1]
Firmware versionsV200R008C10SPC110

Module description

ARs are located between an enterprise network and a public network, functioning as the only ingress and egress for data transmitted between the two networks. The deployment of various network services over the ARs reduces operation & maintenance (O&M) costs as well as those associated with establishing an enterprise network.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES4323, 4324, 4325
CKGvendor affirmed
CVL1036
DRBG1379
ECDSA1023
HMAC2861, 2862, 2863
KTS
KTS
SHS3565, 3566, 3567
Triple-DES2335, 2336, 2337

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); HMAC-SHA-1-96 (HMAC Cert. #2861); NDRNG; Blowfish; DES; HMAC-MD5; IKEv1 KDF (non-compliant); MD5; SM1; SM3; SM4; SNMP KDF (non-compliant)

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-05-08InitialUL 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: 2017-05-08

Source documents