The application must protect the confidentiality and integrity of transmitted information.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-259710 | EX19-MB-000236 | SV-259710r961632_rule | CCI-001184 | high |
| Description | ||||
| Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, applications need to leverage transmission protection mechanisms, such as TLS, TLS VPNs, or IPsec. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. Satisfies: SRG-APP-000219 | ||||
| STIG | Date | |||
| Microsoft Exchange 2019 Mailbox Server Security Technical Implementation Guide | 2025-05-14 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
SC-23
1.00
- DISA · V2R3 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.13.15
1.00
- DISA · V2R3 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-001184
1.00
- DISA · V2R3 · disa_xccdf · related
Details
Check Text (C-259710r961632_chk)
Note: AuthMechanism may include other mechanisms as long as the "Tls" is identified.
Open the Exchange Management Shell and enter the following command:
Get-ReceiveConnector | Select-Object -Property Name, Identity, AuthMechanism
For each Receive connector, if the value of "AuthMechanism" is not set to "Tls", this is a finding.
Fix Text (F-63357r942443_fix)
Open the Exchange Management Shell and enter the following command:
Set-ReceiveConnector -Identity <'IdentityName'> -AuthMechanism 'Tls'
Note: The <IdentityName> value must be in quotes.
Repeat the procedures for each Receive connector.