STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Microsoft Exchange 2019 Edge Server Security Technical Implementation Guide

V-259591

CAT II (Medium)

Exchange Send Fatal Errors to Microsoft must be disabled.

Rule ID

SV-259591r960963_rule

STIG

Microsoft Exchange 2019 Edge Server Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-000381

Discussion

It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. Applications are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Examples of nonessential capabilities include, but are not limited to, advertising software or browser plug-ins not related to requirements or providing a wide array of functionality not required for every mission, but cannot be disabled. Customer Experience reports in Exchange will result in outbound traffic that may be identified by an eavesdropper. For this reason, the Customer Experience reports to Microsoft must not be sent.

Check Content

Open the Exchange Management Shell and enter the following command:

Get-ExchangeServer –status | Select-Object -Property Name, Identity, ErrorReportingEnabled

For each exchange server, if the value of "ErrorReportingEnabled" is not set to "False", this is a finding.

Fix Text

Open the Exchange Management Shell and enter the following command:

Set-ExchangeServer -Identity <'IdentityName'> -ErrorReportingEnabled $false

Note: The <IdentityName> value must be in quotes.

Repeat the procedure for each identity.