Under active development Content is continuously updated and improved

3.14.4System and Information Integrity - Derived

Derived Requirement

>Control Description

Update malicious code protection mechanisms when new releases are available.

>Discussion

Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code.

In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code.

In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended.

>Cross-Framework Mappings

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

  • What policies govern replay-resistant authentication mechanisms?
  • What procedures ensure authentication cannot be replayed?
  • Who approves authentication technologies and standards?
  • What governance prevents replay attacks on authentication?
  • What training addresses replay attack risks?

Technical Implementation:

  • What authentication mechanisms prevent replay attacks?
  • How do you implement nonces, timestamps, or challenge-response?
  • What protocols provide replay resistance (Kerberos, TLS, etc.)?
  • How do you detect and block replay attack attempts?
  • What monitoring identifies potential replay attacks?

Evidence & Documentation:

  • Can you show authentication protocols with replay resistance?
  • What configurations implement replay-resistant mechanisms?
  • Can you provide testing results proving replay protection?
  • What evidence demonstrates replay attack prevention?
  • What audit findings verify replay-resistant authentication?

Ask AI

Configure your API key to use AI features.