How It Works
Google continuously evaluates the security of enrolled Android devices. Each device is assigned a security posture — an overall assessment of how secure the device is. This posture is evaluated at enrollment, when it changes and at least once per day.
Security posture provides a security evaluation of a device based on its current status, considering factors like root access or custom ROMs.
Administrators can configure automatic actions based on the device's security posture. When a device's posture changes to a non-secure state, Appaloosa checks the configured action and can automatically wipe the device if needed.
Security Posture States
Each device is assigned one of the following posture states by Google:
State | Description |
Secure | The device is secure and compliant. No action is taken. |
Posture Unspecified | The device's security posture could not be determined. This can happen with older devices or when the security evaluation has not yet completed. |
At Risk | The device has security vulnerabilities. For example, the OS version may be outdated, or a security patch is missing. |
Potentially Compromised | The device may have been tampered with. This is the most severe non-secure state. |
Why a Device May Have a Bad Security Posture
When a device is not in a Secure state, Google provides detailed reasons through security risks. These risks explain what specifically is wrong with the device:
Security Risk | Description |
Unknown OS | The operating system version cannot be determined. The device may be running a non-standard or unrecognized OS build. |
Compromised OS | The operating system appears to have been tampered with (e.g., rooted device, custom ROM, or unlocked bootloader). This is one of the most common reasons for a "Potentially Compromised" posture. |
Hardware-Backed Evaluation Failed | The device failed a hardware-level security check (SafetyNet / Play Integrity attestation). This means the device's integrity could not be verified by Google's hardware-backed security mechanisms. |
Security Risk Unspecified | A security concern was detected but could not be categorized into a specific risk type. |
Configuring Security Posture Actions
Administrators can configure what happens when a device enters a non-secure posture state. This configuration is available per Android Enterprise configuration (Managed or BYOD).
Where to find the settings
1. Go to Devices > Configurations
2. Select an Android configuration (Managed or BYOD)
3. Navigate to the Security tab
4. Find the Security Posture section
Available actions
For each non-secure posture state, you can choose one of the following actions:
Action | Description |
Allow enrollment | The device is allowed to remain enrolled. No automatic action is taken. |
Wipe device | The device is automatically wiped and removed from the environment. All store admins are notified by email. |
You can configure a different action for each posture state. For example, you could:
Allow devices with Posture Unspecified to remain enrolled
Wipe devices that are At Risk
Wipe devices that are Potentially Compromised
Retroactive enforcement
When you change an action from "Allow enrollment" to "Wipe device", all devices currently in that posture state will be wiped immediately. This ensures consistent policy enforcement.
Viewing Security Posture in the Dashboard
Device details
On a device's detail page, the security posture is displayed with:
Secure: shown as "Secure"
Non-secure states: shown with a red warning icon and a tooltip containing:
The specific security risk reasons (e.g., "Compromised OS")
Any advice messages from Google
Filtering devices
You can filter devices by their security posture:
1. Go to the Devices list
2. Add a filter for Security Posture
3. Select the posture state you want to filter by (Secure, Unspecified, At Risk, or Potentially Compromised)
This is useful for quickly identifying all non-compliant devices in your environment.
Admin Notifications
When a device is automatically wiped due to its security posture, all administrators of the store receive an email notification containing:
- The action taken (device wiped)
- The security posture that triggered the wipe (e.g., "At Risk", "Potentially Compromised")
