808bits

Huawei AP2030, AP4030, AP4130, AP5030, AP5130, AP6050, AP6150, AP7050 and AP8130 Wireless Access Points

FIPS 140-2 certificate #2994 · Huawei Technologies Co., Ltd. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. 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 Section 5.1 of the Security Policy. The protocol TLS shall not be used when operated in FIPS mode.

Certificate

Certificate number2994
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorHuawei Technologies Co., Ltd. · website
Hardware versionsP/Ns AP2030DN, AP4030DN, AP4130DN, AP5030DN, AP5130DN, AP6050DN, AP6150DN, AP7050DE and AP8130DN with Tamper-evident Seals 4057-113016
Firmware versionsV200R007C10SPC100

Module description

The Huawei AP AP2030, AP4030, AP4130, AP5030, AP5130, AP6050, AP6150, AP7050 and AP8130 Wireless Access Points are multi-chip standalone cryptographic modules enclosed in hard, commercial grade plastic and metal cases. The cryptographic boundary for these modules is the enclosure. The primary purpose of these modules is to provide secure communication for data transmitted between different networks. The modules provide network interfaces for data input and output.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES4408
CKGvendor affirmed
CVL1114
DRBG1421
ECDSA1060
HMAC2930
SHS3634
Triple-DES2375

Allowed algorithms

Diffie Hellman (CVL Cert. #1114, key agreement; key establishment methodology provides 112 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

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

Source documents