GSEC Cryptography Practice Question
A software vendor distributes signed firmware updates to customers. During an incident review, an analyst discovers that an attacker who obtained the vendor's code-signing private key was able to produce updates that passed signature verification on customer devices. The vendor wants to redesign the signing process so that compromise of a single signing key no longer allows an attacker to forge valid updates. Which change best achieves this goal?
⚠ Common exam trap
The trap here is conflating stronger cryptography with stronger key custody; a bigger key or a modern algorithm cannot protect against an attacker who already holds the private key.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Require each update to be signed by a threshold of multiple independent keys.
Threshold signing distributes the signing capability across multiple independent keys so that no single compromised key can produce a valid signature. Increasing key size, changing to ECDSA, or adding a transparency log all leave a single key capable of forging updates. Only requiring a quorum of keys changes the trust model so that one stolen key is insufficient.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the RSA key size from 2048 to 4096 bits.
Why it's wrong here
Increasing key size raises the computational cost of brute-force attacks against the key, but it does nothing to prevent misuse of a key that has already been stolen. The attacker in this scenario possesses the private key outright, so a larger modulus only makes signing slightly slower. Key-length hardening is a valid defense-in-depth measure but does not address the stated compromise scenario.
- ✓
Require each update to be signed by a threshold of multiple independent keys.
Why this is correct
Threshold signing requires a quorum of distinct private keys, often held in separate HSMs or by separate administrators, to produce one valid signature. An attacker who compromises a single key cannot meet the threshold, so forged updates fail verification. This directly addresses the goal of making single-key compromise insufficient, and it is supported by standards such as FIPS 186-5 and common HSM quorum configurations.
- ✗
Publish the firmware hashes to a public transparency log.
Why it's wrong here
A transparency log lets observers detect that a signature was issued and can help with after-the-fact auditing, but it does not prevent an attacker holding the private key from generating a signature that verifies on customers' devices. The forged update would still be accepted by the device's signature check. Logging improves detection and accountability, not the cryptographic guarantee that only authorized signers can produce valid signatures.
- ✗
Switch the signature algorithm from RSA to ECDSA with P-256.
Why it's wrong here
ECDSA with P-256 offers equivalent security to RSA-3072 with smaller keys and faster operations, but it still relies on a single private key. If that key is stolen, the attacker can sign arbitrary firmware exactly as before. Changing the algorithm family changes performance and key sizes, not the single-point-of-failure property that caused the incident.
Quick reference
Asymmetric Encryption Algorithm Comparison
| Algorithm | Key Exchange | Signatures | Equivalent Security Key | Notes |
|---|---|---|---|---|
| RSA-3072 | Yes | Yes | 128-bit | Widely deployed; slow for bulk data |
| ECDSA P-256 | No | Yes | 128-bit | Fast signatures; standard TLS certs |
| ECDH / ECDHE | Yes | No | 128-bit | Perfect forward secrecy in TLS 1.3 |
| DH / DHE | Yes | No | 128-bit (3072-bit key) | Replaced by ECDHE in modern TLS |
| Ed25519 | No | Yes | ~128-bit | SSH keys, modern PKI |
About these practice questions
Courseiva writes every GSEC question from scratch — 351 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official GIAC exam blueprint
This GSEC practice question is part of Courseiva's free GIAC certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GSEC exam.