CMMC Practice SI.1.212

Update malicious code protection mechanisms when new releases are available.


CMMC Version 1.02, pg. 280

Bold Coast Security Guidance

Configure your anti-malware software to check for updates at regular intervals, normally every hour, but at least daily. You must specify this interval in your policy, and you will repeat it in your plan, along with who is responsible for checking that the software is updating as expected. To measure its effectiveness, review the reports, also on a regular basis, to check that all workstations are updating in a timely manner. It is not uncommon for some anti-malware installations to get "stuck" from time to time due to a failed or interrupted update, but this could also be an indicator of compromise and must be resolved.

Discussion From Source

DRAFT NIST SP 800-171 R2 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.