OpenControls Logo

STIG Viewer

STIGViewer Support

Windows Server 2019 system files must be monitored for unauthorized changes.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-205803WN19-00-000220SV-205803r958794_ruleCCI-001744medium
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.
STIGDate
Microsoft Windows Server 2019 Security Technical Implementation Guide2026-02-12

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CHG-02.4Automated Security Response
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (9) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AU-12Audit Record Generation
1.00
AU-3Content of Audit Records
1.00
AU-3(1)Additional Audit Information
1.00
AU-5(2)Real-time Alerts
1.00
AU-8Time Stamps
1.00
CM-3(5)Automated Security Response
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00
SI-11Error Handling
1.00
SI-6Security and Privacy Function Verification
1.00
CCI1 mapping
CCI-001744
1.00

Details

Check Text (C-205803r958794_chk)

Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. If system files are not monitored for unauthorized changes, this is a finding. 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.

Fix Text (F-6068r355772_fix)

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