hardMultiple Select
SSCP Practice Question: Which TWO are security implications of using…
Which TWO are security implications of using deprecated cryptographic protocols such as SSL 3.0 and TLS 1.0?
⚠ Common exam trap
ISC2 often tests the misconception that deprecated protocols are 'still secure enough' or that their only downside is performance overhead, but the real trap is that candidates confuse 'interoperability issues' (which are a practical concern) with 'security implications' (which are the core focus of the question).
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
✓
Susceptibility to downgrade attacks
Option A is correct because deprecated protocols like SSL 3.0 and TLS 1.0 lack protections against version rollback, allowing an attacker to force a client and server to negotiate a weaker protocol or cipher suite—classic downgrade attacks such as POODLE against SSL 3.0. Option D is correct because these older protocols rely on weak key exchange mechanisms, including RSA key transport without forward secrecy and export-grade Diffie-Hellman parameters, which can expose session keys if long-term private keys are compromised. The remaining options do not describe security implications: increased computational overhead (B) is a performance concern, compliance with regulations (C) is a governance benefit rather than a risk, and interoperability issues with modern systems (E) is a compatibility problem, not a security vulnerability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Susceptibility to downgrade attacks
Why this is correct
SSL 3.0 and TLS 1.0 permit fallback negotiation to weaker cipher suites and protocol versions. An attacker can force a session down to the deprecated protocol, exploiting its known weaknesses. This downgrade susceptibility is the direct security implication of retaining these obsolete protocols.
- ✗
Increased computational overhead
Why it's wrong here
Deprecated protocols such as SSL 3.0 and TLS 1.0 are cryptographically weaker, not heavier; overhead is not the security concern. It is tempting because older ciphers can be slower, but the question asks about security implications, and these protocols expose known vulnerabilities instead.
- ✗
Compliance with regulations
Why it's wrong here
Regulatory compliance is a governance obligation, not a security implication of the protocol itself; deprecated protocols cause audit failures rather than new attacks. It is tempting because standards such as PCI DSS mandate TLS 1.2 or higher, but that is a compliance driver, not a technical security weakness.
- ✓
Weak key exchange
Why this is correct
SSL 3.0 and TLS 1.0 permit weak key-exchange mechanisms such as RSA without forward secrecy and export-grade Diffie-Hellman, letting an attacker who later obtains the server's private key decrypt previously captured sessions. This directly satisfies the stem's deprecated-protocol constraint, since later TLS versions mandate ephemeral key exchange.
- ✗
Interoperability issues with modern systems
Why it's wrong here
Interoperability is a functional consequence, not a security implication: modern peers refuse the handshake, breaking connectivity. It is tempting because deprecated protocols do cause connection failures, but the question asks how they weaken security, such as via known exploits like POODLE.
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 |
Go deeper
Related to this question
About these practice questions
Courseiva writes every SSCP question from scratch — 971 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.