Alteryx Cryptographic Module
Alteryx Cryptographic Module, from Alteryx Inc., holds FIPS 140-2 certificate #3711 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Certificate
| Certificate number | 3711 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Alteryx Inc. · website |
| Software versions | 2.0.9, 2.0.10, 2.0.11, 2.0.12, 2.0.13, 2.0.14, 2.0.15 or 2.0.16 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Alteryx FIPS Module for OpenSSL is a general-purpose cryptographic module integrated in Alteryx’s products to provide FIPS 140-2 validated cryptography for the protection of sensitive information.
Security level exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms (9)
| Algorithm | CAVP certificates |
|---|---|
| AES | C1990 |
| CVL | C1990 |
| DRBG | C1990 |
| DSA | C1990 |
| ECDSA | C1990 |
| HMAC | C1990 |
| RSA | C1990 |
| SHS | C1990 |
| Triple-DES | C1990 |
Allowed algorithms
EC Diffie-Hellman (CVL Cert. #C1990, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)
Tested configurations
- Windows Server 2016 running on HPE ProLiant DL60 Gen9 with Intel Xeon E5-2609 with PAA
- Windows Server 2016 running on HPE ProLiant DL60 Gen9 with Intel Xeon E5-2609 without PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2020-09-21 | Initial | Acumen Security |
| 2020-12-01 | 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: 2020-09-21, 2020-12-01