Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-65635 | M360-01-003800 | SV-80125r1_rule | Medium |
Description |
---|
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: FAU_GEN.1.1(2) Refinement |
STIG | Date |
---|---|
IBM MaaS360 v2.3.x MDM Security Technical Implementation Guide | 2018-09-13 |
Check Text ( C-66195r1_chk ) |
---|
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 system administrator identify which mobile operating system (iOS, etc.) the MDM policy alerts apply to. 2. Open 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, Windows Phone, etc.) If the "Configure required applications" is not set to "yes" or all new applications are not on the list, this is a finding. |
Fix Text (F-71563r1_fix) |
---|
Configure the MAS 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 identified policy and go to device settings >> application compliance. 3. Set "Configure required applications" is set to "yes" and list all new applications 4. Repeat for other MOS as required (for example, Windows Phone, etc.) |