Courseiva
hardMultiple Select

Insecure and Deprecated Cryptographic Algorithms for SSCP

A security auditor is reviewing the cryptographic algorithms used in an organization. Which THREE of the following are considered insecure or deprecated and should be avoided? (Select THREE.)

Quick Answer

The answer is MD5, DES, and 3DES, as these three are the insecure deprecated cryptographic algorithms that should be avoided. MD5 is broken due to practical collision attacks achievable in seconds on commodity hardware, while DES uses a dangerously short 56-bit key that cannot withstand modern brute-force attempts, and 3DES, though an improvement, is now deprecated by NIST due to slow performance and susceptibility to meet-in-the-middle attacks. On the Systems Security Certified Practitioner SSCP exam, this question tests your ability to identify outdated ciphers and hash functions that violate current security baselines—a common trap is confusing 3DES as still acceptable because it was once a standard, but remember NIST disallowed it for new applications after 2023. A useful memory tip: think “D3M” for Deprecated, DES, 3DES, and MD5—all three are dead ends for secure cryptography.

⚠ Common exam trap

ISC2 often tests the misconception that 3DES is still acceptable because it is 'triple' strength, but the trap is that both DES and 3DES are deprecated due to small block sizes and key lengths, while MD5 is often mistakenly considered safe for checksums despite its proven collision vulnerabilities.

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

✓

DES

DES (B) is insecure because its 56-bit key is far too short and can be brute-forced in hours with modern hardware, so it must be avoided. 3DES (C) is deprecated because its 64-bit block size enables Sweet32-style birthday attacks and its effective key strength is reduced, making it unsuitable for new deployments. MD5 (E) is a broken hash function with practical collision attacks, so it must not be used for integrity or signature purposes. RSA-2048 (A) and AES-256 (D) are not marked correct because they remain strong, currently recommended algorithms when implemented properly.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    RSA-2048

    Why it's wrong here

    RSA-2048 is still acceptable under NIST guidance and provides adequate security for current use, so it does not meet the deprecated criterion. Its age and eventual quantum vulnerability make it tempting to flag, but the question targets genuinely broken algorithms like MD5, SHA-1, DES or RC4.

  • ✓

    DES

    Why this is correct

    DES uses a 56-bit effective key, making exhaustive key search feasible with modern hardware. Its small block size of 64 bits also permits birthday-bound collisions. Both weaknesses make it unsuitable for protecting sensitive data, so auditors should flag it as deprecated.

  • ✓

    3DES

    Why this is correct

    3DES applies DES three times but retains a 64-bit block, so birthday attacks (Sweet32) can recover plaintext in long sessions. Its effective key strength is also reduced by known weaknesses. NIST has deprecated it, making it unsuitable for new deployments.

  • ✗

    AES-256

    Why it's wrong here

    AES-256 remains a current, NIST-approved symmetric cipher with no practical cryptanalytic weakness, so it fails the 'insecure or deprecated' criterion. Its 256-bit key length makes it tempting to flag as excessive or legacy, but the question targets broken algorithms such as MD5, SHA-1 or DES, not strong AES variants.

  • ✓

    MD5

    Why this is correct

    MD5 produces a 128-bit hash with collision resistance thoroughly broken; chosen-prefix collisions are practical. It cannot support integrity or signature assurances, so auditors should flag it as deprecated for any security use, including certificate and password contexts.

Quick reference

Symmetric Encryption Algorithm Comparison

AlgorithmKey SizeBlock SizeStatusNotes
AES-128128-bit128-bitCurrent standardNIST approved; WPA3, TLS
AES-256256-bit128-bitCurrent standardPreferred for sensitive / govt data
3DES112-bit effective64-bitDeprecated (2023)Replaced by AES
DES56-bit64-bitBrokenCracked in < 24 h; never deploy
ChaCha20256-bitStream cipherCurrentTLS 1.3, WireGuard

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on SSCP

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Which TWO of the following cryptographic algorithms are considered secure for modern use?

medium
  • A.MD5 (Message Digest 5)
  • ✓ B.ChaCha20
  • ✓ C.AES-256 (Advanced Encryption Standard with 256-bit key)
  • D.RC4 (Rivest Cipher 4)
  • E.DES (Data Encryption Standard)

Why B: ChaCha20 (B) is a modern stream cipher designed by Daniel J. Bernstein that remains secure and is widely deployed in TLS 1.3, WireGuard, and OpenSSH, offering strong resistance to cryptanalysis with no practical attacks against its full 20-round design. AES-256 (C) is a symmetric block cipher standardized by NIST that, with its 256-bit key, provides a very high security margin and is approved for protecting classified information up to Top Secret. In contrast, MD5 (A) is a hash function broken by practical collision attacks since 2004 and is unsuitable for security purposes. RC4 (D) is a stream cipher with well-known biases in its keystream (e.g., the RC4 biases exploited in WEP and TLS attacks) and has been prohibited in TLS by RFC 7465. DES (E) uses only a 56-bit effective key and is trivially brute-forced with modern hardware, so it is obsolete.

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.