Checklist Summary:

The BlackBerry Enterprise Mobility Server (BEMS) 3.x Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DOD) information systems. BEMS provides additional services for BlackBerry Dynamics apps. BlackBerry Dynamics is a component of the BlackBerry Unified Endpoint Manager (UEM) server. BEMS services include BlackBerry Mail, BlackBerry Connect, BlackBerry Presence, and BlackBerry Docs. A site can select which BEMS services to enable for supported mobile device users. This STIG provides requirements for the configuration of core BEMS and three of the four BEMS services. There are no STIG requirements for the installation and configuration of BlackBerry Presence. This document is meant for use in conjunction with other STIGs including SQL Server, Apache Tomcat, Oracle JRE, and appropriate Windows Server STIGs.

Checklist Role:

• Server

Known Issues:

Not provided.

Target Audience:

Parties within the DOD and federal government’s computing environments can obtain the applicable STIG from the DOD Cyber Exchange website at https://cyber.mil/. This site contains the latest copies of STIGs, SRGs, and other related security information. Those without a Common Access Card (CAC) that has DOD Certificates can obtain the STIG from https://public.cyber.mil/.

Target Operational Environment:

• Managed
• Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

This document is provided under the authority of DODI 8500.01.

Comments/Warnings/Miscellaneous:

Not provided.

Disclaimer:

DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible AO. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure. Security guidance is provided for the DOD. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied at both the device hardening level and the architectural level due to the fact that some settings may not be configurable in environments outside the DOD architecture.

Product Support:

Not provided.

Point of Contact:

Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

updated to FINAL - 12/1/22
Updated URLs per DISA - 7/25/23

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 07/25/2023