Cryptographic Design Decisions
What you'll learn: How to select the right encryption algorithms, manage keys securely, and choose appropriate protocols when designing secure systems.
Making Cryptographic Choices That Last
During the architectural design phase, you'll face critical decisions about cryptography that affect your system's security for years. These aren't implementation details—they're foundational choices that become expensive or impossible to change later.
Think of cryptography like choosing the locks and safe for a bank vault during construction. You can't easily swap them once the building is complete and customers have keys.
Key Decision Areas
Algorithm Selection: Choose proven, current algorithms rather than inventing your own or using outdated ones. For symmetric encryption, AES-256 remains the standard. For hashing passwords, use bcrypt, Argon2, or PBKDF2—never plain SHA-256. For asymmetric encryption, RSA (minimum 2048-bit) or elliptic curve cryptography (ECC) are appropriate choices.
Key Management Architecture: Design how keys are generated, stored, rotated, and destroyed. Will you use a hardware security module (HSM), cloud key management service (KMS), or software-based vault? Keys should never live in code or configuration files—they need dedicated secure storage with audit trails.
Protocol Selection: Choose established protocols like TLS 1.3 for transport, not older versions with known vulnerabilities. When designing APIs, decide whether to use mutual TLS, signed tokens (JWT with RS256/ES256), or API key schemes—each has different security properties and operational complexity.
Cryptographic Agility: Design systems so you can swap algorithms later without rewriting everything. Store algorithm identifiers with encrypted data, abstract crypto operations behind interfaces, and plan key rotation from day one.
Key Takeaway: Cryptographic design decisions should prioritize proven algorithms, secure key management infrastructure, modern protocols, and the flexibility to evolve as threats change—choices made during architecture become security foundations that are costly to replace later.