
Endpoint Inventory and Software Audit Checklist for IT Teams
An endpoint inventory tells IT teams which devices they manage, what hardware those devices contain, and which software applications are installed. A software audit takes that information further by checking whether applications are authorized, supported, appropriately licensed, and consistent with organizational security requirements.
Without accurate records, organizations risk overlooking unmanaged devices, missing vulnerable software, paying for unused licenses, and making infrastructure decisions based on outdated information.
This guide provides a practical endpoint inventory and software audit checklist for IT teams and managed service providers (MSPs). It covers what information to collect, how to identify discrepancies, how to prioritize corrective actions, and how to maintain accurate records as environments change.
What Is an Endpoint Inventory?
An endpoint inventory is a structured record of devices within an organization's IT environment. It typically includes computers, servers, and other managed endpoints, along with information about their hardware, operating systems, assigned users, and management status.
A useful inventory answers several questions:
- How many endpoints does the organization manage?
- Which operating systems and hardware configurations are deployed?
- Who is responsible for each device?
- Which endpoints are actively reporting to management systems?
- Which devices are approaching replacement or retirement?
- Are any devices missing required monitoring or security controls?
- Are unauthorized devices connected to organizational networks?
An endpoint inventory is one component of broader IT asset management, which also covers procurement, ownership, financial records, maintenance, and retirement.
Endpoint Inventory vs. Software Audit
Although closely related, endpoint inventories and software audits have different purposes.
Endpoint Inventory | Software Audit |
Identifies and records managed devices | Examines applications installed on or associated with those devices |
Tracks hardware specifications and operating systems | Checks application versions, authorization, support, and licensing |
Establishes device ownership and lifecycle status | Identifies unnecessary, unauthorized, or outdated software |
Supports maintenance and replacement planning | Supports application security, compliance, and license management |
Answers which devices exist and how they are configured | Answers whether the software environment meets organizational requirements |
The two processes are most effective when connected. A software audit cannot reliably cover every endpoint if the underlying device inventory is incomplete.
Why Accurate Hardware and Software Inventories Matter
1. Improved Security Visibility
Security teams need to know which systems and applications exist before they can consistently assess their exposure.
An incomplete inventory can leave devices outside patching schedules, security monitoring, and incident response workflows. Similarly, unrecorded software may contain vulnerabilities that remain unnoticed.
The NIST Cybersecurity Framework 2.0 explicitly addresses hardware inventory under ID.AM-01 and software, systems, and services inventory under ID.AM-02.
Maintaining these records helps organizations identify assets requiring protection and establish a foundation for vulnerability and risk management.
However, identifying installed software is not the same as identifying vulnerabilities. IT teams must also evaluate versions, vendor advisories, configurations, and applicable vulnerability intelligence.
2. Better IT Asset Management
Hardware inventories support decisions throughout the device lifecycle.
IT teams can use hardware specifications, operating system information, purchase records, and device condition to determine which systems need maintenance, upgrades, reassignment, or retirement.
For example, a device with limited memory and insufficient storage may struggle with increasingly demanding business applications. Accurate records help determine whether upgrading the device is practical or whether replacement makes more sense.
3. Software License and Compliance Management
Software audits help organizations reconcile installed applications and user entitlements with purchasing and licensing records.
An audit may identify:
- Applications installed without approval.
- Software versions no longer supported by their vendors.
- Licenses assigned to employees who no longer need them.
- Installations exceeding contractual entitlements.
- Subscription products with overlapping functionality.
- Applications requiring additional documentation for regulatory or contractual reviews.
Installation counts alone do not establish license compliance. Licensing models may depend on named users, devices, processors, concurrent usage, subscriptions, or other contractual terms.
A reliable audit therefore combines technical discovery with purchasing records, vendor agreements, and entitlement information.
4. More Reliable Operational Planning
Accurate inventories provide useful information for budgeting and capacity planning.
IT managers can identify aging hardware, plan operating system upgrades, estimate replacement requirements, and evaluate software consolidation opportunities.
For MSPs, this information also supports client reporting, onboarding, hardware refresh recommendations, and service planning.
Endpoint Inventory Checklist for IT Teams
The following checklist covers the information and verification activities needed to establish a reliable inventory.
1. Identify All Endpoints Within Scope
Start by defining the systems the inventory should cover.
Checklist:
- Identify all company-owned and managed workstations.
- Identify physical and virtual servers.
- Record remote and hybrid employee devices.
- Include supported Windows, macOS, and Linux endpoints.
- Identify mobile devices and personally owned devices within the organization's management scope.
- Identify network-connected devices requiring separate inventory processes.
- Review inactive, offline, and recently deployed systems.
- Compare discovered devices with procurement and assignment records.
- Identify devices detected on organizational networks that are not present in the approved inventory.
- Record devices whose authorization or ownership cannot be established.
Use more than one discovery source when necessary. Endpoint management platforms, directory services, device management systems, network discovery tools, and procurement records may reveal different parts of the environment.
An endpoint agent typically cannot report on a device where it has never been installed. This makes reconciliation important, particularly for newly acquired, disconnected, or unmanaged devices.
2. Record Essential Device Information
Each device should have a consistent set of identifying information.
Inventory Field | Purpose |
Asset ID | Unique organizational identifier |
Hostname | Identifies the device on a network |
Serial number | Helps identify physical hardware |
Manufacturer and model | Supports hardware identification and replacement planning |
Device type | Distinguishes workstations, servers, and other endpoints |
IP address | Helps identify the device's network connection; record static addresses where applicable |
MAC address | Provides a hardware network interface identifier where available |
Operating system and version | Supports compatibility and security reviews |
CPU | Helps assess processing capacity |
RAM | Supports performance and upgrade decisions |
Storage capacity and available space | Identifies capacity constraints |
Assigned user or department | Establishes operational ownership |
Asset owner | Identifies the person or team accountable for the asset |
Authorization status | Identifies whether the device is approved to access organizational resources |
Management status | Indicates whether the device is enrolled and reporting |
Last seen | Shows the most recent management-system communication |
Last verified | Records when inventory details were last independently checked |
Lifecycle status | Records whether the asset is deployed, in storage, under repair, or retired |
These fields support the principles outlined in CIS Control 1.1: Establish and Maintain Detailed Enterprise Asset Inventory, which emphasizes identifiable assets, network information, ownership, and authorization.
Not every field is available through automated endpoint discovery.
For example, purchasing costs, warranty expiration dates, physical custody, and contractual ownership often come from procurement or asset management records rather than the endpoint itself.
IP addresses can also change, and devices may have multiple network interfaces. They should not be treated as permanent unique asset identifiers.
IT teams should establish which system is authoritative for each type of information.
3. Verify Hardware and Operating System Health
An inventory becomes more useful when its information supports operational decisions.
Checklist:
- Identify endpoints running unsupported operating systems.
- Review devices with consistently limited available storage.
- Identify hardware configurations below organizational standards.
- Review devices experiencing recurring hardware-related alerts.
- Identify equipment approaching planned replacement dates.
- Check whether required endpoint management tools are installed and operational.
- Flag devices with incomplete or outdated hardware information.
A device inventory can reveal relevant specifications and management status, but hardware failure risk requires additional evidence such as monitoring data, diagnostic results, and incident history.
An older device is not automatically unsuitable. Replacement decisions should consider workload requirements, support status, maintainability, security, and total cost.
For more detailed lifecycle considerations, see What Is Hardware Inventory Management?, which covers asset tracking from procurement through retirement.
4. Confirm Ownership and Lifecycle Status
Every asset should have an identifiable owner or responsible team.
Checklist:
- Confirm assigned users and departments.
- Reconcile device assignments with employee onboarding and offboarding records.
- Identify duplicate or unassigned asset records.
- Verify that decommissioned devices are no longer represented as active assets.
- Record retired equipment and disposition status.
- Confirm that required data sanitization and disposal procedures have been completed.
- Review unauthorized devices and document their investigation or disposition.
- Verify that asset ownership changes are reflected in the authoritative inventory.
Device retirement requires more than removing an endpoint from a management console.
Depending on the organization's requirements, retirement may involve data sanitization, account removal, software license recovery, disposal documentation, and updating financial asset records.
Software Audit Checklist for IT Teams
A software audit examines the applications present in an IT environment and evaluates whether they meet business, security, support, and licensing requirements.
The following checklist focuses on executing the audit. For ongoing software discovery, application governance, and inventory maintenance, see Software Inventory Management Best Practices.
1. Establish a Complete Software Inventory
Begin by collecting installed application information from managed endpoints.
Checklist:
- Identify installed applications on all covered endpoints.
- Record application names and publishers.
- Collect installed version information.
- Record initial installation or first-use dates where available.
- Identify operating system and application dependencies where relevant.
- Determine which endpoints have each application installed.
- Review applications installed under individual user accounts.
- Identify duplicate software products serving similar functions.
- Record applications that cannot be reliably identified.
Software discovery methods vary by operating system and management platform.
Some tools collect information from operating system installation records, while others use package managers, application databases, or additional discovery mechanisms. These methods may not detect every portable application, browser extension, container image, or user-managed cloud service.
For a complete organizational software inventory, endpoint discovery may need to be supplemented with browser management, identity, SaaS administration, and cloud asset information.
Distinguish installation counts from device counts. An application may appear more than once on a single device when it is installed separately for different user accounts.
For example, an application with 120 reported installations may be present on fewer than 120 distinct devices.
Installation count, unique device count, and required license quantity are separate measurements. License requirements must be determined from the applicable licensing agreement rather than inferred from raw installation totals.
2. Establish an Authorized Software Baseline
Before determining whether an application is unauthorized, IT teams need an established reference defining which applications are approved for organizational use.
An authorized software baseline, sometimes called an approved application catalog, documents permitted applications and their business purposes.
It also distinguishes software approved for general use from applications restricted to particular departments, roles, or devices.
Recommended software authorization fields:
Field | Audit Purpose |
Application name | Identifies the software product |
Publisher | Identifies the software provider |
Approved version or version policy | Defines applicable version requirements |
Business purpose | Explains why the application is needed |
Application owner | Identifies the responsible department or individual |
Authorization status | Records whether the application is approved, unauthorized, or under review |
Approval authority | Identifies who authorized the application |
Approved device or user scope | Defines where the application may be used |
Installation or first-use date | Supports lifecycle and audit review |
Support status | Identifies whether the vendor continues to support the software |
Exception status | Records authorized deviations from standard policy |
Last verified date | Shows when the record was last reviewed |
The baseline should distinguish application approval from vendor support. An application may have a legitimate business purpose while still running an unsupported version that requires remediation or a formally approved exception.
Checklist:
- Maintain an approved software catalog.
- Assign a business owner to each approved application.
- Document acceptable application versions or support requirements.
- Define who can approve new software.
- Identify applications that require additional security review.
- Document restricted applications and authorized user groups.
- Establish a procedure for requesting exceptions.
- Review application authorizations when business needs or vendor support changes.
This approach aligns with CIS Control 2: Inventory and Control of Software Assets, particularly Safeguards 2.1 and 2.2.
3. Identify Unauthorized or Unnecessary Applications
Compare discovered applications against the organization's approved software catalog.
Checklist:
- Identify applications without an authorized business purpose.
- Review unapproved remote access and administration tools.
- Identify redundant software.
- Review applications installed outside approved deployment processes.
- Confirm ownership of unfamiliar applications.
- Identify software installed outside its approved device or user scope.
- Document approved exceptions.
- Assign remediation actions for unauthorized software.
Not every unfamiliar application is malicious.
An application may be required by a specific department, installed as a dependency, or authorized through an exception that has not yet been documented.
IT teams should verify its function and business need before removing it.
4. Review Software Versions and Vendor Support
Installed software information should be evaluated against vendor support policies and security advisories.
Checklist:
- Identify end-of-life and end-of-support applications.
- Review installed versions against vendor-supported releases.
- Identify applications affected by relevant security advisories.
- Determine whether security updates are available.
- Verify that patching responsibilities are assigned.
- Document applications that cannot be upgraded.
- Establish mitigation or replacement plans for unsupported software.
- Identify unsupported applications operating under approved exceptions.
- Confirm that exceptions include appropriate mitigating controls and accepted residual risk.
An outdated version does not necessarily contain a particular vulnerability, and a current version does not guarantee that an application is secure.
Version information must be interpreted alongside vendor advisories, deployment details, and the organization's exposure.
For organizations managing many devices, connecting software inventory to patch management workflows can make it easier to identify which endpoints require attention.
5. Reconcile Software Licenses and Entitlements
A license audit compares deployed or assigned software with the organization's contractual rights.
Checklist:
- Collect software procurement and subscription records.
- Review applicable license agreements.
- Reconcile installations, assignments, or usage with the relevant license model.
- Identify potentially unused subscriptions.
- Review licenses assigned to former employees.
- Identify potential overdeployment or entitlement shortfalls.
- Document findings requiring vendor or procurement verification.
Software inventory tools can help identify installations and versions, but they may not establish actual usage or contractual entitlement.
For example, a software title installed on 100 devices does not necessarily require 100 licenses. The answer depends on its license terms.
Likewise, removing an application does not always terminate an associated subscription.
License findings should be validated against the applicable agreements before financial or compliance conclusions are made.
6. Review Software Security and Configuration
Application security extends beyond identifying what is installed.
Checklist:
- Verify required endpoint security tools are active.
- Check the status of relevant security controls.
- Identify software requiring excessive privileges.
- Review potentially risky remote administration applications.
- Check for unsupported software dependencies.
- Confirm that software exceptions are documented.
- Review systems with missing or failed security controls.
A software inventory provides the starting point for these checks, but it does not replace endpoint protection, configuration assessment, vulnerability scanning, or formal security auditing.
How to Conduct an Endpoint Inventory and Software Audit
Collecting information is only the beginning. An effective audit should produce verified findings and assigned corrective actions.
Step 1: Define Audit Scope and Ownership
Determine which environments, client organizations, device groups, and software categories are included.
Identify the responsible IT owner and establish the expected audit outputs.
An MSP may conduct separate audits for each client, while an internal IT department may organize them by site, business unit, or system criticality.
Step 2: Collect Data From Available Sources
Gather data from endpoint management systems, directory services, procurement records, asset repositories, software administration consoles, and relevant network discovery tools.
Use consistent collection dates and timestamps so that records can be compared appropriately.
Step 3: Normalize and Reconcile Records
Different systems may represent the same asset differently.
For example, a device may appear under its hostname in an RMM platform, its serial number in an asset register, and an assigned employee's name in procurement records.
Use stable identifiers and documented matching rules to reconcile records without merging unrelated devices.
Flag uncertain matches for review rather than assuming they represent the same asset.
When records conflict, compare their timestamps, collection methods, and authoritative sources. An endpoint's current operating system version may be best established through recent device telemetry, while its purchasing information may be best established through procurement records.
Document unresolved discrepancies rather than silently replacing existing values.
Step 4: Evaluate Findings Against Defined Standards
Compare the collected information with internal policies and relevant external requirements.
Review management coverage, device support status, software authorization, licensing, and security controls.
The CIS Critical Security Controls v8.1 provide recognized guidance for enterprise asset inventory and software inventory management.
CIS Control 1 addresses enterprise assets, while Control 2 addresses software assets and authorization.
These controls can help IT teams establish structured review criteria, but adopting an inventory tool does not automatically establish conformity with the controls.
Step 5: Prioritize Remediation
Not every discrepancy requires the same response.
A practical prioritization model considers security exposure, business impact, urgency, affected systems, and remediation effort.
Finding | Typical Priority | Recommended Response |
Unknown device accessing sensitive resources | High | Verify identity, ownership, and authorization promptly |
Unsupported business-critical application with known exposure | High | Assess vulnerabilities and implement appropriate remediation or mitigation |
Missing endpoint security protection | High | Investigate and restore required protection |
Outdated device ownership record | Medium | Confirm and correct ownership |
Unused software subscription | Medium | Validate usage and contractual terms before cancellation |
Incomplete hardware metadata | Low to Medium | Reconcile missing information based on operational importance |
These priorities are illustrative. Organizations should apply their own risk criteria and account for compensating controls.
Step 6: Document Findings and Manage Exceptions
Some findings cannot be resolved immediately. Business-critical applications may depend on unsupported software, replacement hardware may be unavailable, or remediation may require coordination with another department.
These cases should be managed through a documented exception process rather than ignored.
For each exception:
- Identify the affected asset or application and explain the deviation.
- Document its business justification and associated risk.
- Identify available mitigating or compensating controls.
- Obtain approval from the designated risk owner.
- Record an expiration or review date and the planned resolution.
- Reassess the exception when its conditions change.
For example, an organization may temporarily retain a legacy application because replacing it requires changes to a production system.
The exception should identify the application, affected devices, unsupported status, operational dependency, approved controls, responsible owner, and planned retirement or replacement date.
Documenting the exception does not eliminate the risk. It establishes accountability and a basis for continued review.
This distinction is particularly important for unsupported software, consistent with CIS Safeguard 2.2.
Step 7: Verify Remediation and Record Evidence
An audit finding should remain open until the responsible team verifies the outcome.
For example, discovering an unauthorized application is a finding. Removing it, confirming the removal, and updating the relevant records constitute corrective actions and verification.
Maintain an audit trail that includes:
- Finding and affected asset.
- Evidence or discovery source.
- Risk or business impact.
- Assigned owner.
- Required corrective action.
- Target completion date.
- Exception approval, where applicable.
- Verification method and result.
- Closure date.
Verification should correspond to the original finding. An application removal should be confirmed through updated device inventory or another reliable check. A corrected ownership record should be confirmed against the organization's authoritative records.
Similarly, sending a patch deployment command does not by itself establish that the update was successfully installed.
This information supports accountability and provides a reference for subsequent reviews.
How Often Should Endpoint Inventories and Software Audits Be Performed?
Endpoint inventories should be updated as devices are deployed, changed, reassigned, or retired. Periodic reconciliation is still necessary to identify gaps between management tools and authoritative asset records.
Software audit frequency should reflect organizational risk, rate of change, and applicable requirements.
CIS Controls v8.1 provides specific safeguard-level guidance:
- Enterprise asset inventory: Review and update at least every six months, or more frequently, under Safeguard 1.1.
- Unauthorized devices: Maintain a process to address them weekly under Safeguard 1.2.
- Software inventory: Review and update at least every six months, or more frequently, under Safeguard 2.1.
- Software support status: Review at least monthly under Safeguard 2.2.
- Unauthorized software: Review and address at least monthly under Safeguard 2.3.
These are recommendations within the CIS Controls framework, not universal legal audit requirements. Organizations adopting the controls should follow the applicable safeguard guidance, while also considering contractual and regulatory obligations.
The following schedule provides an operational example.
Activity | Suggested Cadence |
Update discovered endpoint and software information | Automatically as supported by management tools |
Review unknown and unauthorized devices | Weekly |
Review unauthorized or unsupported software findings | Monthly or more frequently based on risk |
Reconcile device ownership and management coverage | Monthly |
Review licensing and application consolidation opportunities | Quarterly |
Conduct a broader inventory and software audit | At least annually, with additional reviews based on risk |
A monthly reconciliation or annual broad audit does not replace the safeguard-specific reviews described above.
The key distinction is that automated discovery updates technical records, while audits validate those records against organizational expectations.
Measuring Endpoint Inventory and Software Audit Effectiveness
An inventory program should be evaluated based on completeness, accuracy, and the resolution of discrepancies rather than the number of records collected.
Useful performance measures include:
Endpoint Inventory Coverage
Measures the proportion of known in-scope endpoints represented in the management inventory.
Inventory coverage (%) = (Known in-scope endpoints present in inventory ÷ Total known in-scope endpoints) × 100
For example, if an organization has 500 known in-scope endpoints and 470 appear in its management inventory:
Inventory coverage = (470 ÷ 500) × 100 = 94%
This indicates that 6% of known endpoints are not represented in the inventory being measured.
The accuracy of the result depends on the reliability of the independent endpoint population used as the denominator. Unknown devices are not automatically captured by this calculation.
Inventory Record Accuracy
Measures the proportion of audited records that match independently verified asset information.
Record accuracy (%) = (Verified accurate records ÷ Records reviewed) × 100
An organization reviewing 200 asset records and confirming 184 as accurate would have 92% record accuracy within that review sample.
A sample-based result should not automatically be treated as the accuracy of the entire fleet.
Other Useful Metrics
IT teams can also monitor:
- Percentage of endpoints reporting within the expected management interval.
- Percentage of in-scope endpoints running supported operating systems.
- Number of unauthorized software findings.
- Number of unresolved software license discrepancies.
- Number of devices awaiting ownership verification.
- Average time to resolve high-priority audit findings.
- Percentage of findings closed with documented verification.
These metrics help separate inventory completeness from ongoing management and audit performance.
Common Endpoint Inventory and Software Audit Mistakes
Relying on a Single Discovery Source
An RMM platform can provide detailed information about enrolled endpoints, but it may not discover unmanaged devices, network infrastructure, or cloud services outside its scope.
Reconcile multiple authoritative sources to identify missing coverage.
Treating Installed Software as Proof of Usage
An installed application may never be used, while a SaaS application may be heavily used without appearing in traditional endpoint software records.
Combine installed software discovery with appropriate usage and licensing information when evaluating spending.
Removing Software Without Assessing Dependencies
An application that appears unnecessary may support another business system or workflow.
Confirm dependencies and business requirements before uninstalling software.
Treating Inventory Collection as a Completed Audit
An automatically generated inventory is evidence of discovered assets, not proof that all assets are authorized, supported, licensed, or compliant.
An audit requires comparison, evaluation, and documented follow-up.
How Level Helps IT Teams Manage Endpoint and Software Inventory
Level provides remote monitoring and management capabilities that help IT teams maintain visibility into managed endpoints across Windows, macOS, and Linux.
Its inventory capabilities bring hardware and software information into a centralized management environment, reducing the need to inspect every device individually.
Relevant capabilities include:
Centralized endpoint visibility. Level's device listing provides an overview of enrolled endpoints, including device status, group membership, tags, and reachability. IT teams can filter and search the device population to investigate specific systems or groups.
Hardware and operating system information. Device details provide hardware and system information that supports inventory reviews, troubleshooting, and infrastructure planning.
Installed application visibility. Level's Applications page allows technicians to review software reported by enrolled devices, compare versions, and identify which managed endpoints have specific applications installed.
Application-level investigation. Technicians can expand application entries to examine versions, installation counts, and affected devices. The device-level Applications tab also provides available details such as publisher, version, installation date, and installation user context.
Application monitoring and alerts. Level's Application Monitor can detect when specified software is present or absent on devices covered by a monitor policy. This helps IT teams identify unwanted applications or missing required software between scheduled audits.
Remote management and corrective action. Level supports running scripts and automations against selected devices, along with uninstall commands for applications where supported uninstall information is available.
Using Application Monitoring to Maintain Software Audit Controls
After establishing an approved software baseline, IT teams need a way to identify deviations that occur between formal reviews.
Level's Application Monitor supports two configurable conditions:
- Is installed: Creates an alert when a specified application is detected on a covered endpoint. This can help identify unwanted or unauthorized software.
- Is not installed: Creates an alert when required software is absent. This can help identify missing security tools, VPN clients, or other required applications.
The monitor compares configured application names against software reported in each device's application inventory.
It supports Windows, macOS, and Linux, although available application discovery methods vary by operating system.
Detection is not instantaneous. On connected devices, Level agents rebuild their installed-application inventory approximately every 10 minutes, while the Application Monitor checks that cached inventory approximately every minute. A new installation or removal may therefore take roughly 10 to 11 minutes to be detected. Offline devices resume evaluation after reconnecting.
For unwanted software, Level can also attempt automatic uninstallation on supported Windows and Linux devices. Automatic uninstall is not supported on macOS.
IT teams can attach an automation to a monitor alert to perform additional actions, such as installing required software, running a remediation script, or notifying responsible personnel.
Application monitoring has important limitations. Level matches configured names against reported application inventory using case-insensitive substring matching. A broad name may match unintended applications, while software not captured by the underlying inventory cannot trigger a matching alert.
For that reason, application names should be verified against reported inventory, and automated removal policies should be carefully tested before deployment.
An Application Monitor does not independently determine whether an application is malicious, vulnerable, or approved. The organization must define those conditions through its software policies and audit procedures.
Example: Investigating an Application During a Software Audit
Consider an IT team reviewing an application that has been flagged for further examination.
Using Level's Applications page, the team can:
- Search for the application across accessible managed endpoints.
- Review its publisher, platform, and reported installation count.
- Expand the application to compare installed versions.
- Identify the devices reporting the version under investigation.
- Determine whether corrective action is appropriate based on vendor guidance, organizational policy, and application dependencies.
- Select the relevant installations and initiate a supported script, automation, or uninstall action.
- Verify the result after the affected endpoints report updated application inventory information.
This workflow helps technicians move from identifying an application to determining which managed devices need attention.
Level's Applications page may show multiple installations of the same application on a single device, particularly where software is registered separately for different user accounts.
Consequently, reported installation counts should not be assumed to equal distinct device counts or software license requirements.
For example, Level's Device Applications documentation explains that Windows can register certain packaged applications separately for individual user profiles.
Another important limitation concerns remediation verification.
A successful uninstall request means that Level sent the supported removal command. It does not guarantee that the operating system completed the uninstall. The result must be verified against subsequently reported device information.
Level's application inventory reflects the latest data reported by enrolled agents rather than a continuous, instantaneous scan of every installation.
Level also does not replace procurement records, contractual software entitlement reviews, independent asset discovery, or a complete compliance audit.
By combining Level's endpoint visibility, application monitoring, and supported remediation capabilities with established asset management procedures, IT teams can reduce manual investigation while maintaining the additional controls needed for reliable organizational records.
Learn more about Level's inventory features or explore the platform to see how centralized endpoint management can support your inventory and software review workflows.
Final Thoughts
An accurate endpoint inventory establishes which devices an organization manages and how they are configured. A software audit evaluates whether the applications associated with those systems meet operational, security, support, and licensing requirements.
The most effective approach combines automated discovery with clearly assigned ownership, periodic reconciliation, risk-based reviews, and documented remediation.
For IT teams and MSPs, the goal is not simply to maintain a longer list of devices and applications. It is to maintain reliable information that supports better decisions, stronger security oversight, and measurable operational control.
Frequently Asked Questions
1. What should be included in an endpoint inventory?
An endpoint inventory should include device identifiers, hardware specifications, operating system information, assigned ownership, management status, and lifecycle details. Additional fields such as warranty information, acquisition date, and replacement status can support asset management and budgeting.
2. What is the difference between a software inventory and a software audit?
A software inventory records which applications and versions are present in an environment. A software audit evaluates that information against authorization, support, security, licensing, and organizational requirements. The inventory provides evidence used during the audit, but does not replace the audit itself.
3. Can an RMM platform perform a complete software audit?
An RMM platform can assist with software discovery, version identification, application monitoring, and endpoint-level corrective actions. However, a complete audit may also require procurement records, license agreements, SaaS administration data, vulnerability assessment, and business authorization reviews. RMM software supports the process but does not independently establish full license or regulatory compliance.
4. How often should IT teams update endpoint and software inventories?
Technical inventories should be updated as changes occur, with automated collection where available. IT teams should also perform periodic reconciliation and risk-based software reviews. CIS Controls v8.1 recommends reviewing enterprise asset and software inventories at least every six months, with more frequent reviews for unauthorized assets, unsupported software, and unauthorized applications. Applicable business and regulatory requirements may require different schedules.
