research

Auditing which devices still run unsupported operating systems

A repeatable audit that finds devices past their operating system support date, separates them from devices that merely look old, and estimates the exposed population.

Short answer

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

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

Verification sample10 devicesStudy protocol
Risk groups3 tiersStudy protocol
Review cadenceQuarterlyStudy protocol

Key takeaways

An unsupported operating system keeps working after the vendor stops issuing fixes, which is exactly why it is easy to ignore. The device boots, the user opens the usual applications, and no alarm sounds on the day support ends. This audit finds those devices from the management console and the asset register, then separates them from machines that are old but still supported. The output gives the IT owner a defensible count and a list of devices to replace or isolate.

Question and scope

This audit asks how many managed devices run an operating system that is past its vendor support date, and which business functions depend on them. The unit is one device with one installed operating system version. The population is every laptop, desktop, and server that the company manages, including devices used by contractors. The result describes that estate on the audit date and does not predict when the next device will fall out of support.

Freeze the device list and the audit date before exporting versions. Include devices that have not checked in for a long time, because an absent device may still be in use. Exclude personal devices that only access web mail unless policy treats them as managed endpoints. Record the exclusion rule so the count can be rebuilt.

Define supported

Define support by the vendor's published lifecycle page for the exact edition and release, not by the general product name. An edition can lose support on a different date from its sibling. Record the lifecycle source and the date it was read. A definition based on a blog post or an old internal note will not survive a challenge.

Distinguish mainstream support, extended support, and end of security updates, because the risk changes at each boundary. A device in extended support may still receive security fixes but not feature updates. Say which boundary the audit uses and apply it to every device. If the company has a stricter internal standard, measure against that standard as well.

Build the device frame

Export the device name, the operating system and version, the build number, the last check-in time, and the assigned user from the management console. Join it to the asset register on a stable key such as the serial number or the asset tag. Add the device group and the business unit so a finding can be routed. A frame built from one system alone will miss the devices that system does not manage.

Record devices that appear in the asset register but not in the console, and devices in the console with no asset record. Both gaps need a note before the support count is calculated. A device that is missing from the console may still be running an unsupported system. Keep the two lists beside the main export rather than silently merging them.

Verify the inventory

Check a sample of ten devices directly on the endpoint or through a remote query. Compare the reported version with the console record. A stale management agent can report an old version long after an upgrade, and a manual install can leave the console behind. Record every mismatch and the method used to resolve it. The verified sample gives the audit a known error rate.

Ask the service desk for devices that were reimaged or replaced in the last quarter. A replacement that was not closed in the asset register can inflate the unsupported count. Confirm the disposal record for any device that is listed as retired. The goal is a clean denominator, not a dramatic number.

Classify by risk

Group the unsupported devices by the data they can reach and the network they sit on. A device used only for a lobby display carries less risk than one with access to finance or customer records. Note whether the device has disk encryption, endpoint protection, and a supported browser. An unsupported system with a current browser is still a risk, but the compensating controls belong in the record.

Record the business owner for each group and the reason the device remains in service. A line-of-business application that refuses to run on a newer system is a different problem from a device nobody has replaced. The classification should point to a decision: replace, isolate, or accept with a written exception. Record that proposed decision beside the group so the report has a next step.

Sample and confirm

Select a random sample of the unsupported devices and confirm the version, the support status, and the business use. Include at least one device from each risk group. Check the vendor lifecycle page again on the day of confirmation so the status is current. A sample that is never confirmed is only a console export.

For each sampled device, record whether a replacement is already on order, whether the user has been told, and what compensating controls are active. Note the date of the last security update the device received. This turns a list of versions into a short set of case notes that the owner can act on. Keep the notes with the audit file so the next reviewer can see how each case was resolved.

Estimate the exposed population

Count the confirmed unsupported devices and report the share of the managed estate. Give a range that reflects the devices with incomplete records rather than a single precise figure. Break the count down by operating system family and by business unit. A percentage without the underlying counts is difficult to verify.

Separate devices that are past security support from devices that are merely past feature support. Combine them only in a clearly labeled total. Report devices with no recent check-in as an unknown group rather than counting them as supported. The unknown group is often the most important number in the report.

Compare with the refresh plan

Compare the unsupported count with the devices already scheduled for replacement in the current budget year. Identify the gap between the plan and the audit finding. Check whether the refresh plan uses the same lifecycle dates as the audit. A plan built on a different support definition will understate the work.

For devices that will remain past support, ask the owner for a written exception with an end date and a compensating control. Note the exception in the audit so the next measurement can track it. Report the cost of accelerating the replacement separately from the risk of waiting. The comparison turns the audit into a budget conversation rather than a compliance exercise.

Report to the owner

Lead with the number of confirmed unsupported devices, the share of the estate, and the unknown group. Show the risk groups and the devices with the nearest support deadlines. Add one example of a device that is still in daily use and one that could be retired without replacement. Keep the technical detail in an appendix for the desktop team.

Ask for a decision on the devices that cannot be replaced this quarter, including whether to isolate them or accept the risk in writing. Name the owner and the review date. If the decision is to accept, record the compensating controls and the next audit date. The report should leave the reader with a short list of actions, not just a version table.

Limits and next use

The audit counts devices that appear in the management console or the asset register and can be confirmed. It may miss a device that is powered off, off the network, or managed by a business unit outside the central process. It also cannot prove that an unsupported device has been exploited. State those limits so the result is read as an inventory finding rather than a breach report.

Repeat the audit each quarter and compare the same risk groups. If the unsupported count falls but the unknown group grows, the management coverage is getting worse rather than better. Record the lifecycle source date so a later reviewer can tell whether the definition changed. The audit becomes useful when the trend is read beside the replacement plan.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the identity, platform support, request intake, data export, and licence inventory controls 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 access revocation measurement and the software licence entitlement audit 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

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the auditing which devices still run unsupported operating systems 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

1

Collect a baseline

Pull the last 30 to 90 days of examples related to auditing which devices still run unsupported operating systems, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
Verification sample10 devicesStudy protocol
Risk groups3 tiersStudy protocol
Review cadenceQuarterlyStudy protocol

Sources

  1. NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management PlanningPatch management planning, maintenance, and end-of-support considerations.
  2. NIST SP 800-53 Rev. 5Configuration management, flaw remediation, and asset inventory controls.
  3. CISA Cross-Sector Cybersecurity Performance GoalsAsset inventory and vulnerability management goals for small organizations.
  4. NIST Cybersecurity Framework 2.0Asset management and platform security outcomes for device fleets.
  5. GAO Assessing Data ReliabilitySampling and reconciliation checks for inventory-based estimates.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical 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