Once local admin rights are gone, IT managers are usually asked to show that removing them worked. The CISO wants evidence that risk has dropped, and the rest of the business wants to know productivity hasn’t suffered for it.
“Nobody’s complained lately” isn’t something you can put in a report, and neither is “we turned it on.” Showing both sides takes numbers you’ve tracked from the start, ideally with a baseline from before rollout.
A least privilege program produces plenty of data. The useful part is picking a handful of metrics that tell a clear story, and knowing what a good or bad reading looks like for each one.
Count the Admin Accounts Still on Your Devices
This is the metric that proves the core job got done. If the goal was to remove standing admin rights, the number of accounts that still hold them is your scoreboard. NSA and CISA list improper separation of user and administrator privilege among the most common misconfigurations their red and blue teams find, and they recommend limiting admin accounts and auditing them routinely.
The risk is easy to explain upward. In the 2026 Verizon Data Breach Investigations Report, software vulnerabilities overtook stolen passwords as the top way attackers get in, at 31% of breaches. When an exploited app runs under an account with local admin rights, the attacker gets those rights too.
In Admin By Request EPM, the Local Admins panel on the Reports page lists every account that currently holds local admin rights across your endpoints, and you can revoke them from the portal instead of visiting each device. A healthy reading is a short list of necessary service and system accounts. Regular user accounts on that list need reviewing, and a sudden bump usually means new devices arrived with default admin accounts nobody caught during setup.

Track Elevation Requests Over Time
Request volume is the clearest sign of how the program is settling in. Expect it to run high in the first weeks after rights are removed, then ease off as you approve the apps people use every day and turn them into rules. A line that keeps climbing month after month deserves a closer look, since it can mean more users have elevation access than you intended.
The Reports Dashboard tech note walks through the charts that cover this. User Requests plots requests over time and User Elevations plots completed elevations, both split by type. When the two lines track closely, approvals are flowing. A steady gap means requests are being denied or left sitting, which can point to approvers missing notifications or users giving up and finding another way around.
Who’s asking counts as much as how often. The Elevated Users panel ranks users by how many times they’ve elevated, and a few developers or IT staff near the top is normal. Standard users with no obvious business reason at the top of the list are the outliers to review, which makes this panel a handy input for periodic access reviews.
Measure How Much of the Approval Work Is Automated
Every manual approval costs someone time, so the balance between automated and manual decisions is a good proxy for efficiency. These approval metrics are worth a line in your monthly report:
- Share of requests auto-approved: how many went through pre-approval, Machine Learning or AI Approval without waiting for a person.
- Approval turnaround: the time between a user asking and getting an answer. Slow approvals push people toward workarounds.
- Denied and blocked requests: elevations refused by an approver or stopped by malware scanning.
- Approver spread: how evenly approvals are shared across your team.
Rising automation is a good sign as long as it comes from deliberate rules. The Elevated Applications panel shows which apps are elevated most often, and any app that keeps appearing without a pre-approval rule is manual work your team doesn’t need to be doing. Our guide on how privilege management can be automated covers how the three approval methods fit together.
For turnaround, the Auditlog API includes request time and response time fields for each entry, so you can calculate it in whatever reporting tool you already use. Approver spread comes straight from the Approver Activity panel. If one person handles nearly every request, that’s a single point of failure, and requests pile up the moment they’re on leave.
Denials and blocks need context to read well. A handful of denied requests and the occasional malware block are what a working control looks like. The Malware Detection panel shows elevation attempts flagged or blocked by OPSWAT MetaDefender, though an empty panel is only good news if the feature is switched on.
Watch What the Helpdesk Sees
Helpdesk tickets are where users tell you, indirectly, whether least privilege is getting in their way. Take a baseline of admin-related tickets (software installs, printer setup, driver updates) before rollout, then track the same categories afterward. We’ve written about why IT is drowning in tickets under permanent admin rights, and ticket volume is often the number that gets a CFO’s attention.
A short spike right after rights are removed is normal. What you want to see is that count falling back below the baseline as automation picks up the routine requests. If it stays high, check it against approval turnaround and the gap between requests and completed elevations, since the three tend to move together.
Keep an Eye on the Exceptions
Break Glass and Admin Session are the broadest forms of elevation, so their usage deserves its own line in the report. A Break Glass account is a one-time-use local admin account for when normal admin paths are unavailable, and all privileged activity in that session is logged to the Auditlog. Usage should be rare. A regular pattern suggests something in the normal workflow is broken, such as an agent problem or a team without a proper approval route.
Admin Session gives a user time-limited, system-wide admin rights, while Run As Admin elevates a single application. The User Elevations chart splits activity by type, and if Admin Sessions make up a large share, it’s worth asking whether those users could get by with Run As Admin. The User Installs chart fills in the detail, showing what was installed, by whom and on which computer.

Turning the Numbers Into a Report
Raw charts don’t make a report on their own. Pick a regular cadence (monthly for operations, quarterly for leadership) and show trends against your baseline rather than single snapshots. The Reports page has a Mail Me This View button that emails you a snapshot of the dashboard, which is useful for stakeholders without portal access.
For audit evidence, the Security Score rates your EPM settings out of 1,000 against a set of best practices, and its drill-down page exports to PDF. Exporting it quarterly gives you a timestamped record of your posture, which pairs well with a privileged access policy that holds up under scrutiny. If your security team already works in a SIEM or Power BI, the free REST API can feed audit log, request and inventory data straight in.
Proof You Can Point To
A least privilege program that works leaves a trail: fewer admin accounts, request volume that settles into a steady rhythm, more approvals handled automatically and a helpdesk that isn’t buried. Tracking those numbers from day one is what lets you prove it, and it helps you catch problems while they’re still small. If you’re not there yet, start by avoiding the common mistakes when removing admin rights.
To see these reports with your own data, our EPM solution’s Free Plan covers 25 endpoints with the full feature set, free forever. If you’d rather have a guided tour, book a live demo and we’ll walk you through the Reports Dashboard.