research
Auditing whether mobile devices allow unapproved app installs
A method for checking mobile device management settings, app catalogues, and exceptions that let staff install software outside review.
Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.
Research playbook
On this pageJump to section
Key stats
Key takeaways
A phone or tablet can install a new app in seconds, and the business may never see the request. Some of those apps are harmless tools, while others copy company data to personal storage or open a new sign-in path. Most small companies rely on a mobile management profile but never test what it actually blocks. This audit checks the settings, the catalogue, and the exceptions that determine what can be installed. The audit checks configuration and practice, not the security quality of each approved app.
Question and scope
The audit asks whether managed mobile devices can install applications outside the approved catalogue, and which devices or groups are exempt. The unit is one managed device or one policy assignment. The population is every mobile device enrolled in the company management system. The result describes the configuration and a sample of devices at the audit date. Record the management platform, the policy version, and the audit date.
Include company-owned phones, tablets, and laptops that run mobile apps where the management system covers them. Include personal devices enrolled under a bring-your-own-device policy. Exclude devices that are not enrolled, but count them and record why. An audit that ignores unenrolled devices will overstate control. Note the unenrolled devices, the reason they sit outside management, and the owner who must enroll them.
Define the control baseline
Write down the expected state for app installation, such as allowing only apps from the managed catalogue, blocking unknown sources, and requiring review for new categories. Base the baseline on the company policy and the management platform's capabilities. Note where the platform cannot enforce the rule. Record whether the platform can block installation or only report it, and note the version that provides the control.
Decide how the company treats app updates, side-loaded tools, and browser-based installs. Record whether personal devices may keep personal apps and how work data is separated. A baseline that ignores personal use will be quietly abandoned by staff. The rule should be specific enough to test. Write the baseline as a short checklist that a reviewer can mark pass or fail.
Build the device frame
Export the enrolled device list with the platform, the operating system version, the owner, the group, and the last check-in. Add the policy assigned to each device. Note the devices that have not checked in for thirty days. A device that has not reported is not confirmed compliant. Record the last check-in date and the operating system version for each device.
Match the device list to the asset register and the identity provider. Mark the devices that cannot be matched. Record the personal devices and their enrollment type. The frame should show both the managed population and the gap outside it. Note the devices that appear in the asset register but not in management, and the date each was last seen.
Collect management settings
Export the mobile policies and record the settings that govern app installation, unknown sources, and app store access. Capture the date and the platform version because settings change between releases. Note which groups each policy applies to. A policy that applies to nobody is a configuration, not a control. Record the policy assignment, the group that receives it, and the number of devices in that group.
Check the app protection settings that control copy, save, and sign-in on managed apps. Record whether the company can remove work data without wiping a personal device. Compare the settings with the baseline. Note any setting that is available but unused. Capture the setting name, the value, the platform version, and the screen where it was found so another reviewer can repeat the check.
Test a sample of devices
Choose at least ten devices across platforms, departments, and ownership types. On each device, check the installed app list, the management status, and whether the app store is available. Try to install a harmless test app that is outside the catalogue. Record the result and the steps taken. Use a test device or a compliance report when a live install is not appropriate.
Do not install unapproved software on a production device without approval. Use a test device or the platform's compliance report where a live test is not appropriate. Record the method for each device. The sample should show whether the policy works in practice, not only whether it exists. Record the test app, the result, and the person who performed the test.
Review the app catalogue
List the approved apps and the person who approved each one. Check the last review date and the business reason. Remove apps that are no longer used or supported. Note the apps that are approved for one group but visible to everyone. The catalogue is the allow list and should be maintained like one. Note the apps that are approved for one group but visible to all.
Check how a new app request is submitted and who can approve it. Test the route with a sample request. Record the time to decision and the evidence required. A catalogue without a request path will be bypassed by anyone in a hurry. Record the request route, the approver, the time to decision, and the evidence attached to the request.
Check exceptions and personal devices
List the devices with an exception, the reason, and the end date. Confirm that each exception is still needed. Check whether a personal device can install work apps from outside the catalogue. Record how work data is separated and what happens when the person leaves. Note the exception reason, the approval date, the review date, and the person who granted it.
Review the groups that can install apps without review, such as the leadership team or the engineering team. Confirm that the group membership is current. Note any exception granted verbally. An exception without an end date becomes the new baseline. Record the groups with install rights, the current membership, and the date the membership was checked, with the approver named.
Report by risk and owner
Group the findings by risk, starting with devices that allow unknown sources and apps that can copy work data. Add the unenrolled devices and the exceptions without an end date. Send the report to the mobile owner and the technical manager. Keep personal device details out of the summary. Add the unenrolled devices and the open exceptions to the risk summary.
Assign an owner and a due date to each finding. Ask for a decision on every exception. Record the decision in the mobile register. The report is complete when each finding has a resolution, not when the export is finished. Record the decision, the owner, the date for each finding, and the evidence that closes it, such as a screenshot or a signed note.
Set the review cadence
Review the policies after every platform update and at least quarterly. Recheck the app catalogue monthly and the exceptions at each review. Confirm that new starters receive the current profile. Add the review to the onboarding and leaver checklists. Note the platform updates that changed a setting or added a new control, and retest the baseline after each one so the policy still does what the team expects.
Repeat the device sample after a policy change to confirm the result. Keep the export and the report with the mobile documentation. Compare the number of exceptions with the previous quarter. A stable, small exception list is a better sign than a perfect policy that nobody follows. Record the sample result, the policy version used for the retest, and the devices that changed group.
Limits of the audit
The audit sees the devices and settings the management system reports. It cannot see apps installed in a personal profile outside management, or a browser tool that behaves like an app. It also cannot prove that an approved app is safe. State these limits so the report is read as a configuration review. Note the apps that were removed from the catalogue and the reason.
The device sample may miss a rare configuration. Increase the sample when the estate has many platforms or ownership types. Repeat the audit after an incident or a platform migration. The method is strongest when the same baseline and sample rules are used each time. Keep the baseline and the sample rule with the mobile documentation so the next reviewer applies the same test.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the vault administrator, SaaS project account, domain contact, loaner handover, and mobile app measures discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.
Compare this study with the vault administrator audit and the SaaS project account study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.
Benchmark brief
What this research page must produce
A practical estimate for volume, review time, escalation rate, and assistant capacity.
A clear split between routine support, preparation work, and technical ownership.
What the auditing whether mobile devices allow unapproved app installs data shows
Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.
The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.
Workflow
Recommended operating workflow
Collect a baseline
Pull the last 30 to 90 days of examples related to auditing whether mobile devices allow unapproved app installs, including completed work and unresolved exceptions.
Classify the work
Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.
Set the operating number
Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.
Refresh the benchmark
Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.
Decision rules
| Metric | Use it to decide | Manager action |
|---|---|---|
| Weekly volume | Whether the workflow is worth assigning as recurring assistant work. | Approve a weekly capacity target and backlog threshold. |
| Access sensitivity | Whether the assistant can work directly or only prepare review notes. | Set least-privilege permissions and removal dates. |
| Escalation rate | Whether the workflow is stable enough to delegate. | Rewrite the SOP when exceptions exceed the agreed threshold. |
Consolidated statistics
| Statistic | Figure | Source |
|---|---|---|
| Unit | One managed device | Study protocol |
| Device sample | Ten devices | Study protocol |
| Review cadence | Quarterly | Study protocol |
Sources
- NIST SP 800-124 Rev. 2, Guidelines for Managing the Security of Mobile DevicesMobile device management and application control guidance.
- CISA Cross-Sector Cybersecurity Performance GoalsBaseline controls for endpoint and software management.
- NIST Cybersecurity Framework 2.0Asset and configuration management outcomes.
- NIST SP 800-53 Rev. 5, Security and Privacy ControlsControl language for configuration settings and audit records.
Measurement checklist
| Field | What to capture | Owner |
|---|---|---|
| Volume | Weekly request count, backlog age, and repeat issue patterns | Assistant prepares, manager reviews |
| Risk | Access level, customer impact, security sensitivity, and approval needs | Technical owner |
| Cadence | Daily, weekly, monthly, or quarterly review rhythm | Manager |
| Evidence | Sample tickets, logs, screenshots, and before-after examples | Assistant collects, owner validates |
| Escalation | Triggers, approval path, response time, and stop-work rules | Technical owner |
How to read the result
A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.
Source and refresh note
This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.
How should teams use this benchmark?
Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.
Get free benchmark review