National Vulnerability Database

National Vulnerability Database

National Vulnerability
Database

IBM MaaS360 MDM STIG Ver 1, Rel 2 Checklist Details (Checklist Revisions)

Supporting Resources:

Target:

Target CPE Name
IBM MaaS360 MDM cpe:/a:ibm:maas360:- (View CVEs)

Checklist Highlights

Checklist Name:
IBM MaaS360 MDM STIG
Checklist ID:
790
Version:
Ver 1, Rel 2
Type:
Compliance
Review Status:
Archived
Authority:
Governmental Authority: Defense Information Systems Agency
Original Publication Date:
03/10/2016

Checklist Summary:

The IBM MaaS360 v2.3.x Mobile Device Management (MDM) Security Technical Implementation Guide (STIG) provides security policy and configuration requirements for the use of the MaaS360 MDM platform to provide administrative management of Mobile Operating System (MOS) devices in the Department of Defense (DoD). This STIG applies to version 2.3.x of the MaaS360 server. The MaaS360 product can be deployed as either Software as a Service (SaaS), where the server is installed in an IBM data center, or On-Premise, where the server is installed in a DoD datacenter. Both implementation models are covered by this STIG. The Supplemental document contains information regarding features, functions, and required Information Assurance (IA) controls for each implementation. The MaaS360 SaaS version has completed Federal Risk and Authorization Management Program (FeDRAMP) certification (Level 2 Provisional Authorization [PA]). It is recommended that DoD Authorizing Officials (AO) limit deployments of MaaS360 to On-Premise. The scope of this STIG includes the Apple iOS 9 and the Microsoft Windows 8.1 Phone. AOs can contact DISA at disa.stig_spt@mail.mil to obtain current information regarding the capability of the MaaS360 to manage STIG-required MDM controls for other mobile devices, including BlackBerry and Android.

Checklist Role:

  • Database Management System

Known Issues:

Not provided.

Target Audience:

Not provided.

Target Operational Environment:

  • Managed
  • Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

DoD Instruction (DoDI) 8500.01 requires that “all IT that receives, processes, stores, displays, or transmits DoD information will be […] configured […] consistent with applicable DoD cybersecurity policies, standards, and architectures” and tasks that Defense Information Systems Agency (DISA) “develops and maintains control correlation identifiers (CCIs), security requirements guides (SRGs), security technical implementation guides (STIGs), and mobile code risk categories and usage guides that implement and are consistent with DoD cybersecurity policies, standards, architectures, security controls, and validation procedures, with the support of the NSA/CSS, using input from stakeholders, and using automation whenever possible.” This document is provided under the authority of DoDI 8500.01.

Comments/Warnings/Miscellaneous:

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 Authorizing Official. 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 Department of Defense. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied both at the device hardening level as well as the architectural level due to the fact that some of the settings may not be able to be configured in environments outside the DoD architecture. Disclaimer

Disclaimer:

Not provided.

Product Support:

Not provided.

Point of Contact:

disa.stig_spt@mail.mil

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

Moved to FINAL - 08/29/2017
Updated to Ver 1, Rel 2 - 10/25/18
Updated to FINAL - 11/26/18
moved to archive status - 4/15/19
Updated URLs - 6/6/19
updated URLs - 9/11/19

Dependency/Requirements:

URL Description

References:

Reference URL Description
https://dl.dod.cyber.mil/wp-content/uploads/stigs/pdf/IBM_MAAS_360_V1_Release_Memo.pdf Sunset - IBM MaaS360 MDM Ver 1 Release Memo

NIST checklist record last modified on 09/11/2019