What changed in BlackBerry Enterprise Mobility Server 3.x STIG V1R2V1R2 changes

BlackBerry Enterprise Mobility Server 3.x STIG V1R2 (2023-07-26) replaced V1R1 (2022-11-03): 1 check updated. It has 27 checks, against 27 in V1R1.

  • 0 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1Fix text 1

Updated in V1R2 (1)

V-254720CAT IIIf the Mail service (Push Notifications support for BlackBerry Work) is installed on the BlackBerry Enterprise Mobility Server (BEMS), it must be configured to use Windows Integrated Authentication for the Exchange connection.Check text, Fix text

Check text

This requirement is not applicable if the Mail service (Push Notifications support for BlackBerry Work) is not enabled on BEMS. Verify Windows Integrated Authentication for the Exchange connection for the Mail service has been set up in BEMS as follows: *On-Prem email server used at site: 1. In the BEMS Dashboard, under "BlackBerry Services Configuration", click "Mail". 2. Click "Microsoft Exchange". 3. Under "Enter Service Account Details", verify "Use Windows Integrated Authentication" has been selected. *O-365 email server used at site: 1. If credential authentication is used by the site: a. In the BEMS Dashboard, under "BlackBerry Services Configuration", click "Mail". b. Click "Microsoft Exchange". c. In the "Select Authentication type" section, verify "Credential" authentication type is listed. 2. If client certificate is used at site: a. In the BEMS Dashboard, under "BlackBerry Services Configuration", click "Mail". b. Click "Microsoft Exchange". c. In the "Select Authentication type" section, verify "Client Certificate" authentication type is listed. If Windows Integrated Authentication for the Exchange connection for the Mail service has not been set up in BEMS, this is a finding.

Fix text

Set up Windows Integrated Authentication for the Exchange connection for the Mail service in BEMS: *On-Prem email server used at site: 1. Log on to BEMS with the service account that will be configured. 2. In the BEMS Dashboard, under "BlackBerry Services Configuration", click "Mail". 3. Click "Microsoft Exchange". 4. Under "Enter Service Account Details", select the "Use Windows Integrated Authentication" check box. 5. Click "Save". *O-365 email server used at site: Use one of the following procedures based on the authentication type used at the site. 1. Credential a. In the BEMS Dashboard, under "BlackBerry Services Configuration", click "Mail". b. Click "Microsoft Exchange". c. In the "Select Authentication type" section, select "Credential" authentication type and complete the associated task to allow BEMS to communicate with Microsoft O365. (This option uses a defined BEMS username and password to authenticate to Microsoft Office 365 using Basic Authentication.) i. In the "Username" field, enter the User Principal Name (UPN) of the BEMS service account. ii. In the "Password" field, enter the password for the service account. 2. Client Certificate a. In the BEMS Dashboard, under "BlackBerry Services Configuration", click "Mail". b. Click "Microsoft Exchange". c. In the "Select Authentication type" section, select "Client Certificate" authentication type and complete the associated task to allow BEMS to communicate with Microsoft O365. (This option uses a client certificate to allow the BEMS service account to authenticate to Microsoft Office 365.) i. For the "Upload PFX file", click "Choose File" and select the client certificate file. ii. In the "Enter PFX file Password" field, enter the password for the client certificate.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V1R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.