Queue monitoring must be configured with threshold and action.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-33619	Exch-2-842	SV-44039r2_rule	ECSC-1	Medium

Description
Monitors are automated 'process watchers' that respond to performance changes, and can be useful in detecting outages and alerting administrators where attention is needed. Exchange has built-in monitors that enable the administrator to generate alerts if thresholds are reached, better enabling them to react in a timely fashion. This field offers choices of alerts when a 'warning' or 'critical' threshold is reached on the SMTP queue. A good rule of thumb (default) is to issue warnings when SMTP queue growth exceeds 10 minutes and critical messages when it exceeds 20 minutes, which should only exist occasionally. Frequent alerts against this counter may indicate a network or other issue (such as inbound SPAMMER traffic) that directly impacts email delivery. Notification choices include email alert to an email enabled account, for example, an email Administrator, or invoke a script to take other action, for example, to add an Event to the Microsoft Application Event Log, where external monitors might detect it.

Description

Monitors are automated 'process watchers' that respond to performance changes, and can be useful in detecting outages and alerting administrators where attention is needed. Exchange has built-in monitors that enable the administrator to generate alerts if thresholds are reached, better enabling them to react in a timely fashion. This field offers choices of alerts when a 'warning' or 'critical' threshold is reached on the SMTP queue. A good rule of thumb (default) is to issue warnings when SMTP queue growth exceeds 10 minutes and critical messages when it exceeds 20 minutes, which should only exist occasionally. Frequent alerts against this counter may indicate a network or other issue (such as inbound SPAMMER traffic) that directly impacts email delivery. Notification choices include email alert to an email enabled account, for example, an email Administrator, or invoke a script to take other action, for example, to add an Event to the Microsoft Application Event Log, where external monitors might detect it.

STIG	Date
Exchange 2010 Client Access Server STIG	2015-12-02

Details

Check Text ( C-41726r8_chk )
Note: If a third party application is performing monitoring functions, the reviewer should verify the application is monitoring correctly and mark the vulnerability NA. Open the Exchange Management Shell and enter the following command: perfmon In the left pane, expand and navigate Data Collector Sets --> User Defined If no sets are defined or queues are not being monitored, this is a finding.

Check Text ( C-41726r8_chk )

Note: If a third party application is performing monitoring functions, the reviewer should verify the application is monitoring correctly and mark the vulnerability NA.

Open the Exchange Management Shell and enter the following command:

perfmon

In the left pane, expand and navigate Data Collector Sets --> User Defined

If no sets are defined or queues are not being monitored, this is a finding.

Fix Text (F-37511r5_fix)
Open the Exchange Management Console In the left pane, navigate to and select Microsoft Exchange On-Premises --> Toolbox In the Right pane double click on Performance Monitor In the left pane, navigate to and select Performance Logs and Alerts --> Data Collector Sets --> User Defined Right click on User Defined and configure the system to use User Defined data collection for monitoring the queues.

Fix Text (F-37511r5_fix)

Open the Exchange Management Console

In the left pane, navigate to and select Microsoft Exchange On-Premises --> Toolbox

In the Right pane double click on Performance Monitor

In the left pane, navigate to and select Performance Logs and Alerts --> Data Collector Sets --> User Defined

Right click on User Defined and configure the system to use User Defined data collection for monitoring the queues.