View source for Practice SI.L1-3.14.4 Details

'''Source of Reference: The official [https://www.acq.osd.mil/cmmc/documentation.html CMMC Level 1 Self-Assessment Guide] from the Office of the Under Secretary of Defense Acquisition & Sustainment.'''

For inquiries and reporting errors on this wiki, please [mailto:support@cmmctoolkit.org contact us]. Thank you.

== SI.L1-3.14.4 – UPDATE MALICIOUS CODE PROTECTION ==
=== SECURITY REQUIREMENT ===
Update malicious code protection mechanisms when new releases are available.
=== ASSESSMENT OBJECTIVES ===
Determine if:
: [a] malicious code protection mechanisms are updated when new releases are available.
=== POTENTIAL ASSESSMENT METHODS AND OBJECTS ===
'''Examine'''

[SELECT FROM: System and information integrity policy; configuration management policy and procedures; procedures addressing malicious code protection; malicious code protection mechanisms; records of malicious code protection updates; system security plan;system design documentation; system configuration settings and associated documentation;scan results from malicious code protection mechanisms; record of actions initiated by malicious code protection mechanisms in response to malicious code detection; system audit logs and records; other relevant documents or records].

'''Interview'''

[SELECT FROM: System or network administrators; personnel with information security responsibilities; personnel installing, configuring, and maintaining the system; personnel with responsibility for malicious code protection; personnel with configuration management responsibility].

'''Test'''

[SELECT  FROM:  Organizational  processes  for  employing,  updating,  and  configuring malicious code protection mechanisms; organizational process for addressing false positives and resulting potential impact; mechanisms supporting or implementing malicious code protection mechanisms (including updates and configurations); mechanisms supporting or implementing malicious code scanning and subsequent actions].
=== 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.
=== FURTHER DISCUSSION ===
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.

'''Example'''

You have installed anti-malware software to protect a computer from malicious code.Knowing that malware evolves rapidly, you configure the software to automatically check for malware definition updates every day and update as needed [a].

'''Potential Assessment Considerations'''
* Is there a defined frequency by which malicious code protection mechanisms must be updated (e.g., frequency of automatic updates or manual processes) [a]?
=== KEY REFERENCES ===
* FAR Clause 52.204-21 b.1.xiv
* NIST SP 800-171 Rev 2 3.14.4