NIST SP 800-171 & CMMC 2.0 Control 3.14.4 Requirement:

Update malicious code protection mechanisms when new releases are available.

NIST SP 800-171 & CMMC 2.0 3.14.4 Requirement Explanation:

Malware changes on an hourly or daily basis, and it is important to update detection and protection mechanisms frequently to maintain the effectiveness of the protection. In general, anti-malware software compares a file against a signature database to decide if the file is malicious. For anti-malware software to be effective the signature database must remain updated. If the signature database is outdated then it can not detect new malware.

Example NIST SP 800-171 & CMMC 2.0 3.14.4 Implementation:

Configure your anti-malware software to update its malware signature database. The updates should be periodic (e.g., every day at 8:00 AM) or automatic when a new update is availble.

NIST SP 800-171 & CMMC 2.0 3.14.4 Scenario(s):

- Scenario 1:

Alice set up the anti-malware software on her computers to update their signature databases hourly.
 

Discover Our NIST SP 800-171 & CMMC 2.0 Solutions:

 /assets/images/app/complaince_accelerator.gif

Compliance Accelerator

Power through compliance. Meet and maintain your NIST SP 800-171 & CMMC 2.0 compliance requirements.
 /assets/images/app/quantum_accelerator.gif

Quantum Assessor

Transform your business. Create new revenue streams and provide scalability for your NIST SP 800-171 and CMMC 2.0 services.
 /assets/images/app/supply_chain_verifier.gif

Supply Chain Verifier

Trust is everything. Verify, monitor, and support subcontactor compliance.