CMMC Practice SI.L1-3.14.4

Update malicious code protection mechanisms when new releases are available.

Monarch ISC 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.

Security Catapult

Be prepared for CMMC

Our Q&A assessment tool is designed by security advisors for MSPs and DoD contractors of all sizes.

Try now for free

Security Catapult

Understand your gaps

See compliance gaps, compliance scores and proactive security tasks in a single interface.

Try now for free

Security Catapult

Validate NIST SP 800-171

Based on your CMMC answers, we let you know where you stand on NIST.

Try now for free

Security Catapult

Build a plan of action

Track your burn down and stay on top of security needs.

Try now for free

Security Catapult

Build your policy

Say goodbye to maintaining a security policy. We do it for you.

Try now for free

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.