research
Measuring the age of privileged accounts that are never used
An audit method for finding privileged accounts with no recent activity and measuring their age, ownership, and exposure.
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 privileged account that nobody uses still carries the ability to change systems, read data, or create new administrators. It sits outside the daily routine, so it rarely appears in access reviews that focus on active staff. This study measures the age and exposure of privileged accounts with no recent activity. The result helps the identity team decide which accounts to remove, convert, or monitor.
Question and scope
The study asks how many privileged accounts have no recorded use in the review period and how long they have held that privilege. The unit is one account in one system, such as a directory administrator, a cloud role, or a local administrator login. The population is every account with a privileged role in the identity inventory plus any privileged account found during the review. The result describes that inventory and period.
Exclude break-glass accounts that are intentionally dormant but tested on a schedule, and count them separately. Include service accounts only when a person can sign in interactively with them. Record the exclusion rule and the test evidence. A dormant account with a current test record is different from one nobody has touched.
Define privileged and unused
Treat an account as privileged when it can change permissions, create or delete accounts, read sensitive data across teams, or alter security settings. Record the specific role or group that grants the privilege. A job title is not evidence of privilege. The role assignment is what matters for the audit.
Treat an account as unused when it has no successful interactive sign-in during the review period, excluding automated health checks and scheduled tasks. State the period, such as ninety days. A shorter period will classify seasonal accounts as unused, so note the seasonality. The definition should be applied to every system in the same way.
Build the account frame
Export privileged role assignments from the directory, the cloud console, and the application administrators. Match them by account identifier and display name. Add the role, the system, the creation date, and the owner field. A frame built from one console will miss local administrators and vendor-managed roles.
Attach the last successful interactive sign-in and the last password or key rotation date. Note whether the account is enabled and whether it can bypass multi-factor authentication. These fields change the risk of a dormant account. Keep the raw export with the review record so the counts can be rebuilt.
Verify with authentication logs
Check the sign-in logs for each account rather than trusting the owner field or the last-login field in the console. Some systems show the last interactive sign-in while ignoring application tokens. Look for successful and failed attempts, and note the source address. A failed attempt from an unknown location is a finding even when the account is dormant.
Match the sign-in time with scheduled jobs and monitoring checks. An account used only by automation should be converted to a service identity with limited scope, not left as an interactive administrator. Record the job and the owner for each automated use. The distinction prevents a real service account from being disabled as unused.
Measure age and exposure
For each unused privileged account, calculate the days since the last successful interactive sign-in and the days since the role was assigned. Report the median and the oldest case. Split the result by privilege level and by system. A dormant domain administrator and a dormant reporting role are not the same risk.
Count the accounts that can bypass multi-factor authentication, export data, or create other administrators. Those capabilities define the exposure even when the account is quiet. Note whether the account has a named owner and a documented purpose. The combination of no use, no owner, and high capability is the priority group.
Sample for owner confirmation
Send the owner of each high-risk dormant account a short request to confirm the purpose or approve removal. Include the last sign-in date, the role, and the systems it can reach. Ask for a response within five working days. A non-response is recorded as unconfirmed, not as approval to keep the account.
For accounts with no owner, ask the system owner and the team that most recently used the role. Check the ticket history for the request that created the account. If no one claims it, mark it as orphaned. Confirm that disabling it will not break an integration before taking action.
Report and remediate
Give each system owner a list of dormant and orphaned privileged accounts with the evidence behind each one. Ask for a decision to remove the role, disable the account, convert it to a service identity, or document a tested exception. Set a date for the decision and a second date for verification. The report should end with named actions.
For accounts that must remain, require an owner, a purpose, a review cadence, and a test record. Reduce the privilege to the minimum the purpose needs. Rotate the credential and confirm the rotation. Record the change in the ticket and update the inventory. Remediation is complete when the next export shows the reduced role.
Check the approval path
For each privileged role, find the request or ticket that granted it and the person who approved. A role with no approval record is a finding even when the account is active and used. Check whether the approval named the specific system and the duration. A general request for admin access is not evidence that this role was reviewed.
Compare the approval date with the role assignment date. A role added before the approval, or never approved, should be flagged separately from a dormant account. Record the approver and the business reason. The path matters because a dormant account with a clean approval can be removed quietly, while an unapproved one needs a broader review.
Account for vendor-managed roles
Vendors and managed service providers often hold privileged accounts that never appear in the staff directory. Ask each vendor for its current account list and compare it with the roles the company can see. Include accounts used for support sessions and remote monitoring. A vendor account that is dormant is still an entry point.
Confirm the contract end date and the offboarding step for each vendor. Record the person who can disable the account and the notice required. Review vendor roles on the same cadence as staff roles. The inventory should show every privileged path, including the ones the company does not administer.
Use the result in the access review
Add dormant privileged accounts to the standing access review instead of running a separate project each time. Give the reviewer the last sign-in date, the role, and the owner confirmation in one view. Set a decision rule for accounts with no use and no owner. The review should produce removals, not another list.
Review the vendor roles in the same meeting as staff roles so the full privileged path is visible. Ask each system owner to confirm the accounts that remain. Record the exception and its test date. The access review becomes the control that keeps the dormant count from returning.
Keep the owner confirmation with the role record so the next review does not start from an empty field. A short note that names the person and the date is enough. Ask the system owner to confirm the account is still needed before the review closes. The record should show a decision, not only a check.
Limits and next use
The study measures accounts visible in the identity and application inventories and the sign-in logs that were available. It cannot see a local account on an unmanaged device or a credential shared outside the directory. It also cannot prove that an unused account is safe to remove without a dependency check. State these limits so the result is read as a prioritisation tool.
Repeat the study each quarter and compare the same privilege groups. If the dormant count falls but the number of exceptions rises, the team may be relabelling rather than removing access. Keep the method with the access review. The measure is working when the oldest high-risk accounts disappear from the list.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the DNS change, recovery key, software trial, privileged account, and forwarding rule 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 privileged account age audit and the mailbox forwarding survival 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 measuring the age of privileged accounts that are never used 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 measuring the age of privileged accounts that are never used, 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 |
|---|---|---|
| Review period | 90 days | Study protocol |
| Priority signals | 3 combined | Study protocol |
| Unit | Privileged account | Study protocol |
Sources
- CISA Cross-Sector Cybersecurity Performance GoalsIdentity and access goals for privileged account management.
- NIST Cybersecurity Framework 2.0Identity management and access control outcomes for dormant accounts.
- NIST SP 800-53 Rev. 5, Security and Privacy ControlsAccess enforcement and audit requirements behind the role review.
- NIST SP 800-63B, Digital Identity GuidelinesAuthenticator and account recovery guidance for privileged sign-in 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