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 firstname.lastname@example.org to obtain current information regarding the capability of the MaaS360 to manage STIG-required MDM controls for other mobile devices, including BlackBerry and Android.
- Database Management System
- Specialized Security-Limited Functionality (SSLF)
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.
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
NIST checklist record last modified on 09/11/2019