An enterprise security architect is standardizing cryptographic controls across a zero-trust network infrastructure. Match each security design requirement on the left with the most appropriate cryptographic mechanism or algorithm on the right.
- Negotiating a transient shared secret over an untrusted channel to provide Perfect Forward Secrecy (PFS) for TLS sessionsECDHE (Elliptic Curve Diffie-Hellman Ephemeral)
- Providing simultaneous payload confidentiality, integrity verification, and origin authenticity in a single symmetric operationAES-GCM (Authenticated Encryption with Associated Data)
- Mitigating offline GPU-accelerated brute-force attacks against stored user credential hashes using configurable memory-hard work factorsArgon2id key derivation function
- Ensuring non-repudiation and origin verification for published software updates without encrypting the file binary itselfECDSA (Elliptic Curve Digital Signature Algorithm)
Cevap
1. Negotiating a transient shared secret with PFS matches ECDHE; 2. Simultaneous confidentiality, integrity, and authenticity matches AES-GCM; 3. Mitigating GPU brute-force cracking of stored credentials matches Argon2id; 4. Non-repudiation for software updates without payload encryption matches ECDSA.
Each requirement directly aligns with the operational purpose of the corresponding cryptographic primitive: ECDHE for forward-secret key exchange, AES-GCM for authenticated symmetric encryption, Argon2id for memory-hard credential hashing, and ECDSA for asymmetric digital signatures.
Adım Adım Çözüm
Anahtar Kavram
Cryptographic Concepts and Algorithms