03.14.09E Cryptographic Protection

Statement

Implement cryptographic mechanisms to detect unauthorized changes to software, firmware, and information.

Guidance

Cryptographic mechanisms used to protect integrity include digital signatures and the computation and application of signed hashes using asymmetric cryptography, protecting the confidentiality of the key used to generate the hash, and using the public key to verify the hash information. Organizations that use cryptographic mechanisms also consider cryptographic key management solutions. This requirement does not enhance a specific requirement in SP 800-171 but can be used to strengthen the protection of CUI associated with critical programs or high value assets.

Statement

• (includes preempt) Ensure that the threat event does not have an impact.

  • Reduce likelihood of occurrence and/or reduce likelihood of impact.

  • The adversary’s efforts or resources cannot be applied or are wasted.

• (includes exert) Make it more difficult for threat events to cause adverse impacts or consequences.

  • Reduce likelihood of impact and reduce level of impact.

  • Adversary activities are restricted in scope, fail to achieve full effect, do not take place in accordance with adversary timeline, or require greater resources than adversary had planned.

• (includes detect) Reduce risk due to ignorance of threat events and possible replicated or similar threat events in the same or similar environments.

  • Reduce likelihood of impact.

  • The adversary loses the advantage of stealth as defenders are better prepared by developing and sharing threat intelligence.

Assessment objective

cryptographic mechanisms are implemented to detect unauthorized changes to software.

Assessment objective

cryptographic mechanisms are implemented to detect unauthorized changes to firmware.

Assessment objective

cryptographic mechanisms are implemented to detect unauthorized changes to information.

Assessment method

• System and information integrity policy system and information integrity procedures procedures addressing software, firmware, and information integrity system design documentation system configuration settings and associated documentation system audit records system security plan cryptographic mechanisms and associated documentation records of detected unauthorized changes to software, firmware, and information other relevant documents or records

Assessment method

• Personnel responsible for software, firmware, and/or information integrity personnel with information security responsibilities system/network administrators system developers

Assessment method

• Software, firmware, and information integrity verification tools cryptographic mechanisms implementing software, firmware, and information integrity

1. Přehled

1.1 Odkazy

1.2 Identifikované požadavky

1.3 Související regulace

2. Identifikované požadavky

3. Související regulace

Propojené úkoly

• NIST -

  https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final