Quick Answer
The answer is improper key storage and weak random number generation. Improper key storage is a common weakness because if cryptographic keys are stored in plaintext, in world-readable files, or transmitted without encryption, an attacker can easily exfiltrate them and decrypt all protected data, rendering the strongest algorithm useless. Weak random number generation is equally critical, as cryptographic operations rely on unpredictability for keys, nonces, and initialization vectors; a flawed PRNG, such as a linear congruential generator, allows an attacker to predict or reproduce these values and break session security. On the SSCP exam, this question tests your understanding that cryptography fails not from broken algorithms but from poor implementation hygiene, often appearing in scenario-based items where a developer hardcodes a key or uses `Math.random()` for crypto. A common trap is assuming only algorithm strength matters, but the exam emphasizes that entropy and key management are foundational. Remember the mnemonic: “Keys and Randomness—if either is weak, the whole system leaks.”
This SSCP practice question tests your understanding of cryptography. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO of the following are common weaknesses in cryptographic implementations that an SSCP should be aware of? (Select exactly 2.)
Weak random number generation
Predictable random numbers can lead to key compromise.
Improper key storage
Keys stored insecurely can be stolen.
Frequent rekeying
Why wrong: Rekeying is a good practice.
Using proven encryption algorithms like AES
Why wrong: Using proven algorithms is a strength, not weakness.
Following NIST guidelines
Why wrong: Following guidelines is a strength.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Weak random number generation
Weak random number generation is a critical flaw because cryptographic keys, nonces, and initialization vectors rely on unpredictability. If an attacker can predict or reproduce the random values (e.g., due to a low-entropy source or a flawed PRNG like a linear congruential generator), they can derive secret keys or break session security. This undermines the entire cryptographic system regardless of the algorithm strength.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Weak random number generation
Why this is correct
Predictable random numbers can lead to key compromise.
Related concept
Read the scenario before looking for a memorised answer.
Improper key storage
Why this is correct
Keys stored insecurely can be stolen.
Related concept
Read the scenario before looking for a memorised answer.
Frequent rekeying
Why it's wrong here
Rekeying is a good practice.
Using proven encryption algorithms like AES
Why it's wrong here
Using proven algorithms is a strength, not weakness.
Following NIST guidelines
Why it's wrong here
Following guidelines is a strength.
Common exam traps
ISC2 often tests the misconception that 'using strong algorithms' or 'following standards' automatically guarantees security, when in fact implementation flaws like weak randomness or poor key management are the real vulnerabilities.
Detailed technical explanation
Cryptographic randomness often relies on hardware entropy sources (e.g., CPU RDRAND) or OS-provided CSPRNGs (e.g., /dev/urandom on Linux). A real-world example is the Debian OpenSSL vulnerability (CVE-2008-0166) where a flawed random number generator produced only 32,767 possible keys, making SSH and TLS keys trivially brute-forceable. This highlights that even strong algorithms like RSA or AES are useless if the key generation is predictable.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Cryptography — study guide chapter
Learn the concepts, then practise the questions
Cryptography practice questions
Targeted practice on this topic area only
All SSCP questions
504 questions across all exam domains
Systems Security Certified Practitioner SSCP study guide
Full concept coverage aligned to exam objectives
SSCP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SSCP questions linked to Risk Identification, Monitoring and Analysis.
Practise SSCP questions linked to Network and Communications Security.
Practise SSCP questions linked to Systems and Application Security.
Practise SSCP questions linked to Security Operations and Administration.
Practise SSCP questions linked to Incident Response and Recovery.
Practise SSCP questions linked to Access Controls.
Practise SSCP questions linked to Cryptography.
Practise SSCP questions linked to SSCP fundamentals.
Practise SSCP questions linked to SSCP scenario.
Practise SSCP questions linked to SSCP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Cryptography — This question tests Cryptography — Read the scenario before looking for a memorised answer..
The correct answer is: Weak random number generation — Weak random number generation is a critical flaw because cryptographic keys, nonces, and initialization vectors rely on unpredictability. If an attacker can predict or reproduce the random values (e.g., due to a low-entropy source or a flawed PRNG like a linear congruential generator), they can derive secret keys or break session security. This undermines the entire cryptographic system regardless of the algorithm strength.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 30, 2026
This SSCP practice question is part of Courseiva's free ISC2 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 SSCP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.