Manajemen Kunci dan Hashing

Welcome to this lesson on Key Management and Hashing! We'll explore how to protect the secrets that protect your data.

Cryptographic keys are fundamental to secure communication and data storage. Think of them as secret passwords or unique stamps that lock and unlock sensitive information.

The security of your entire system often depends on the security of your cryptographic keys.

• Data Breaches: If an attacker gains access to your encryption keys, all data encrypted with those keys becomes readable.
• Impersonation: Compromised signing keys can allow attackers to forge identities or tamper with data without detection.
• Trust Erosion: Loss of keys can lead to a complete breakdown of trust in your system's security posture.

Keys must be truly random and sufficiently long to be secure. Weak or predictable keys are easy for attackers to guess.

Always use cryptographically secure random number generators (CSRNGs) provided by your programming language's standard library. Never roll your own!

Try running this example to see how a secure key can be generated:

Once generated, keys need to be stored securely. This is one of the most critical aspects of key management.

• Hardware Security Modules (HSMs): Dedicated physical devices for secure key generation, storage, and cryptographic operations.
• Key Management Services (KMS): Cloud-based services (e.g., AWS KMS, Azure Key Vault) that provide secure key storage and lifecycle management.
• Avoid: Storing keys directly in source code, configuration files, or version control.

Even with the best storage, keys can eventually be compromised. Regular key rotation limits the damage if a key is ever exposed.

Key rotation involves generating a new key, re-encrypting data with the new key, and securely archiving or destroying the old key. This reduces the 'window of exposure' for any single key.

Hashing is a one-way process that transforms input data into a fixed-size string of characters, called a hash or digest.

• One-way: You can't easily reverse a hash to get the original data.
• Fixed-size: No matter the input size, the output hash is always the same length.
• Unique (mostly): A tiny change in input results in a vastly different hash.

Hashing is crucial for verifying data integrity and securely storing passwords.

Never store user passwords in plain text or encrypted form. Always store their hash.

If a database is breached, attackers only get hashes, not the actual passwords. Since hashing is one-way, they can't easily recover the original passwords.

However, simple hashing isn't enough on its own. We need more techniques!

A salt is a unique, random string added to a password before it's hashed. Each user gets a different salt.

Salting prevents rainbow table attacks, where attackers pre-compute hashes for common passwords. With salts, even if two users have the same password, their stored hashes will be completely different.

This example conceptually shows how a salt is added before hashing:

For password hashing, don't use general-purpose hash functions like SHA-256 or MD5. They are too fast, making brute-force attacks easier.

Instead, use algorithms specifically designed to be slow and computationally intensive:

• Bcrypt: Widely used and highly recommended.
• Scrypt: Another strong option, especially resistant to GPU-based attacks.
• Argon2: The winner of the Password Hashing Competition, considered state-of-the-art.

These algorithms have adjustable 'work factors' to increase their computational cost over time.

Cryptography is complex. Common mistakes can severely weaken your security:

• Don't 'Roll Your Own' Crypto: Always use well-vetted, standard cryptographic libraries. Custom implementations are almost always insecure.
• Hardcoding Keys: Never embed encryption keys directly in your code.
• Using Weak Algorithms: Avoid deprecated or known-vulnerable algorithms (e.g., MD5, SHA1 for security, DES, RC4).
• Improper Randomness: Don't use non-cryptographically secure random number generators for security tasks.

Which of the following are recommended best practices for managing cryptographic keys and passwords?

In this lesson, we've covered the vital aspects of cryptographic key management and secure password hashing.

• Keys: Generate strong, random keys, store them securely (HSM/KMS), and rotate them regularly.
• Hashing: Always hash passwords using unique salts and slow, purpose-built algorithms like bcrypt, scrypt, or Argon2.
• Avoid Pitfalls: Never create your own crypto, hardcode keys, or use weak algorithms.

By following these practices, you significantly strengthen your backend applications against data breaches and unauthorized access. Keep learning and stay secure!