Supported editions for this feature: Business Plus; Enterprise; Education Standard and Education Plus; G Suite Business; Cloud Identity Premium. Compare your edition
You can use the audit and investigation page to run searches related to Device log events. There you can view a record of actions on computers, mobile devices, and smart home devices that are used to access your organization's data. For example, you can see when a user added their account to a device or if a device’s password doesn’t follow your password policy. You can also set an alert to be notified when an activity occurs.
For a full list of services and activities that you can investigate, such as Google Drive or user activity, read through the data sources for the audit and investigation page.
Open the audit and investigation page
Before you begin
- To see all audit events for mobile devices, the devices need to be managed using advanced device management.
- To see changes to applications on Android devices, you must turn on application auditing.
- You can’t see activities for devices that sync corporate data using Google Sync.
- If you downgrade to an edition that doesn't support the audit log, the audit log stops collecting data for new events. However, old data is still available to admins.
Access Device log event data
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
- On the left, click ReportingAudit and investigationDevice log events.
Filter the data
- Open the log events as described above in Access Device log event data.
- Click Add a filter, and then select an attribute.
- In the pop-up window, select an operatorselect a valueclick Apply.
(Optional) To create multiple filters for your search:
- Click Add a filter and repeat step 3.
- (Optional) To add a search operator, above Add a filter, select AND or OR.
- Click Search.
Note: Using the Filter tab, you can include simple parameter and value pairs to filter the search results. You can also use the Condition builder tab, where the filters are represented as conditions with AND/OR operators.
For this data source, you can use the following attributes when searching log event data:
|Account state||Whether the account is registered or unregistered|
|Actor group name||Group name of the actor|
|Actor organizational unit||Organizational unit of the actor|
|Application ID||Identifier for the application|
|Application SHA-256 hash||For app-related events, the SHA-256 hash of the application package (Android only)|
|Application state||Whether the application is installed, uninstalled, or updated|
|Date||Date and time of the event (displayed in your browser's default time zone)|
|Device compliance state||
Whether the device complies with your organization’s policies.
A device is marked not compliant if it:
Example: User's Nexus 6P is not compliant with set policies because device is not adhering to password policy.
|Device compromised state||
Whether the device is compromised. Devices can become compromised if they’re rooted or jailbroken—processes that remove restrictions on a device. Compromised devices can be a potential security threat.
The system records an entry each time a user’s device is compromised or no longer compromised.
Example: User's Nexus 5 is compromised.
|Device ID||Identifier for the device that the event happened on|
|Device model||The model of the device|
|Device owner||The owner of the device|
Whether the ownership of the device changed.
For example, a personal device was changed to company-owned after its details were imported into the Admin console.
This audit occurs immediately after a company-owned device is added to the Admin console. If a company-owned device is deleted from the Admin console, the audit occurs at the next sync (after it’s re-enrolled for management).
Example: Ownership of user’s Nexus 5 has changed to company owned, with new device id abcd1234.
|Device property||Information about the device, such as Device model, Serial number, or WiFi MAC address.|
The device user changed the developer options, unknown sources, USB debugging, or verify apps setting on their device.
This event is recorded the next time the device syncs.
Example: Verify Apps changed from off to on by user on Nexus 6P.
|Device type||Type of device that the event happened on. For example, Android or Apple iOS.|
|Domain||The domain where the action occurred|
|Event||The logged event action, such as Device OS update or Device sync event|
|Failed password attempts||
The number of failed attempts by a user to unlock a device.
An event is generated only if there are more than 5 failed attempts to unlock a user's device.
Example: 5 failed attempts to unlock user's Nexus 7.
|iOS vendor ID||Identifier for the iOS vendor|
|New device ID||Identifier for the new device|
|OS property||Information about the OS, such as Build number, OS version, or Security patch|
|Register privilege||The role of the user for a device, such as Device owner or Device administrator|
|Resource ID||Unique identifier for the device|
|Serial number||The serial number of the device|
|User email||Email address of the device user|
Manage log event data
Manage search results column data
You can control which data columns appear in your search results.
- At the top-right of the search results table, click Manage columns .
- (Optional) To remove current columns, click Remove .
- (Optional) To add columns, next to Add new column, click the Down arrow and select the data column.
Repeat as needed.
- (Optional) To change the order of the columns, drag the data column names.
- Click Save.
Export search result data
- At the top of the search results table, click Export all.
- Enter a name click Export.
The export displays below the search results table under Export action results.
- To view the data, click the name of your export.
The export opens in Google Sheets.
Create reporting rules
Go to Create and manage reporting rules.
When and how long is data available?
Go to Data retention and lag times.