to move, Enter to open, Esc to close. Try 3.5.3, AC.L2-3.1.1, MFA or unmarked.

3.14.5Scan on schedule and in real time

Periodic full scans plus real-time scanning of files as they arrive.

The requirement, verbatim

NIST SP 800-171 Rev. 2 · 3.14.5

Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.

Requirement 3.14.5, practice name in the CMMC assessment guide: System & File Scanning.

NIST's discussion

Periodic scans of organizational systems and real-time scans of files from external sources can detect malicious code. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities.

NIST SP 800-171 Rev. 2, discussion under 3.14.5. Whitespace normalised; wording unchanged.

Assessment objectives

An assessor decides each of these separately. The requirement is met only when every objective is.

  1. [a] periodic scans of the system are performed
  2. [b] real-time scans of files from external sources as files are downloaded, opened, or executed are performed

NIST SP 800-171A, determination statements for 3.14.5.

For assessors: examine, interview, test

NIST SP 800-171A names what an assessor may examine, whom they may interview, and what they may test for this requirement. Assessors select from these lists; they are not a checklist of everything you must produce.

Examine
  • 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
  • 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
  • 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

NIST SP 800-171A, potential assessment methods and objects for 3.14.5.

Evidence

No evidence examples are published for this requirement yet. The objectives above are what an assessor checks; evidence is whatever shows each one is true in your environment, dated and kept with your system security plan.

Scoring weight

Worth 3 points. Not meeting this requirement subtracts 3 from your 110-point SPRS score.

DoD NIST SP 800-171 Assessment Methodology v1.2.1 weighting, as carried in the Bedrock scoring table. The score starts at 110 and subtracts the weight of every requirement not met.

In Rev. 3

Rev. 2 is what your contract requires today. A standing DoD class deviation keeps Rev. 2 in force; NIST has published Rev. 3, but it is not adopted for contracts. In Rev. 3 this requirement is withdrawn and incorporated elsewhere: 03.14.02 Malicious Code Protection.

See the Rev. 2 and Rev. 3 wording word by word, or start with the status page.

Where this page's facts come from
Requirement text
bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.basicRequirement@rev2
Discussion
bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.discussion@rev2
Practice name
bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.title@rev2 (CMMC Assessment Guide practice name)
Objectives
bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2
Examine, interview, test
bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2 ({examineGuidance, interviewGuidance, testGuidance})
Level
bedrock-cmmc-api@89b8e8e:migrations/021_fix_level1_requirements.sql#Requirement.cmmcLevel@rev2
Weight
bedrock-cmmc-api@89b8e8e:internal/cmmc/requirement_values.go#requirementValues (DoD AM v1.2.1 / eMASS L2 template v3.8)
Rev. 3 mapping
bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/r2_r3_transition_map.json#r2_to_r3
Plain-language title and summary
editorial/CMMC Navigator.dc.html#RAW (Foxx Cyber editorial)