Master your organization's IT assets effectively with our comprehensive IT Asset Management Process, aiding in tracking, evaluating and optimizing assets.
1
Define review scope and ownership
2
Collect authoritative inventory evidence
3
Discover in-scope enterprise assets
4
Normalize the asset register
5
Verify identifiers and accountability
6
Reconcile location and connection status
7
Review software inventory and licensing
8
Assess exposure and exception routing
9
Contain and assign asset exceptions
10
Evaluate lifecycle and replacement priorities
11
Plan sanitization and disposal
12
Reconcile register totals and evidence
13
Document corrective action plan
14
Confirm governance readiness
15
Approval: Asset governance
16
Close and communicate review results
Define review scope and ownership
Set the boundary for this inventory reconciliation before collecting data. Name the accountable asset manager and approver, define included sites and environments, and use a fixed evidence cutoff so later counts are comparable. Exclude assets only with an explicit scope reason; vague boundaries create false gaps.
Collect authoritative inventory evidence
Gather exports or reports from the systems that can prove what exists, including endpoint management, directory, network, cloud, procurement, service management and software tooling. Record source freshness and limitations. Do not treat one discovery source as complete when assets can be offline, remote or cloud-hosted.
1
Endpoint management
2
Directory services
3
Network discovery
4
Cloud platform inventory
5
Procurement or finance records
6
Service management register
7
Software inventory tooling
Discover in-scope enterprise assets
Run or obtain current discovery results for hardware, virtual, remote, cloud and non-computing assets within scope. Reconcile active and intermittently connected devices rather than relying on a single live scan. Preserve the raw evidence and record the population before normalization.
1
Active network discovery
2
Endpoint management export
3
Directory reconciliation
4
Cloud resource export
5
Physical verification
6
Procurement record comparison
Normalize the asset register
Create one normalized register with a stable record for each asset. Standardize identifiers, type, owner, department, location, system association, network details and lifecycle state. Keep source references so each record is traceable; do not silently merge records that might represent separate devices.
Verify identifiers and accountability
Test the register for duplicate identifiers, missing owners, missing system associations and ambiguous records. Resolve straightforward duplicates against source evidence and record anything requiring investigation. Identifiers must remain text values so leading zeros and mixed characters are preserved.
Reconcile location and connection status
Compare recorded locations and network identifiers with current evidence. Confirm whether each connected asset is approved and whether remote, virtual or cloud assets are represented. Isolate discrepancies instead of overwriting history when the evidence does not establish the correct state.
1
All connections authorized
2
Unauthorized asset detected
3
Unmanaged asset detected
4
Approval evidence missing
5
Review incomplete
Review software inventory and licensing
Reconcile installed software against licensed and authorized software records. Capture publisher, version, business purpose, deployment context and support state where relevant. Flag unsupported or unauthorized software for action; a paid license alone does not prove current support or authorization.
1
Authorized and supported
2
Unauthorized software found
3
Unsupported software found
4
License evidence incomplete
5
Software inventory incomplete
Assess exposure and exception routing
Assess inventory gaps, unsupported components, unauthorized connections, missing ownership and vulnerability exposure using the evidence gathered above. Select the primary exception route for this run and explain severity, business impact and immediate safeguards. Use 'No material exception' only when the evidence is complete.
1
No material exception
2
Unauthorized or unmanaged asset
3
Unsupported or unlicensed software
4
Missing ownership or location
5
Vulnerability exposure
6
Disposal or sanitization pending
1
Low
2
Moderate
3
High
4
Critical
5
Not yet assessed
Contain and assign asset exceptions
Use this task when the review finds a material exception. Record containment already applied, the accountable resolver and the evidence needed for closure. For unauthorized components, prefer isolation or access restriction while facts are established; do not delete records or destroy evidence as a shortcut.
Evaluate lifecycle and replacement priorities
Classify assets by operational lifecycle, support status, condition, criticality and replacement need. Separate renewal decisions from disposal execution and document why an asset should be retained, upgraded, replaced or retired. Avoid age-only decisions when supportability and business impact differ.
1
Retain and monitor
2
Repair or reconfigure
3
Upgrade software or firmware
4
Renew license or support
5
Replace asset
6
Retire asset
Plan sanitization and disposal
For assets leaving organizational control, choose sanitization and disposition methods that match the media and information sensitivity. Preserve chain-of-custody and verification evidence before reuse, return, sale, recycling or destruction. Never mark disposal complete solely because equipment was collected.
1
Verified complete
2
Awaiting sanitization
3
Awaiting disposition
4
Evidence incomplete
5
Exception approved
Reconcile register totals and evidence
Reconcile discovered, normalized, exception and disposition populations so every in-scope record has a traceable outcome. Explain count differences and confirm there is no duplicate accounting across systems. Do not force totals to match by deleting unexplained records.
Document corrective action plan
Translate unresolved findings into owned, testable corrective actions. Each action needs a clear result, accountable owner, target date and closure evidence. Consolidate related fixes without obscuring individual high-risk items, and flag dependencies that could delay completion.
Confirm governance readiness
Perform the pre-approval quality check. Confirm the register is current, sources and variances are documented, material exceptions are contained and every open action has ownership. State any residual risk plainly so the approver can decide from evidence rather than an optimistic status label.
1
Ready for approval
2
Ready with accepted residual risk
3
Blocked by unresolved critical risk
4
Blocked by incomplete evidence
5
Returned for correction
Approval: Asset governance
Will be submitted for approval:
Define review scope and ownership
Will be submitted
Collect authoritative inventory evidence
Will be submitted
Discover in-scope enterprise assets
Will be submitted
Normalize the asset register
Will be submitted
Verify identifiers and accountability
Will be submitted
Reconcile location and connection status
Will be submitted
Review software inventory and licensing
Will be submitted
Assess exposure and exception routing
Will be submitted
Contain and assign asset exceptions
Will be submitted
Evaluate lifecycle and replacement priorities
Will be submitted
Plan sanitization and disposal
Will be submitted
Reconcile register totals and evidence
Will be submitted
Document corrective action plan
Will be submitted
Confirm governance readiness
Will be submitted
Close and communicate review results
After approval, record the decision, publish the reconciled register through the organization's controlled channel and notify action owners. Retain the evidence package and schedule the next review outside this single run. Keep the run open if the approved outcome and communicated status do not agree.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.