SkieWhat counts as a breach in Skie?
A breach is a sign that a managed device is not where, or how, it should be. The main cases are a device that has gone silent for longer than its limit, one that has left its geofence, one that has lost a protection, and one that missed its check-in. The thresholds for the silence cases are editable.
Skie uses the word breach for anything that tells an administrator a device may not be under the rules. It is not a claim that someone did something wrong. A flat battery produces a silent device, and so does a classroom with no Wi-Fi.
Silent: the device has not reported within its limit. Skie moves it through states described in Due, Overdue and Offline unusual and, past the breach limit, raises a breach. Left a zone: a device in a group with a geofence is reported outside it. Lost a protection: after every apply the device reads each protection back from Android and reports a compliance score, so if one is found off, that shows up. Missed check-in: the device was expected to report and did not, covered in missing check-in.
Skie is also built to be tamper-proof, and if anything ever did get through, the admin is alerted immediately, down to the exact device. That is what the breach centre is for.
You control how sensitive it is. The Due, Overdue, Offline unusual and breach thresholds can all be edited, as can the sync interval. A school that closes for a week will want longer limits than a depot that runs all day. Set them to match real life, otherwise the list fills with noise and people stop reading it.
Practical tip: review the thresholds after the first two weeks of a pilot, when you have seen how many false alarms your own network and routines produce.