| Finding ID |
Severity |
Title |
Description |
|
V-228397
|
High |
Exchange servers must have an approved DoD email-aware virus protection software installed. |
With the proliferation of trojans, viruses, and spam attaching themselves to email messages (or attachments), it is necessary to have capable email-aware anti-virus (AV) products to scan messages and identify any resident malware. Because email messages and their attachments are formatted to the MIME standard, a flat-file AV scanning engine... |
|
V-228418
|
Medium |
Exchange must have authenticated access set to Integrated Windows Authentication only. |
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., networks, web servers, and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate... |
|
V-228417
|
Medium |
Exchange must have forms-based authentication disabled. |
Identification and Authentication provide the foundation for access control. Access to email services applications in the DoD requires authentication using DoD Public Key Infrastructure (PKI) certificates. Authentication for Outlook Web App (OWA) is used to enable web access to user email mailboxes and should assume that certificate-based authentication has been... |
|
V-228416
|
Medium |
Exchange must use encryption for Outlook Web App (OWA) access. |
This setting controls whether client machines should be forced to use secure channels to communicate with this virtual directory. If this feature is enabled, clients will only be able to communicate with the directory if they are capable of supporting secure communication with the server.
The use of secure communication... |
|
V-228415
|
Medium |
Exchange must use encryption for RPC client access. |
This setting controls whether client machines are forced to use secure channels to communicate with the server. If this feature is enabled, clients will only be able to communicate with the server over secure communication channels.
Failure to require secure connections to the client access server increases the potential for... |
|
V-228413
|
Medium |
The applications built-in Malware Agent must be disabled. |
Malicious code protection mechanisms include but are not limited to anti-virus and malware detection software. To minimize potential negative impact to the organization that can be caused by malicious code, it is imperative that malicious code is identified and eradicated.
Malicious code includes viruses, worms, trojan horses, and spyware. It... |
|
V-228412
|
Medium |
The application must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
Configuring the application to implement organization-wide security implementation guides and security checklists ensures compliance with Federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed that affect the... |
|
V-228411
|
Medium |
Exchange must have the most current, approved service pack installed. |
Failure to install the most current Exchange service pack leaves a system vulnerable to exploitation. Current service packs correct known security and system vulnerabilities. |
|
V-228410
|
Medium |
Exchange must provide Mailbox databases in a highly available and redundant configuration. |
Exchange Server mailbox databases and any data contained in those mailboxes should be protected. This can be accomplished by configuring Mailbox servers and databases for high availability and site resilience.
A database availability group (DAG) is a component of the Mailbox server high availability and site resilience framework built into... |
|
V-228409
|
Medium |
Exchange Internal Send connectors must use an authentication level. |
The Simple Mail Transfer Protocol (SMTP) connector is used by Exchange to send and receive messages from server to server. Several controls work together to provide security between internal servers. This setting controls the encryption method used for communications between servers. With this feature enabled, only servers capable of supporting... |
|
V-228408
|
Medium |
The Exchange SMTP automated banner response must not reveal server details. |
Automated connection responses occur as a result of FTP or Telnet connections when connecting to those services. They report a successful connection by greeting the connecting client and stating the name, release level, and (often) additional information regarding the responding product. While useful to the connecting client, connection responses can... |
|
V-228407
|
Medium |
Exchange must not send nondelivery reports to remote domains. |
Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Ensure that nondelivery reports to remote domains are disabled. Before enabling this setting, first configure a remote domain using the... |
|
V-228406
|
Medium |
Exchange must not send delivery reports to remote domains. |
Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Ensure that delivery reports to remote domains are disabled. Before enabling this setting, first configure a remote domain using the... |
|
V-228405
|
Medium |
The Exchange Email application must not share a partition with another application. |
In the same way that added security layers can provide a cumulative positive effect on security posture, multiple applications can provide a cumulative negative effect. A vulnerability and subsequent exploit to one application can lead to an exploit of other applications sharing the same security context. For example, an exploit... |
|
V-228404
|
Medium |
Exchange Outlook Anywhere clients must use NTLM authentication to access email. |
Identification and authentication provide the foundation for access control. Access to email services applications require NTLM authentication. Outlook Anywhere, if authorized for use by the site, must use NTLM authentication when accessing email.
Note: There is a technical restriction in Exchange Outlook Anywhere that requires a direct SSL connection from... |
|
V-228403
|
Medium |
Exchange services must be documented and unnecessary services must be removed or disabled. |
Unneeded but running services offer attackers an enhanced attack profile, and attackers are constantly watching to discover open ports with running services. By analyzing and disabling unneeded services, the associated open ports become unresponsive to outside queries, and servers become more secure as a result.
Exchange Server has role-based server... |
|
V-228402
|
Medium |
Exchange software must be monitored for unauthorized changes. |
Monitoring software files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system. |
|
V-228401
|
Medium |
An Exchange software baseline copy must exist. |
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... |
|
V-228400
|
Medium |
The Exchange application directory must be protected from unauthorized access. |
Default product installations may provide more generous access permissions than are necessary to run the application. By examining and tailoring access permissions to more closely provide the least amount of privilege possible, attack vectors that align with user permissions are less likely to access more highly secured areas. |
|
V-228396
|
Medium |
Exchange must not send automated replies to remote domains. |
Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Remote users will not receive automated "Out of Office" delivery reports. This setting can be used to determine if all... |
|
V-228395
|
Medium |
Exchange must have anti-spam filtering configured. |
Originators of spam messages are constantly changing their techniques in order to defeat spam countermeasures; therefore, spam software must be constantly updated to address the changing threat. A manual update procedure is labor intensive and does not scale well in an enterprise environment. This risk may be mitigated by using... |
|
V-228394
|
Medium |
Exchange must have anti-spam filtering enabled. |
Originators of spam messages are constantly changing their techniques in order to defeat spam countermeasures; therefore, spam software must be constantly updated to address the changing threat. A manual update procedure is labor intensive and does not scale well in an enterprise environment. This risk may be mitigated by using... |
|
V-228393
|
Medium |
Exchange must have anti-spam filtering installed. |
Originators of spam messages are constantly changing their techniques in order to defeat spam countermeasures; therefore, spam software must be constantly updated to address the changing threat. A manual update procedure is labor intensive and does not scale well in an enterprise environment. This risk may be mitigated by using... |
|
V-228392
|
Medium |
Exchange external/Internet-bound automated response messages must be disabled. |
Spam originators, in an effort to refine mailing lists, sometimes monitor transmissions for automated bounce-back messages. Automated messages include such items as "Out of Office" responses, nondelivery messages, and automated message forwarding.
Automated bounce-back messages can be used by a third party to determine if users exist on the server.... |
|
V-228391
|
Medium |
Exchange Internal Receive connectors must not allow anonymous connections. |
This control is used to limit the servers that may use this server as a relay. If a Simple Mail Transport Protocol (SMTP) sender does not have a direct connection to the Internet (for example, an application that produces reports to be emailed), it will need to use an SMTP... |
|
V-228378
|
Medium |
Exchange email-forwarding SMTP domains must be restricted. |
Auto-forwarded email accounts do not meet the requirement for digital signature and encryption of Controlled Unclassified Information (CUI) and Personally Identifiable Information (PII) in accordance with DoDI 8520.2 (reference ee) and DoD Director for Administration and Management memorandum, "Safeguarding Against and Responding to the Breach of Personally Identifiable Information".
Use... |
|
V-228377
|
Medium |
Exchange email forwarding must be restricted. |
Auto-forwarded email accounts do not meet the requirement for digital signature and encryption of Controlled Unclassified Information (CUI) and Personally Identifiable Information (PII) in accordance with DoDI 8520.2 (reference ee) and DoD Director for Administration and Management memorandum, "Safeguarding Against and Responding to the Breach of Personally Identifiable Information".
Use... |
|
V-228376
|
Medium |
Exchange Mailboxes must be retained until backups are complete. |
Backup and recovery procedures are an important part of overall system availability and integrity. Complete backups reduce the chance of accidental deletion of important information and make it possible to have complete recoveries.
It is not uncommon for users to receive and delete messages in the scope of a single... |
|
V-228375
|
Medium |
Exchange internal Receive connectors must require encryption. |
The Simple Mail Transfer Protocol (SMTP) Receive connector is used by Exchange to send and receive messages from server to server using SMTP protocol. This setting controls the encryption strength used for client connections to the SMTP Receive connector. With this feature enabled, only clients capable of supporting secure communications... |
|
V-228374
|
Medium |
Exchange Internet-facing Send connectors must specify a Smart Host. |
When identifying a "Smart Host" for the email environment, a logical Send connector is the preferred method.
A Smart Host acts as an Internet-facing concentrator for other email servers. Appropriate hardening can be applied to the Smart Host, rather than at multiple locations throughout the enterprise.
Failure to identify a... |
|
V-228373
|
Medium |
Exchange Mailbox databases must reside on a dedicated partition. |
In the same way that added security layers can provide a cumulative positive effect on security posture, multiple applications can provide a cumulative negative effect. A vulnerability and subsequent exploit to one application can lead to an exploit of other applications sharing the same security context. For example, an exploit... |
|
V-228372
|
Medium |
The Exchange Post Office Protocol 3 (POP3) service must be disabled. |
POP3 is not approved for use within the DoD. It uses a clear-text-based user name and password and does not support the DoD standard for PKI for email access. User name and password could easily be captured from the network, allowing a malicious user to access other system features. Uninstalling... |
|
V-228371
|
Medium |
The Exchange Internet Message Access Protocol 4 (IMAP4) service must be disabled. |
IMAP4 is not approved for use within the DoD. It uses a clear-text-based user name and password and does not support the DoD standard for PKI for email access. User name and password could easily be captured from the network, allowing a malicious user to access other system features. Uninstalling... |
|
V-228370
|
Medium |
Exchange Local machine policy must require signed scripts. |
Scripts often provide a way for attackers to infiltrate a system, especially scripts downloaded from untrusted locations. By setting machine policy to prevent unauthorized script executions, unanticipated system impacts can be avoided. Failure to allow only signed remote scripts reduces the attack vector vulnerabilities from unsigned remote scripts. |
|
V-228369
|
Medium |
Exchange Audit data must be on separate partitions. |
Log files help establish a history of activities and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Audit log content must always be considered sensitive and in need of protection.
Successful exploit of an application server vulnerability may well be logged by monitoring or... |
|
V-228368
|
Medium |
Exchange must protect audit data against unauthorized deletion. |
Log files help establish a history of activities and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Audit log content must always be considered sensitive and in need of protection. Audit data available for modification by a malicious user can be altered to conceal... |
|
V-228367
|
Medium |
Exchange must protect audit data against unauthorized access. |
Log files help establish a history of activities and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Audit log content must always be considered sensitive and in need of protection. Audit data available for modification by a malicious user can be altered to conceal... |
|
V-228366
|
Medium |
Exchange must not send Customer Experience reports to Microsoft. |
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... |
|
V-228365
|
Medium |
Exchange must protect audit data against unauthorized read access. |
Log files help establish a history of activities and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Audit log content must always be considered sensitive and in need of protection. Audit data available for modification by a malicious user can be altered to conceal... |
|
V-228364
|
Medium |
Exchange Send Fatal Errors to Microsoft must be disabled. |
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... |
|
V-228363
|
Medium |
Exchange Queue monitoring must be configured with threshold and action. |
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... |
|
V-228362
|
Medium |
Exchange Message Tracking Logging must be enabled. |
A message tracking log provides a detailed log of all message activity as messages are transferred to and from a computer running Exchange.
If events are not recorded, it may be difficult or impossible to determine the root cause of system problems or the unauthorized activities of malicious users. |
|
V-228361
|
Medium |
Exchange Email Subject Line logging must be disabled. |
Log files help establish a history of activities and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. When "message tracking" is enabled, only the sender, recipients, time, and other delivery information is included by default. Information such as the subject and message body is... |
|
V-228358
|
Medium |
The Exchange Email Diagnostic log level must be set to the lowest level. |
Log files help establish a history of activities and can be useful in detecting attack attempts or determining tuning adjustments to improve availability. Diagnostic logging, however, characteristically produces large volumes of data and requires care in managing the logs to prevent risk of disk capacity denial-of-service conditions.
Exchange diagnostic logging... |
|
V-228357
|
Medium |
Exchange Connectivity logging must be enabled. |
A connectivity log is a record of the SMTP connection activity of the outbound message delivery queues to the destination Mailbox server, smart host, or domain. Connectivity logging is available on Hub Transport servers and Edge Transport servers. By default, connectivity logging is disabled. If events are not recorded, it... |
|
V-228356
|
Medium |
Exchange auto-forwarding email to remote domains must be disabled or restricted. |
Attackers can use automated messages to determine whether a user account is active, in the office, traveling, and so on. An attacker might use this information to conduct future attacks. Verify Automatic Forwards to remote domains are disabled, except for enterprise mail that must be restricted to forward only to... |
|
V-228355
|
Medium |
Exchange servers must use approved DoD certificates. |
Server certificates are required for many security features in Exchange; without them, the server cannot engage in many forms of secure communication.
Failure to implement valid certificates makes it virtually impossible to secure Exchange's communications. |
|
V-228354
|
Medium |
Exchange must have Administrator audit logging enabled. |
Unauthorized or malicious data changes can compromise the integrity and usefulness of the data. Automated attacks or malicious users with elevated privileges have the ability to effect change using the same mechanisms as email administrators.
Auditing any changes to access mechanisms not only supports accountability and nonrepudiation for those authorized... |
|
V-228399
|
Low |
The Exchange Receive connector timeout must be limited. |
Email system availability depends in part on best practice strategies for setting tuning. This configuration controls the number of idle minutes before the connection is dropped. It works in conjunction with the Maximum Inbound Connections Count setting.
Connections, once established, may incur delays in message transfer. If the timeout period... |
|
V-228398
|
Low |
The Exchange Global Recipient Count Limit must be set. |
Email system availability depends in part on best practice strategies for setting tuning configurations. The Global Recipient Count Limit field is used to control the maximum number of recipients that can be specified in a single message sent from this server. Its primary purpose is to minimize the chance of... |
|
V-228390
|
Low |
The Exchange Outbound Connection Timeout must be 10 minutes or less. |
Email system availability depends in part on best practice strategies for setting tuning configurations. This configuration controls the number of idle minutes before the connection is dropped. It works in conjunction with the Maximum Outbound Connections Count setting.
Connections, once established, may incur delays in message transfer. The default of... |
|
V-228389
|
Low |
The Exchange Outbound Connection Limit per Domain Count must be controlled. |
Email system availability depends in part on best practice strategies for setting tuning configurations. This configuration controls the maximum number of simultaneous outbound connections from a domain as a delivery tuning mechanism. If the limit is too low, connections may be dropped. If the limit is too high, some domains... |
|
V-228388
|
Low |
The Exchange global outbound message size must be controlled. |
Email system availability depends in part on best practice strategies for setting tuning configurations. Message size limits should be set to 10 megabytes (MB) at most but often are smaller, depending on the organization. The key point in message size is that it should be set globally and should not... |
|
V-228387
|
Low |
The Exchange global inbound message size must be controlled. |
Email system availability depends in part on best practice strategies for setting tuning configurations. Message size limits should be set to 10 megabytes (MB) at most but often are smaller, depending on the organization. The key point in message size is that it should be set globally and should not... |
|
V-228386
|
Low |
The Exchange Send connector connections count must be limited. |
The Exchange Send connector setting controls the maximum number of simultaneous outbound connections allowed for a given SMTP connector and can be used to throttle the SMTP service if resource constraints warrant it. If the limit is too low, connections may be dropped. If the limit is too high, some... |
|
V-228385
|
Low |
Exchange Message size restrictions must be controlled on Send connectors. |
Email system availability depends in part on best practice strategies for setting tuning configurations. For message size restrictions, multiple places exist to set or override inbound or outbound message size. Failure to control the configuration strategy can result in loss of data or system availability.
This setting enables the administrator... |
|
V-228384
|
Low |
The Exchange Receive Connector Maximum Hop Count must be 60. |
Email system availability depends in part on best practice strategies for setting tuning configurations. This setting controls the maximum number of hops (email servers traversed) a message may take as it travels to its destination. Part of the original Internet protocol implementation, the hop count limit prevents a message being... |
|
V-228383
|
Low |
Exchange Receive connectors must control the number of recipients per message. |
Email system availability depends in part on best practice strategies for setting tuning configurations.
This configuration controls the maximum number of recipients who will receive a copy of a message at one time. This tunable value is related to throughput capacity and can enable the ability to optimize message delivery.... |
|
V-228382
|
Low |
Exchange Message size restrictions must be controlled on Receive connectors. |
Email system availability depends in part on best practice strategies for setting tuning configurations. For message size restrictions, multiple places exist to set or override inbound or outbound message size. Failure to control the configuration strategy can result in loss of data or system availability.
This setting enables the administrator... |
|
V-228381
|
Low |
Exchange Mailbox Stores must mount at startup. |
Administrator responsibilities include the ability to react to unplanned maintenance tasks or emergency situations that may require Mailbox data manipulation. Occasionally, there may be a need to start the server with "unmounted" data stores if manual maintenance is being performed on them. Failure to uncheck the "do not mount on... |
|
V-228380
|
Low |
Exchange Mail Quota settings must not restrict receiving mail. |
Mail quota settings control the maximum sizes of a user’s mailbox and the system’s response if these limits are exceeded. Mailbox data that is not monitored against a quota increases the risk of mail loss due to filled disk space, which can also render the system unavailable. Multiple controls supply... |
|
V-228379
|
Low |
Exchange Mail quota settings must not restrict receiving mail. |
Mail quota settings control the maximum sizes of a user’s mailbox and the system’s response if these limits are exceeded. Mailbox data that is not monitored against a quota increases the risk of mail loss due to filled disk space, which can also render the system unavailable.
Failure to allow... |
|
V-228360
|
Low |
Exchange Circular Logging must be disabled. |
Logging provides a history of events performed and can also provide evidence of tampering or attack. Failure to create and preserve logs adds to the risk that suspicious events may go unnoticed and raises the potential that insufficient history will be available to investigate them.
This setting controls how log... |
|
V-228359
|
Low |
Exchange Audit record parameters must be set. |
Log files help establish a history of activities and can be useful in detecting attack attempts. This item declares the fields that must be available in the audit log file in order to adequately research events that are logged.
Audit records should include the following fields to supply useful event... |
