BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

3 FUNCTIONAL SECURITY OBJECTIVES

NIST platform security: roots of trust, firmware and secure enclaves FIPS 140-2
All changes in this version
first version loaded 3 FUNCTIONAL SECURITY OBJECTIVES

Title

FUNCTIONAL SECURITY OBJECTIVES

Control

The security requirements specified in this standard relate to the secure design and implementation of a cryptographic module. The requirements are derived from the following high-level functional security objectives for a cryptographic module:

To employ and correctly implement the Approved security functions for the protection of sensitive information.

• To protect a cryptographic module from unauthorized operation or use.

• To prevent the unauthorized disclosure of the contents of the cryptographic module, including plaintext cryptographic keys and CSPs.

• To prevent the unauthorized and undetected modification of the cryptographic module and cryptographic algorithms, including the unauthorized modification, substitution, insertion, and deletion of cryptographic keys and CSPs.

• To provide indications of the operational state of the cryptographic module.

• To ensure that the cryptographic module performs properly when operating in an Approved mode of operation.

• To detect errors in the operation of the cryptographic module and to prevent the compromise of sensitive data and CSPs resulting from these errors.