STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

IBM MaaS360 with Watson v10.x MDM Security Technical Implementation Guide

Version

V1R2

Release Date

Aug 6, 2019

SCAP Benchmark ID

IBM_MaaS360_with_Watson_v10.x_MDM_STIG

Total Checks

12

Tags

other
CAT I: 0CAT II: 9CAT III: 3

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (12)

V-82153MEDIUMThe MaaS360 MDM server must be configured to transfer MaaS360 MDM server logs to another server for storage, analysis, and reporting. Note: MaaS360 MDM server logs include logs of MDM events and logs transferred to the MaaS360 MDM server by MDM agents of managed devices.V-82159LOWThe MaaS360 MDM server must be configured to display the required DoD warning banner upon administrator logon. Note: This requirement is not applicable if the TOE platform is selected in FTA_TAB.1.1 in the Security Target (ST).V-82167MEDIUMThe MaaS360 MDM server must be configured to have at least one user in the following Administrator roles: Server primary administrator, security configuration administrator, device user group administrator, auditor.V-82169MEDIUMThe MaaS360 MDM server must be configured to leverage the MDM platform user accounts and groups for MaaS360 MDM server user identification and authentication.V-82171MEDIUMAuthentication of MaaS360 MDM platform accounts must be configured so they are implemented via an enterprise directory service.V-82175LOWThe MaaS360 MDM server must be configured to enable all required audit events (if function is not automatically implemented during MDM/MAS server install): a. Failure to push a new application on a managed mobile device.V-82181LOWThe MaaS360 server must be configured to enable all required audit events (if function is not automatically implemented during MDM/MAS server install): b. Failure to update an existing application on a managed mobile device.V-82187MEDIUMThe MaaS360 server platform must be protected by a DoD-approved firewall.V-82189MEDIUMThe firewall protecting the MaaS360 server platform must be configured to restrict all network traffic to and from all addresses with the exception of ports, protocols, and IP address ranges required to support MaaS360 server and platform functions.V-82191MEDIUMThe firewall protecting the MaaS360 server platform must be configured so that only DoD-approved ports, protocols, and services are enabled. (See the DoD Ports, Protocols, Services Management [PPSM] Category Assurance Levels [CAL] list for DoD-approved ports, protocols, and services.)V-82193MEDIUMThe MaaS360 MDM Agent must be configured to implement the management setting: periodicity of reachability events equals six hours or less.V-82195MEDIUMThe MaaS360 MDM Agent must provide an alert via the trusted channel to the MDM server for the following event: change in enrollment state.