Why does a missing check-in count as a breach?

Skie for Enterprise · Updated

Short answer

A device that stops checking in tells you nothing, and silence is exactly what you would see if someone had switched it off or taken it out of range on purpose. So Skie treats a missed check-in as a breach once it passes the limit you set. It may only be a flat battery, but you will know.

Managed devices report in regularly. A repeating alarm about every four minutes reports presence, and a device syncs instantly when the internet returns or when the screen turns on after being stale. So a healthy device leaves a steady trail of last-seen times.

If that trail stops, an administrator is blind. Nothing is telling them whether the device is in a locker, out of charge, off the Wi-Fi, switched off by someone, or in another town. The safest assumption is that it needs a look, so a missed check-in is a breach in its own right, not just a missing data point.

The word breach does not accuse anyone. Most missed check-ins have dull explanations. What Skie gives you is the time: how long the device has been silent and when it was last seen. That lets you tell the difference between a device that missed one check-in a few minutes ago and one that vanished yesterday afternoon.

The limits are yours to set. The Due, Overdue, Offline unusual and breach thresholds are editable, and so is the sync interval. A school might accept a long silence over a holiday weekend, while a delivery fleet will want a short one. When the device returns and reports, the breach can be resolved. See what resolve does.

The rules on the device keep working while it is silent, since they are cached on it. Practical tip: check Wi-Fi password changes and charging habits first when a whole group goes quiet together.