research
Auditing the accuracy of the asset register against the endpoint agent
A reconciliation method that matches register records to endpoint observations, classifies each mismatch, and measures the error groups behind the match rate.
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
An asset register is only useful when it matches the devices that actually connect to the network. The register says one thing, the endpoint agent says another, and the gap is where unmanaged devices and stale records live. This audit compares the two sources and classifies every mismatch. The result gives the team a short list of records to fix and devices to investigate.
Question and scope
The audit asks how many asset records disagree with the endpoint inventory and what kinds of error cause the difference. The unit is one device identity, matched across the register and the agent. The population is the devices in the chosen business unit or site. The result describes the accuracy of that register at the time of the export.
Include servers, laptops, and mobile devices that run the agent, and note the devices that cannot run it. Exclude virtual machines that are created and destroyed within the export window unless they hold a persistent role. Record the scope and the export time before matching anything. A moving inventory needs a fixed snapshot to compare.
Choose comparison sources
Use the register as the book of record and the endpoint console as the observation. Add the network access control list or the DHCP lease table as a third source for devices that never installed the agent. Each source has a different lag, so record the export time for all of them. A comparison with mismatched timestamps creates false differences.
Check the field mapping before the audit, such as hostname, serial number, and device owner. Decide which field is the primary key and which fields are supporting evidence. A hostname can change, so a serial number is usually stronger. Write the matching rule so another analyst can reproduce the result.
Define a match
Treat a record as matched when the primary key is identical in both sources and the device type agrees. A serial number match with a different hostname is still a match, but the hostname difference is a finding. A hostname match with a different serial number is a possible duplicate or a rebuilt device. Classify the case rather than forcing it into a match.
Review the records that match only after normalization, such as a serial number with a prefix or a lowercase hostname. Keep the original values in the evidence. Note whether the register or the agent is likely to be correct. The classification should explain the error, not just count it.
Sample and inspect
If the population is large, sample across device types, sites, and record ages. Pull the full record for each sampled device and check the owner, location, and status. Compare the last seen time in the agent with the last update in the register. A record that has not changed in a year is a candidate for a stale entry.
Inspect a few unmatched devices on the network to see whether they are real and unmanaged, retired, or duplicated. Use the switch port, the wireless controller, or the user report to locate them. Do not disable a device before confirming what it is. An unmatched record can be a missing agent rather than a missing device.
Measure the error types
Group the differences into missing from register, missing from agent, duplicate record, wrong owner, wrong location, and wrong status. Count each group and calculate its share of the sample. The groups point to different fixes, such as an import rule, a decommission step, or an owner update. A single accuracy percentage would hide those differences.
Estimate the total error count from the sample only when the sample is random and large enough. Otherwise report the sample counts and label the estimate as provisional. Show the confidence range if one is calculated. Do not present a sample result as a full census.
Assign owners
Give every error group an owner who can correct it, such as the service desk for owner fields and the endpoint team for missing agents. Set a target date for each group rather than one date for the whole list. Record the correction in the register and the ticket. An error with no owner returns at the next audit.
For devices that cannot run the agent, record the reason and a compensating control. For duplicate records, merge them with a note that keeps the history. For retired devices, mark the record as retired instead of deleting it. The register should show what happened, not just the current state.
Report and recheck
Report the match rate, the error counts by type, and the number of unmanaged devices found. Add one example of a device that was on the network but missing from the register. Ask for a decision on the import and decommission steps that caused the largest group. Keep the report short enough for an operations meeting.
Recheck the same sample after the corrections and compare the error types. If the match rate improves but duplicates remain, the merge rule needs work. Record the recheck date and the person who ran it. The second measurement shows whether the fix changed the process or only the list.
Limits and next use
The audit compares records at one point in time and cannot see a device that was never observed by any source. It also depends on the quality of the primary key, which may be missing on older hardware. A device that connects only through a guest network may not appear in the agent data. State these limits with the result.
Repeat the audit quarterly and track the error groups rather than a single score. If the same group persists, change the process that creates the record. Keep the matching rule and the sample with the report. Accuracy improves when the audit feeds the workflow that maintains the register.
Check the change history
Pull the change history for a sample of mismatched records and look for the step that created the error. A device that was rebuilt may keep an old serial number, while a loan laptop may move between owners without an update. Note whether the error came from a manual entry, an import, or a missing decommission step. The history explains why the register drifted.
Compare the history with the ticket that requested the change. If the ticket closed without a register update, the process has a gap at the handoff rather than at the data entry. Ask the technician who closed the ticket what would have made the update easier. The answer is often a required field or a linked form.
Feed the result into procurement
Share the error groups with the team that buys and retires hardware. A register that misses new devices may need an import from the purchase order, while a register full of retired devices may need a decommission step. Ask for one process change that removes the largest group. Measure the same group at the next audit.
Include the register accuracy result in the quarterly technology review. A match rate without the error groups does not tell the business what to fix. Name the owner, the change, and the date for the next check. The register becomes trusted when the people who update it see the result of their work.
Keep the comparison repeatable
Save the export, the matching script, and the normalization rules with the report. A reviewer should be able to rerun the comparison without rebuilding the logic from memory. Note the fields that changed between cycles and why. A repeatable method makes the next audit a comparison rather than a new project. Store the script in version control so an older run can be reproduced after a rule change.
Test the matching rule on a small set of known devices before running the full population. Include one duplicate, one retired device, and one device with a missing serial number. If the rule cannot classify those cases, adjust it before the result is published. A rule that only works on clean data will fail in the real register. Write down any known limitation of the rule and revisit it next cycle.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the renewal, shared account, backup, asset register, and access ticket controls discussed here. The NIST SP 800-53 Rev. 5 supports the account 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 shared account ownership audit and the backup check coverage 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 the accuracy of the asset register against the endpoint agent 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 the accuracy of the asset register against the endpoint agent, 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 |
|---|---|---|
| Comparison sources | 2 or more | Study protocol |
| Sample floor | 25 devices | Study protocol |
| Error groups | 6 types | Study protocol |
Sources
- NIST SP 800-128, Guide for Security-Focused Configuration ManagementConfiguration item records and inventory accuracy practices.
- NIST Cybersecurity Framework 2.0Asset management outcomes for identifying and maintaining inventory.
- CISA Cross-Sector Cybersecurity Performance GoalsAsset inventory goals that depend on accurate device records.
- GAO Assessing Data ReliabilitySampling and reconciliation checks for comparing two data sources.
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