System files must be monitored for unauthorized changes.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-226248	WN12-GE-000017	SV-226248r894352_rule		Medium

Description
Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system.

STIG	Date
Microsoft Windows Server 2012/2012 R2 Domain Controller Security Technical Implementation Guide	2023-02-27

Details

Check Text ( C-27950r894349_chk )
Determine whether the site monitors system files (e.g., .exe, .bat, .com, .cmd, and *.dll) on servers for unauthorized changes against a baseline on a weekly basis. An approved and properly configured solution will contain both a list of baselines that includes all system file locations and a file comparison task that is scheduled to run at least weekly. If system files are not being monitored for unauthorized changes, this is a finding.

Check Text ( C-27950r894349_chk )

Determine whether the site monitors system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) on servers for unauthorized changes against a baseline on a weekly basis.

An approved and properly configured solution will contain both a list of baselines that includes all system file locations and a file comparison task that is scheduled to run at least weekly.

If system files are not being monitored for unauthorized changes, this is a finding.

Fix Text (F-27938r890476_fix)
Monitor system files (e.g., .exe, .bat, .com, .cmd, and *.dll) on servers for unauthorized changes against a baseline on a weekly basis. This can be done with the use of various monitoring tools.