CISSP-ISSEP · Question #167
Which of the following types of cryptography defined by FIPS 185 describes a cryptographic algorithm or a tool accepted as a Federal Information Processing Standard?
The correct answer is B. Type III cryptography. Type III cryptography, as defined under FIPS 185, specifically refers to a cryptographic algorithm or tool that has been accepted and published as a Federal Information Processing Standard - meaning it has gone through the formal NIST review and approval process for government us
Question
Which of the following types of cryptography defined by FIPS 185 describes a cryptographic algorithm or a tool accepted as a Federal Information Processing Standard?
Options
- AType III (E) cryptography
- BType III cryptography
- CType I cryptography
- DType II cryptography
How the community answered
(39 responses)- B92% (36)
- C3% (1)
- D5% (2)
Explanation
Type III cryptography, as defined under FIPS 185, specifically refers to a cryptographic algorithm or tool that has been accepted and published as a Federal Information Processing Standard - meaning it has gone through the formal NIST review and approval process for government use. Type I cryptography is incorrect because it refers to NSA-approved classified algorithms used to protect classified national security information. Type II cryptography is incorrect because it covers unclassified NSA-approved algorithms intended for sensitive but unclassified government data. Type III (E) cryptography (option A) is a distractor that specifically denotes the escrowed encryption subset of Type III - algorithms that include key escrow capabilities (like the Skipjack algorithm under the Clipper Chip initiative) - making it a narrower category than Type III itself.
Memory tip: Think of the "F" in FIPS matching "III" - three letters, three syllables - Fed-er-al. Type III = FIPS-approved. Type I = classified (one step above), Type II = unclassified-sensitive (in between), and the "(E)" suffix always means escrowed.
Topics
Community Discussion
No community discussion yet for this question.