From IBM MaaS360 v2.3.x MDM Security Technical Implementation Guide
Part of PP-MDM-203106
Associated with: CCI-000129 CCI-000169 CCI-000366 CCI-001571
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.
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 Devices >> Groups.
2. Have System Administrator identify one or more groups that alert for failure to update an existing application on a managed mobile device.
3. Select "edit" for one of the identified groups and verify that the two conditions exist:
Condition 1: "Software Installed", "Application Name", "Contains", "
Configure the MAS Server to enable all required audit events: Failure to update an existing application on a managed mobile device.
On the MaaS360 Console complete the following Steps:
1. Navigate to Devices >> Groups.
2. Select one or more groups that alert for failure to update an existing application on a managed mobile device.
3. Select "edit" for one of the identified groups and set the two conditions:
Condition 1: "Software Installed", "Application Name", "Contains", "
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer