--- title: "Algorithm Support" slug: "dsm-algorithm-support" updated: 2026-06-02T03:43:06Z published: 2026-06-02T03:43:06Z canonical: "support.fortanix.com/dsm-algorithm-support" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fortanix.com/llms.txt > Use this file to discover all available pages before exploring further. # Algorithm Support This page describes the algorithms supported by **Fortanix-Data-Security-Manager (DSM)**. *For more information on Fortanix DSM cryptographic policies, refer to the* [*User's Guide: Account Cryptographic Policy*](/v1/docs/users-guide-account-cryptographic-policy)*.* | **Crypto** | **Primitive Type** | **Algorithm** | **Mode/Method** | **Key Size/Curve** | **Import/export key format (Private/Public)** | **Use** | | --- | --- | --- | --- | --- | --- | --- | | Symmetric | Block cipher | AES | ECB, CBC, CBC (no padding), CFB, CTR, GCM, CCM, OFB, KW, KWP, CMAC, FF1 | 128, 192, or 256 bits | Raw | Data Encryption/Decryption, Key Wrapping/Unwrapping, MAC, Key Generation, Key Derivation, and Tokenization | | DES | ECB, CBC, CBC (no padding) | 56 bits | Data Encryption/Decryption, Key Wrapping/Unwrapping, MAC, Key Generation, and Key Derivation | | 3DES | 112, 168 bits | | ARIA | ECB, CBC, CBC (no padding), CFB, CTR, GCM, CCM | 128, 192, 256 bits | Data Encryption/Decryption, Key Wrapping/Unwrapping, and Key Derivation | | SEED | ECB, CTR, CBC, CBC (no padding) | 128 bits | | Cryptographic hash functions | SHA-1 | SHA-1 | HMAC key length: between 112 and 8192 bits | (HMAC) raw | Message Digest, MAC, and Key Generation | | SHA-2 | SHA-224, SHA-256, SHA-384, SHA-512 | | RIPEMD | RIPEMD-160 | | SHA-3 | SHA3-224, SHA3-256, SHA3-384, SHA3-512 | | | Message Digest and Key Generation | | Asymmetric | Finite field | KCDSA | standard | Between 512 and 2048 bits**7** | PKCS#8 DER/ SubjectPublicKeyInfo DER | Digital Signature sign/verify and Key Generation | | DSA | standard**1**, deterministic signatures (RFC 6979)**2** | Between 1024 and 8192 bits**3** | PKCS#8 DER/ SubjectPublicKeyInfo DER (RFC5208/RFC5280) | | Elliptic Curve | ECDSA | NIST P-192, NIST P-224, NIST P-256, NIST P-384, NIST P-521, SecP192K1, SecP224K1, SecP256K1 | PKCS#8 DER/ SubjectPublicKeyInfo DER (RFC5480/RFC5915) | | EC-KCDSA | standard | NIST P-192, NIST P-224, NIST P-256, NIST P-384, NIST P-521, SecP192K1, SecP224K1, SecP256K1 | PKCS#8 DER/ SubjectPublicKeyInfo DER | | EdDSA | standard**4**, prehash**4** | Ed25519 | PKCS#8 DER/ SubjectPublicKeyInfo DER (RFC8410) | | standard**8** | Ed448 | | ECDH | | NIST P-192, NIST P-224, NIST P-256, NIST P-384, NIST P-521, SecP192K1, SecP224K1, SecP256K1, X25519, X448 | PKCS#8 DER/ SubjectPublicKeyInfo DER (RFC5480/RFC5915/RFC8410) | Key Exchange and Key Generation | | BIP32 | Mainnet, Testnet | SecP256K1 | BIP32 Serialization format | Key Generation (HMAC), BIP32 child derivation, and Signature/verification of cryptocurrency transactions | | SLIP10 | | SecP256K1, NIST P-256 | SLIP32 Serialization format | Key Generation (HMAC), SLIP10 child derivation, and Digital Signature sign/verify | | BLS | Small signatures variant, small public keys variant | BLS12-381 | Public key: Uncompressed public point (SEC1 or appendix C of draft-irtf-cfrg-pairing-friendly-curves-10). Private key: 32 private key bytes concatenated with the uncompressed public point. | Digital Signature sign/verify and Key Generation | | | RSA | PKCS#1 v1.5**5**, OAEP**6**, PSS**6** | Between 1024 and 8192 bits | PKCS#8 DER/ SubjectPublicKeyInfo DER (RFC5208/RFC5280) | Data Encryption/Decryption, Digital Signature sign/verify, Key Wrapping/Unwrapping, and Key Generation | | | Asymmetric - Post-Quantum | Hash-based | LMS | HSS with L = 1 or L = 2 | LMOTS_SHA256_N{24, 32}_W{4,8} LMS_SHA256_M{24, 32}_H{5, 10, 15, 20} (NIST.SP.800-208) | Private key: Custom, Public key: SubjectPublicKeyInfo DER (RFC5280) | Digital Signature sign/verify, and Key Generation | | XMSS | Single tree | XMSS-SHA2_{10,16}_{192,256} (NIST.SP.800-208) | Private key: Custom, Public key: SubjectPublicKeyInfo DER (RFC5280) | Digital Signature sign/verify, and Key Generation | | Module lattices | ML-KEM | | ML-KEM-512, ML-KEM-768, ML-KEM-1024 | PKCS#8 DER/ SubjectPublicKeyInfo DER (draft-ietf-lamps-kyber-certificates-11)/FIPS 203 | Key Encapsulation/Decapsulation, and Key Generation | | ML-DSA | Pure ML-DSA and Hash ML-DSA**9**, external Mu, hedged and deterministic | ML-DSA-44, ML-DSA-65, ML-DSA-87 | PKCS#8 DER/ SubjectPublicKeyInfo DER (RFC9881)/FIPS 204 | Digital signature sign/verify, and Key Generation | **1** With hash algorithms: SHA-1, RIPEMD-160, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-224, SHA3-256, SHA3-384, SHA3-512, Blake2b***** (256, 384, 512), Blake2s-256***** **2** With hash algorithms: SHA-1, RIPEMD-160, SHA-224, SHA-256, SHA-384, SHA-512 **3** Imported keys can use any parameters. The key generation will use the following specific parameters: - 2048/224 and 2048/256: [[RFC 5114](https://tools.ietf.org/html/rfc5114)] - 3072/256: [[NIST example parameters](https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Standards-and-Guidelines/documents/examples/DSA2_All.pdf)] **4** With hash algorithms: SHA-512 **5** With hash algorithms (sign/verify): SHA-1, RIPEMD-160, SHA-224, SHA-256, SHA-384, SHA-512, SSL3***** **6** Supported mask generation functions: MGF1 with SHA-1, RIPEMD-160, SHA-224, SHA-256, SHA-384, SHA-512. The MGF hash function must be the same as the data hash function. **7** Imported keys can use any parameters. The key generation will use the following specific parameters: - 2048/224/SHA224 and 2048/256/SHA256: [[KISA](https://seed.kisa.or.kr/kisa/Board/62/detailView.do)] **8** With hash algorithms: SHAKE256 **9** With hash algorithms: SHA256, SHA512 ***** Hash algorithms not listed as a supported “Cryptographic hash function” on this page can only be used in signature generation/verification with prehashed data. Fortanix Data Security Manager (DSM) is the world’s first cloud service secured with Intel® SGX. With Fortanix DSM, you can securely generate, store, and use cryptographic keys and certificates, as well as other secrets such as passwords, API keys, tokens, or any blob of data. Your business-critical applications and containers can integrate with Fortanix DSM using legacy cryptographic interfaces (PKCS#11, CNG, and JCE) or using the native Fortanix DSM RESTful interface. ## Related - [Fortanix DSM for Google Workspace Client-Side Encryption](/fortanix-dsm-for-google-workspace-client-side-encryption.md) - [Algorithm Support - Strict FIPS Mode](/dsm-algorithm-support-strict-fips-mode.md) - [PKCS#11 Supported Functions and Mechanisms](/fortanix-dsm-clients-pkcs11-supported-functions-and-mechanisms.md) - [Key Operations](/fortanix-dsm-key-operations.md) - [Introduction](/dsm-example-code-introduction.md)