BlackBerry Enterprise Mobility Server 2.x STIG Version Comparison
BlackBerry Enterprise Mobility Server 2.x Security Technical Implementation Guide
Comparison
There are 2 differences between versions v1 r2 (Jan. 25, 2019) (the "left" version) and v2 r0.1 (Sept. 1, 2020) (the "right" version).
Check BEMS-00-011500 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.
Text Differences
Title
The BlackBerry Enterprise Mobility Server (BEMS) must remove all export ciphers to protect the confidentiality and integrity of transmitted information.
Check Content
Verify BEMS has been configured to remove all export ciphers: 1. Find the xml file "jetty.xml" located in the BEMS install directory on the BEMS host Windows server. 2. Find the "ExcludeCiphersSuites" "AllowCiphersSuites" field. 3. Verify if any export ciphers are listed in the "jetty.xml" file. If file. Verify only approved cypher suites are included. (See NIST SP 800-53r2 for a list of approved TLS suites.) If BEMS has been configured to use export ciphers, this is a finding.
Discussion
During the initial setup of a Transport Layer Security (TLS) connection to the application server, the client sends a list of supported cipher suites in order of preference. The application server will reply with the cipher suite it will use for communication from the client list. If an attacker can intercept the submission of cipher suites to the application server and place, as the preferred cipher suite, a weak export suite, the encryption used for the session becomes easy for the attacker to break, often within minutes to hours.
Fix
Configure BEMS to remove all export ciphers. 1. Find the xml file "jetty.xml" located in the BEMS install directory on the BEMS host Windows server. 2. Find the "ExcludeCiphersSuites" "AllowCiphersSuites" field and remove all export ciphers. 3. cipher suites that are not approved. (See NIST SP 800-53r2 for a list of approved TLS suites.) 3. Save file. 4. Restart the BEMS server.