How to Tell if a Work Phone Is Safe to Use
Ten checks that tell you if a company Android phone is safe for work data, what each one means, and how to see them for every phone in one place.
A work phone is safe to use when it is locked, encrypted, up to date on security fixes, running the software its maker shipped, and only installing apps from Google Play. If any of those is missing, the phone is a risk to whatever data sits on it. The hard part is not knowing the list. It is checking it on every phone, every week, without picking each one up.
Here is the scene that makes most owners look. A plumbing company with fourteen technician phones renews its cyber insurance. The questionnaire asks three things in a row. Are all mobile devices protected by a passcode? Are they encrypted? Are they receiving security updates? The owner is fairly sure the answer is yes. Fairly sure is not what the form wants.
This post walks through the checks that matter, what each one means in plain English, and how to read them for the whole fleet at once.
The ten things that decide if a phone is safe
Think of these as the questions you would ask if you could hold each phone in your hand.
- System integrity. Is the phone running the software its maker shipped, or has it been rooted or modified? A rooted phone can ignore the rules you set.
- Screen lock. Is there a PIN, pattern or password? Without one, anyone holding the phone can open it.
- Encryption. Is the data stored on the phone encrypted, so it cannot be read if someone takes the storage apart?
- Security update age. Is the latest security update less than 90 days old? Older than that and known holes stay open.
- Google Play Protect. Is app scanning switched on?
- Unknown app sources. Can apps only come from Google Play, or can someone install a file from anywhere?
- USB debugging. Is it off, so a computer plugged into the phone cannot read it?
- Developer options. Are they off? They exist for app builders, not for staff.
- Company policy. Does the phone meet the security settings you chose for it?
- Last check-in. Has the phone reported in within the last day, so you are reading a current answer and not an old one?
The last one is easy to skip and it matters most. A phone that passed everything three weeks ago and has not been heard from since is not a safe phone. It is an unknown one.
Why checking by hand does not work
You can check most of this on a single phone. Settings, then Security, then About phone for the update date. It takes a few minutes if you know where to look, and the menus differ by brand.
Now do it for fourteen phones that are out in vans all day. Then do it again next month. Nobody does, which is why the insurance form gets answered from memory.
There is also a gap you cannot close by hand. You cannot tell by looking whether a phone has been rooted. That needs a check from outside the phone.
How Device Trust answers it
Device Trust is a NounDesk feature that runs those ten checks on every enrolled company phone and gives it one rating.
- Trusted: every check passes.
- At risk: something is worth fixing soon, like a security update that is getting old.
- Not trusted: a serious problem. Fix it before the phone holds work data.
- Not reported yet: the phone has not sent its first security report.
System integrity comes from Google Play Integrity, which confirms whether the phone is running its original software. It is not read from an app on the phone, so a modified phone cannot simply claim to be fine.
Each rating comes with a plain-English reason and the fix. Not a code to look up. A sentence like “No PIN, pattern or password. Anyone holding the device can open it.”
A phone in lost mode is always marked Not trusted, so a missing phone never shows as safe. If one goes missing, our first-hour checklist for a lost work phone covers what to do next.
The checks run again every time the phone checks in. You never start a scan, and there is nothing extra to install.
How to check a phone in NounDesk
The rating shows in two places. The devices list has a Trust column, so you can scan the whole fleet in one look. Each device’s Security tab has the full breakdown. The Device Trust guide has the detail. Every role can see it.
- Open a device from the devices list.
- Select the Security tab.
- Read the Device trust rating at the top.
- Look down the 10 checks. Each one is marked pass, warning or fail, with the reason and the fix.
The Reports page also charts Trust across the fleet, so you can see how many phones sit in each rating.
What to do when a phone is not trusted
Device Trust tells you which phone, what is wrong and what to do. The fixing is still yours. Most problems have a short answer.
- No screen lock, no encryption, or Play Protect off. Publish a security policy that requires them. Our five policy templates cover these settings in plain English.
- Apps from unknown sources allowed. Turn off apps outside Google Play in the policy.
- Developer options or USB debugging on. Ask the employee to turn them off. Often someone was trying to fix a problem and forgot.
- Security update over 90 days old. Check whether the phone has an update waiting, or whether the maker has stopped sending them. Our guide to keeping company Android phones updated has a monthly routine for this.
- System integrity failed. Treat the phone as compromised. Lock it, take it back, and decide whether to erase it.
- Last check-in failed. Find out where the phone is. It may be switched off in a drawer, or it may be lost.
The honest limits
It is worth being clear about what this does not do.
It reports. It does not block. An untrusted phone can still sign in to your email and other apps. Device Trust tells you about it so you can act, for example by changing the policy, locking the phone or putting it in lost mode.
It is as current as the last check-in. The rating updates every time the phone checks in. A phone that has been off since Friday shows what it looked like on Friday, and the last check-in check flags that it is stale.
Phones you already have start as Not reported yet. They change to a real rating at their next report. Give it a day before you read the fleet.
Company-owned Android phones and tablets only. It covers phones enrolled in NounDesk. Personal phones and iPhones are not covered.
For the wider picture of running company phones, see our guide to Android MDM for small business.
What to do this week
- Open the devices list and sort by Trust. Count how many phones are Trusted, At risk and Not trusted. That number is your real answer to the insurance form.
- Fix every Not trusted phone first. Start with system integrity and screen lock. Those are the ones that matter most if a phone is lost.
- Clear the At risk phones next. Most are old security updates. Note any phone that no longer gets updates from its maker, and plan to replace it.
- Chase any phone that has not checked in for a day. Ask who has it and whether it is switched on.
- Keep the Security tab handy for the questionnaire. When an insurer or client asks how your phones are protected, it shows each check on each phone.
FAQ
How can I tell if a work phone has been rooted?
You need a check from outside the phone, because a rooted phone can hide it. Device Trust uses Google Play Integrity to confirm whether the phone is running the software its maker shipped.
Does an untrusted phone get blocked from company apps?
No, not today. Device Trust shows you the problem and the fix, and you act on it by changing the policy, locking the phone or putting it in lost mode.
How often is the rating updated?
Every time the phone checks in. If a phone goes quiet for more than a day, the last check-in check fails, so an old result is never shown as a current one.
Do I need to install anything on the phones?
No. It works on every company phone already enrolled in NounDesk, with no extra app and no setup.
If you want to see the Trust rating for your own phones, try NounDesk and enroll your first device today.