Microsoft Exchange 2013 Mailbox Server STIG Version Comparison

There are 1 differences between versions v2 r1 (Jan. 22, 2021) (the "left" version) and v2 r3 (July 24, 2024) (the "right" version).

Check EX13-MB-000340 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

The version of Exchange running on the system must be a supported version. have the most current, approved service pack installed.

Check Content

Determine Exchange 2013 is no longer supported by the vendor. If most current, approved service pack. Open the system is running Exchange 2013, Management Shell and enter the following command: Get-ExchangeServer | fl Name, AdminDisplayVersion If the value of AdminDisplayVersion does not return the most current, approved service pack, this is a finding.

Discussion

Failure to install Security flaws with software applications are discovered daily. Vendors are constantly updating and patching the their most current Exchange products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service pack packs, leaves and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerable vulnerability related to exploitation. Current service packs correct the discovered flaw). This requirement will apply to software patch management solutions used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their known own security and patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance vulnerabilities. Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

Fix

Upgrade to a supported version. Install the most current, approved service pack.