STIGUI
V-82175CAT III — Low severitySV-96889r1_rule

The 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.

Rule version M360-10-100200 · STIG v1 · 2019-08-06

Discussion

Failure to generate these audit records makes it more difficult to identify or investigate attempted or successful compromises, potentially causing incidents to last longer than necessary.

SFR ID: FMT_SMF.1.1(3) c, FAU_GEN.1.1(2)

Check

Review the MaaS360 server console and confirm the server is configured to alert for audit event failures on managed mobile devices.

On the MaaS360 Console, complete the following steps: 1. Navigate to Security >> Policies and have the System Administrator identify which mobile operating system (iOS, etc.) the MDM policy alerts apply to. 2. Open the identified policy and go to device settings >> application compliance. 3. Verify that "Configure required applications" is set to "yes" and that all new applications are listed. 4. Repeat for other MOS as required (for example, Android).

If the "Configure required applications" is not set to "yes" or all new applications are not on the list, this is a finding.

Fix

Configure the MaaS360 server to enable all required audit events: Failure to push a new application on a managed mobile device.

On the MaaS360 Console, complete the following steps: 1. Navigate to Security >> Policies and select the mobile operating system (iOS, etc.) the MDM policy alerts apply to. 2. Open the identified policy and go to device settings >> application compliance. 3. Set "Configure required applications" to "yes" and list all new applications. 4. Repeat for other MOS as required (for example, iOS, Android, etc.).

Identifiers

Group ID
V-82175
Group title
PP-MDM-323202
Rule ID
SV-96889r1_rule
Check ID
C-82003r1_chk
Fix ID
F-89033r1_fix