research
Auditing which staff laptops still have a local administrator account
A method for counting active local administrator accounts on staff laptops, verifying the collection, and separating documented support needs from unmanaged access.
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 local administrator account on a staff laptop is a second set of keys that nobody records. It may be created by a setup script, an old support visit, or an application that demanded elevation during installation. The account rarely appears in the identity provider, which makes it invisible to joiner and leaver processes. This audit counts the laptops with active local administrator accounts and checks whether each one has a written reason.
Question and scope
The audit asks which staff laptops have at least one enabled account in the local administrators group, and whether that access is documented and still needed. The unit is one laptop. The population is every portable device assigned to a named employee on the audit date. The result describes the local configuration of those devices, not the domain or cloud administrator roles. Record the operating system version because account defaults differ between releases.
Include devices managed by the company even when the user bought them through a stipend. Exclude servers and shared lab machines, but note how many exist. Record the management tool used to collect the data and whether it has full coverage. A laptop that is missing from the console may still hold a local administrator account, so list the missing devices as a separate gap.
Define local administrator
Define a local administrator as an enabled account that belongs to the built-in administrators group or holds equivalent rights through a policy. Check whether the account is named, shared, or created by the device vendor. Note whether it has a password set and when the password was last changed. Record the distinction between a disabled account and a deleted one because the audit should count only active rights.
Separate the built-in administrator account from vendor support accounts and from the user's own daily account. A daily account with administrator rights is different from a separate recovery account used only for repairs. Note whether the device allows elevation without a separate credential. The definition should be written before the collection so two reviewers count the same thing. Write one example of an acceptable exception beside the definition so the boundary is visible.
Build the device frame
Export the device list from the management console and match it to the asset register. Include the assigned user, the department, the operating system, and the last check-in date. Remove devices that have not checked in for thirty days and investigate them separately. A stale record can make the audit look complete when a large part of the fleet is unreachable.
Add the devices that appear in the asset register but not in the console. Ask the user or the team lead whether the device is still in service. Record the answer and the date. List the devices that cannot be reached and the reason. The frame should show both what was measured and what could not be measured. Give the list to the asset owner and ask them to close the records that are wrong.
Collect group membership
Use the management tool to run a read-only query against the local administrators group on each device. Capture the group name, the account names, the enabled state, and the last logon where available. Export the raw output before any summary. Keep the query and the date with the export so a reviewer can repeat it. A screenshot of one laptop is not a fleet measurement.
Check the query results for duplicates caused by multiple collection runs. Normalise the account names so a domain account and a local account with the same name are not merged. Note the devices that returned an error and rerun the query once. Record the error count and the reason. A missing result is a finding, not a zero. Keep the error list with the export so the next reviewer can see what was missed.
Sample and verify
Select at least ten percent of the devices and open the local users and groups screen or run the query again directly. Compare the live result with the export. Record any difference and the likely cause, such as a policy change or a delayed check-in. The sample tests whether the collection method is trustworthy. Repeat the direct check on a second device when the first result differs from the export.
Choose the sample across departments, device models, and operating system versions. Include at least two devices that reported no local administrators. Ask the user to confirm whether they have ever used an administrator password. A user who knows the password is evidence that the access is in use, even if the account is rarely logged. Record the user's answer in the audit file and note how they use the administrator password.
Separate legitimate needs
List the business reasons that justify a local administrator account, such as a specific engineering tool, an offline recovery requirement, or a legacy application that cannot run without elevation. Ask the technical owner to confirm each reason in writing. Record the expiry date and the review owner. A reason that cannot be written down is usually a habit rather than a requirement.
Check whether the need can be met with a managed support account that is enabled only during a repair. Note the process for enabling and disabling it and whether the action is logged. A permanent local administrator account created for a one-time install should be removed after the install. The audit should recommend the smallest access that satisfies the documented need.
Measure exposure
Count the laptops with at least one active local administrator account and report the share of the measured fleet. Split the count by named user accounts, vendor accounts, and shared accounts. Report the number of devices where the user knows the password. These categories carry different risk and should not be collapsed into one number. Add the count of devices with more than one administrator account as a separate line.
Add the age of the account and the date of the last password change where the tool records it. An account that has never been used still expands the attack surface if its password is weak or shared. Note the devices that are missing disk encryption or endpoint protection as a separate exposure. The report should show where the risk concentrates, not only the total.
Report and remediate
Write a short report with the method, the measured population, the share of devices with local administrator accounts, and the documented exceptions. Group the findings by department and by device model. Avoid naming individual users in the summary and use asset identifiers instead. Attach the raw export and the sample verification sheet. Send the draft to the technical owner and give them two working days to correct the facts.
Assign an owner and a due date to each finding. Start with accounts that have no documented reason, then the shared accounts, then the exceptions that need a review date. Record the removal method and the test that confirms the account is gone. A finding is closed only when the device shows the corrected state. Ask the device owner to confirm the removal and record the confirmation date.
Repeat after changes
Rerun the audit after a policy change, an operating system upgrade, or a support contract change. A new setup script can recreate the account that was removed. A vendor tool can add a support account during an update. Compare the new share with the previous result and investigate any increase. Note the change that triggered the rerun beside the new export.
Keep the query and the export with the endpoint documentation. Set a quarterly review and a shorter monthly check of new devices. Record the date and the person who ran it. A stable share with documented exceptions is a better result than a one-time clean number. Store the quarterly result beside the previous one so the trend is easy to read.
Limits of the audit
The audit sees the local accounts that the management tool can query. It cannot see a device that is powered off, offline, or outside the console. It also cannot prove that a password has never been shared or written down. State these limits so the report is read as a configuration review, not a guarantee. Name the systems that were out of scope so a reader does not assume the whole estate was covered.
The sample may miss a device that changes after the collection date. Repeat the audit after a large deployment or a staff change. The method measures presence, not intent. Use the documented reasons and the interviews to interpret the number, and keep the raw export for anyone who wants to check the result. Record the next audit date and the person who will run it before closing the report.
Interview the device owners
Ask five users whether they have ever used an administrator password and how they got it. Record the answer without judging the person, because the answer explains how the account spreads. Ask the team lead whether a support visit created the account and whether anyone documented it. Compare the answers with the management export. Ask the team lead whether the support visit was logged in the ticket system.
Include the person who supports the devices and the person who approved the last purchase. Ask whether the setup script still creates the account and where the script is stored. A script that runs on every new laptop will rebuild the access after each cleanup. Record the script owner and the change process. Keep the script and its change history with the endpoint build documentation.
Keep the evidence usable
Store the export, the query, the sample sheet, and the report in one folder with the audit date. Name the files by date and scope rather than by the person who ran the audit. Give read access to the technical owner and the person who will run the next review. A folder that only one person can open will not survive a staff change.
Write a one-page method note that explains how to repeat the query and where to find the definitions. Add the known limitations and the systems that were out of scope. Include the date of the last run and the next planned date. The note should let a new reviewer reproduce the result without asking the original author. Add the method note to the audit folder and link it from the endpoint runbook.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the local administrator, password reset, vendor case, file restore, and browser credential measures discussed here. The NIST SP 800-63B digital identity guidance supports the verification and credential checks, NIST SP 800-34 contingency planning guidance supports the restore measure, and the GAO data reliability guidance supports the sampling approach. Apply your own policies, contracts, and system documentation when adapting the method.
Compare this study with the local administrator audit and the file restore timing 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 which staff laptops still have a local administrator account 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 which staff laptops still have a local administrator account, 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 laptop | Study protocol |
| Verification sample | 10 percent | Study protocol |
| Review cadence | Quarterly | Study protocol |
Sources
- NIST SP 800-53 Rev. 5, Security and Privacy ControlsAccess enforcement and least-privilege control language used to define the audit.
- CISA Cross-Sector Cybersecurity Performance GoalsBaseline account and privilege controls for small organisations.
- NIST Cybersecurity Framework 2.0Identify and protect outcomes used to frame the device inventory.
- CISA Cyber EssentialsPractical starting points for account and device hygiene.
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