BC-FNA (Bouncy Castle FIPS .NET API)
Caveat: When installed, initialized and configured as specified in the Security Policy Section 8 and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys.
Certificate
| Certificate number | 2792 |
|---|---|
| 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.1.1 |
Module description
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
| Algorithm | CAVP certificate |
|---|---|
| AES | C2202 |
| CVL | C2202 |
| DRBG | C2202 |
| DSA | C2202 |
| ECDSA | C2202 |
| HMAC | C2202 |
| KAS-SSC | vendor affirmed |
| KTS | |
| KTS | |
| KTS | vendor affirmed |
| PBKDF | vendor affirmed |
| RSA | C2202 |
| SHA-3 | C2202 |
| SHS | C2202 |
| Triple-DES | C2202 |
Other algorithms
MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); AES (non-compliant); ARC4; Camellia; ChaCha; ElGamal; NewHope; OpenSSL PBKDF; PKCS#12 PBKDF; Poly1305; SEED; Serpent; SPHINCS-256
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 |
|---|---|---|
| 2016-11-14 | Initial | CGI Information Systems & Management Consultants Inc |
| 2021-04-19 | Update | 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
- Validation dates on record: 2016-11-14, 2021-04-19