Microsoft Azure Networking Adapter Kernel
Microsoft Azure Networking Adapter Kernel, from Microsoft Corporation, holds FIPS 140-2 certificate #4273 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When operated in FIPS mode. The module generates random strings whose strengths are modified by available entropy
Certificate
| Certificate number | 4273 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software-Hybrid |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Microsoft Corporation · website |
| Software versions | 1.0 |
| Hardware versions | BCM58732 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Cryptographic Library is a general-purpose, software-hybrid cryptographic module. The module provides general purpose cryptographic services that leverage FIPS 140-2-approved cryptographic algorithms. The module runs as part of the operating system kernel, provides cryptographic services to kernel applications through a C language Application Program Interface (API), and provides cryptographic services to user applications through an AF_ALG socket-type interface. The module is implemented as a set of shared libraries and binary files.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
Tested configurations
- Immutable OS version 1.0 (build 5.10.54.4-microsoft-standard-2008.3.21082301) running on an Azure Compute C2030 Server with a Broadcom SoC 8 Core ARM v8 Cortex A72 with PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-07-25 | Initial | Leidos Accredited Testing & Evaluation (AT&E) Lab |
| 2022-08-22 | Update | Leidos Accredited Testing & Evaluation (AT&E) 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2022-07-25, 2022-08-22