SkieWhat does the Skie compliance score confirm about hardening?
After every policy apply, the device reads each protection back from Android and reports whether it is actually in force. The compliance score is built from that read-back, so it confirms the state Android itself reports, not just that Skie sent a command. A lower score points you to the device and the protection that needs attention.
Sending a rule and having it take effect are two different things. A device might be switched off, mid-update or on a model that behaves oddly. So Skie does not stop at sending. When a policy is applied, the Skie app on the device asks Android for the current value of each protection, such as whether factory reset is blocked or safe mode is disabled, and sends the results back.
The compliance score summarises those results for a device, and the dashboard rolls it up for a group, branch, school or organisation. You can see the average, how many devices are fully compliant, and how many are on the latest policy. If one device reports that a protection is off, you can open it and see which one.
A run can also be started on demand. This is useful after you change a policy and want an answer straight away instead of waiting for the next sync. A device that has not checked in recently will show up through the Due, Overdue and Offline states, and a missing check-in is counted in the breach centre.
The score confirms what Android reports at the time of the check. It is a good daily view for an admin, not a replacement for looking at a device in person when something looks odd.
Practical tip: check the average compliance for each school on Monday morning. A single device sitting below the rest usually means it was powered off over the weekend, and a sync brings it back.