Cryptographic & Algorithmic Standards

This article lists the cryptographic standards, encryption practices, and implementation rules Praetorian uses to protect customer data.

Transport Layer Security (TLS)

• TLS Versions: We require TLS 1.2 or 1.3 for secure communications. Older versions such as TLS 1.0 and 1.1 are not permitted, even if FIPS 140-2 compliant, as they are explicitly disallowed by FIPS 140-3, NIST SP 800-53, and FedRAMP guidelines.
• Preferred Algorithms for TLS:
  1. ECDHE-ECDSA-AES256-GCM-SHA384
  2. ECDHE-RSA-AES256-GCM-SHA384
  3. ECDHE-ECDSA-AES128-GCM-SHA256
  4. ECDHE-RSA-AES128-GCM-SHA256
  5. TLS_AES_256_GCM_SHA384
  6. TLS_AES_128_GCM_SHA256

Quantum-Safe Cryptography (Forward-Looking Guidance)

Status: The algorithms in this section describe our post-quantum roadmap and internal recommendations, not capabilities currently deployed in the Praetorian Guard Platform. Today's production cryptography relies on the classical, quantum-resistant-where-applicable primitives described in the surrounding sections (AES-256, SHA-2/SHA-3, ECDHE-based TLS 1.2/1.3, etc.). We are tracking NIST's post-quantum standards and will roll out support as upstream libraries, FIPS-certified modules, and our cloud providers expose them.

• Key Encapsulation Mechanism (KEM): When we adopt post-quantum KEMs, our target is ML-KEM-768, a NIST-approved quantum-safe algorithm. For FIPS environments, ML-KEM will be sourced from a FIPS-certified cryptographic module.
• Digital Signatures: Our target post-quantum signature algorithm is ML-DSA-65 with a 256-bit random seed. In certain contexts, SLH-DSA is an alternative we are evaluating, particularly for embedded applications or systems requiring a longer security horizon.

Encryption Standards

Block Ciphers

• AES (Advanced Encryption Standard): AES-128 is the minimum, but AES-256 is preferred for "future-proofing" against emerging threats. All implementations must use Galois Counter Mode (GCM) for authenticated encryption.
• Quantum Resistance: AES-256 is considered quantum-resistant, making it a cornerstone of our encryption strategy.

Full-Disk Encryption

• Algorithms: For laptop full-disk encryption, XTS-AES-128 (256-bit key) or XTS-AES-256 (512-bit key) are acceptable. These are pre-configured for Praetorian-approved devices running macOS or Ubuntu.

Digital Signature Algorithms

• Approved Algorithms:

  • RSA: Minimum key size of 2048 bits.
  • ECDSA: Minimum key size of 224 bits.
  • EdDSA: Ed25519 and Ed448 are approved when certified in the cryptographic module.

• Quantum-Safe Signatures (roadmap): As post-quantum support becomes available in our stack, ML-DSA-65 is our target for most use cases, with SLH-DSA under evaluation for specific applications. See Quantum-Safe Cryptography (Forward-Looking Guidance) above.

Hash Functions

• SHA-2 Family: SHA-256 is the minimum requirement, with SHA-384 or higher preferred where supported.
• Quantum Resistance: SHA-2-256+ and SHA-3-256+ are considered quantum-resistant.
• Disallowed Algorithms:
  • SHA-1: Permitted only for specific non-cryptographic uses where collision resistance is not required.
  • MD5: Prohibited entirely.

Message Authentication Codes (MAC)

• Approved Algorithms:
  • HMAC: Key length must be 112 bits or greater.
  • KMAC: Used for specific authenticated encryption requirements.
  • CMAC and GMAC: Only used with AES. HMAC is preferred for most applications, while GMAC is not recommended for general purposes.

Random Number Generation

• /dev/random: Our standard for secure pseudo-random number generation. It ensures high entropy and aligns with FIPS guidelines.
• /dev/urandom: Used where appropriate. In modern systems (Linux kernel 5.18+), it operates equivalently to /dev/random in FIPS mode.

Password storage

• Password storage is managed by AWS Cognito using SRP protocol with a 16-character minimum complexity policy including uppercase, lowercase, numbers, and symbols.

Deprecated and Disallowed Algorithms

• DSA: No longer approved under FIPS 186-5.
• SHA-1: Not allowed for digital signatures or cryptographic functions requiring collision resistance.
• MD5: Prohibited for all uses.

Implementation Guidance

Secure Coding Practices

• Our developers follow strict secure coding guidelines tailored to the languages and frameworks used in our products.
• Regular code reviews and security audits ensure adherence to these guidelines.

FIPS-Certified Modules

• All cryptographic implementations in FIPS environments use certified modules to ensure compliance with FIPS 140-3.

For questions or additional details, please contact us at security@praetorian.com.