BC-FNA (Bouncy Castle FIPS .NET API)
BC-FNA (Bouncy Castle FIPS .NET API), from Legion of the Bouncy Castle Inc., holds FIPS 140-2 certificate #4416 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. No assurance of the minimum strength of generated keys.
Certificate
| Certificate number | 4416 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Legion of the Bouncy Castle Inc. · website |
| Software versions | 1.0.2 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Bouncy Castle FIPS .NET API is a comprehensive suite of FIPS Approved algorithms implemented in pure C#. All key sizes and modes have been implemented to allow flexibility and efficiency, and additional algorithms, including some post-quantum ones, are available in non-approved operation as well.
Security level exceptions
- Physical Security: N/A
Approved algorithms (17)
| Algorithm | CAVP certificates |
|---|---|
| AES | A1905 |
| CKG | vendor affirmed |
| CVL | A1905 |
| DRBG | A1905 |
| DSA | A1905 |
| ECDSA | A1905 |
| HMAC | A1905 |
| KAS | A1905 |
| KAS-SSC | A1905 |
| KDA | A1905 |
| KTS | |
| KTS-RSA | |
| PBKDF | A1905 |
| RSA | A1905 |
| SHA-3 | A1905 |
| SHS | A1905 |
| Triple-DES | A1905 |
Allowed algorithms
RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
Tested configurations
- Microsoft Windows 10 Professional (64-bit) on .NET 4.5.2 framework running on Dell XPS 15 7590 with Intel Core i7-9750H (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-01-18 | Initial | Acumen Security |
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: 2023-01-18