STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

V-221255

CAT II (Medium)

The Exchange software baseline copy must exist.

Rule ID

SV-221255r961461_rule

STIG

Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

Version

V2R6

CCIs

CCI-001813

Discussion

Exchange software, as with other application software installed on a host system, must be included in a system baseline record and periodically reviewed; otherwise, unauthorized changes to the software may not be discovered. This effort is a vital step to securing the host and the applications, as it is the only method that may provide the ability to detect and recover from otherwise undetected changes, such as those that result from worm or bot intrusions. The Exchange software and configuration baseline is created and maintained for comparison during scanning efforts. Operational procedures must include baseline updates as part of configuration management tasks that change the software and configuration.

Check Content

Review the Email Domain Security Plan (EDSP).

Determine the baseline documentation.  

Review the application software baseline procedures and implementation artifacts. 

Note the list of files and directories included in the baseline procedure for completeness. 

If an email software copy exists to serve as a baseline and is available for comparison during scanning efforts, this is not a finding.

Fix Text

Implement an email software baseline process and update the EDSP.