Free DISA STIG and SRG Library | Vaulted

V-65639

The MaaS360 Server must leverage the MDM Platform user accounts and groups for MaaS360 Server user identification and authentication.

Finding ID
M360-01-005300
Rule ID
SV-80129r1_rule
Severity
Cat II
CCE
(None)
Group Title
PP-MDM-204101
CCI
CCI-000015
Target Key
(None)
Documentable
No
Discussion

A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. If an attacker compromises an account, the entire MaaS360 Server infrastructure is at risk. Providing automated support functions for the management of accounts will ensure only active accounts will be granted access with the proper authorization levels. These objectives are best achieved by configuring the MaaS360 Server to leverage an enterprise authentication mechanism (e.g., Microsoft Active Directory, Kerberos). SFR ID: FIA

Fix Text

Configure the MaaS360 Server to leverage the MDM Platform user accounts and groups for MaaS360 Server user identification and authentication. On the MaaS360 Console complete the following steps: 1. Navigate to Setup >> Login Settings. 2. Select "Configure Federated Single Sign-On" and "Authenticate against Corporate User Directory". 3. For SaaS deployments only install the Cloud Extender: Setup >> Cloud Extender and select "Cloud Extender Online".

Check Content

Review the MaaS360 server console and confirm that the MDM platform accounts are leveraged when users identify and authenticate themselves to the MaaS360 console. On the MaaS360 Console complete the following steps: 1. Navigate to Setup >> Login Settings. 2. Verify "Configure Federated Single Sign-On" is checked and "Authenticate against Corporate User Directory" is selected. 3. For SaaS deployments only verify the Cloud Extender is installed: Setup >> Cloud Extender and verify "Cloud Extender Online" is checked. If "Configure Federated Single Sign-On" and "Authenticate against Corporate User Directory" are not selected, this is a finding. For SaaS deployments if Cloud Extender is not installed or "Cloud Extender Online" is not checked, this is a finding.