Explore our comprehensive IT Asset Management Process PPT outlining strategies for effective asset management, policy development, tracking, training, auditing, and continuous improvement.
1
Set review scope and ownership
2
Collect authoritative inventory evidence
3
Reconcile discovered enterprise assets
4
Contain unauthorized enterprise assets
5
Verify required asset record details
6
Verify software inventory and support
7
Document unsupported software exceptions
8
Classify asset importance and data
9
Confirm ownership location and custody
10
Assess lifecycle and maintenance status
11
Control asset transfer and disposal
12
Prioritize control gaps and risks
13
Create corrective asset action plan
14
Validate evidence and residual exceptions
15
Approval: IT asset review
16
Close review and schedule follow-up
Set review scope and ownership
Define one bounded IT asset review cycle before gathering evidence. Confirm the business boundary, review cutoff, accountable asset manager, and approving manager. Include physical, virtual, remote, cloud, mobile, network, and IoT assets where they fall inside scope; record exclusions explicitly so inventory coverage is testable.
1
Enterprise-wide review
2
Business unit review
3
Location-based review
4
Technology platform review
5
Targeted risk review
Collect authoritative inventory evidence
Assemble evidence from the systems that can establish what assets exist, who owns them, and whether they are authorized. Prefer timestamped exports from authoritative tools and retain the source date. Do not rely on a single discovery source when the scope includes remote, cloud, virtual, or intermittently connected assets.
1
Configuration management database
2
Endpoint or mobile management
3
Network discovery or DHCP logs
4
Cloud and virtualization inventory
5
Procurement and finance records
6
Manual location or custody register
Reconcile discovered enterprise assets
Compare the authoritative inventory with discovered and observed assets. Normalize duplicate identifiers, account for devices that are offline or paused, and distinguish approved assets from unknown or unmanaged ones. Investigate coverage gaps instead of interpreting a clean scan as proof of completeness.
1
Complete and reconciled
2
Minor gaps documented
3
Material gaps documented
4
Discovery coverage insufficient
5
Reconciliation not possible
Contain unauthorized enterprise assets
For each unauthorized or unmanaged asset, identify it, establish current connectivity and custody, and choose a proportionate containment route. Preserve evidence needed for investigation. Avoid wiping or disposing of an unknown device until ownership, legal hold, and incident-response implications have been checked.
1
Remove from network
2
Quarantine with restricted access
3
Approve and onboard
4
Investigate ownership first
5
Escalate as security incident
Verify required asset record details
Test inventory records for the details needed to operate and protect assets: stable identifier, type, owner, department, location, authorization, network identifiers where applicable, and last verification date. Use a defined sample or the full population and record the method so another reviewer can reproduce the result.
1
All required details present
2
Isolated missing details
3
Recurring missing details
4
Ownership materially incomplete
5
Records unreliable for control
Verify software inventory and support
Reconcile installed software against the authorized software inventory. Check publisher, version, business purpose, deployment route, authorization, support status, and planned decommission date where relevant. Treat unsupported mission-required software as an exception requiring documented controls and risk acceptance.
1
Endpoint software inventory
2
Server configuration inventory
3
Cloud application inventory
4
License management records
5
Approved software catalog
1
Complete and authorized
2
Minor exceptions documented
3
Unsupported software present
4
Unauthorized software present
5
Coverage insufficient
Document unsupported software exceptions
Document every unsupported product that must remain in use, its mission need, exposure, compensating controls, accountable owner, expiry date, and accepted residual risk. Unsupported software without an approved, time-bounded exception should be treated as unauthorized and entered into remediation.
1
Low
2
Moderate
3
High
4
Critical
5
Not yet assessed
Classify asset importance and data
Classify the reviewed population according to business importance, service dependencies, and the sensitivity of data stored or processed. Use the organization's approved taxonomy where one exists. Resolve inconsistent classifications with service owners because lifecycle, protection, recovery, and sanitization decisions depend on this result.
1
Low
2
Moderate
3
High
4
Mission critical
5
Not yet classified
1
Public
2
Internal
3
Confidential
4
Restricted
5
Not yet classified
Confirm ownership location and custody
Verify that assets have accountable business and technical ownership and that location or custody is current. Include loaned, remote, spare, repair, vendor-held, and storage assets. Reconcile custody evidence to the inventory and assign each unresolved handoff to a named owner.
1
All assets have verified owners
2
Minor ownership gaps
3
Material ownership gaps
4
Custody evidence incomplete
5
Ownership cannot be established
Assess lifecycle and maintenance status
Determine whether assets are being onboarded, actively supported, awaiting maintenance, being transferred, or ready for retirement. Check warranty or support state, configuration and patch evidence, repair history, capacity, and business need. Select the lifecycle state that drives the next controlled action.
1
New or onboarding
2
Active and supported
3
Maintenance due
4
Transfer or redeploy
5
Retire or dispose
1
Current and healthy
2
Minor maintenance due
3
Material maintenance overdue
4
Vendor support ending
5
Unsupported or failed
Control asset transfer and disposal
For transferred, redeployed, retired, or disposed assets, select an approved sanitization outcome based on media type, data sensitivity, reuse destination, legal obligations, and verification capability. Maintain chain of custody and evidence that the chosen clear, purge, destroy, or specialist route was completed and validated.
1
Clear
2
Purge
3
Destroy
4
Not applicable no storage
5
Specialist assessment required
1
Internal redeployment
2
Return to lessor or vendor
3
Certified recycling
4
Donation or resale
5
Secure destruction
Prioritize control gaps and risks
Consolidate the evidence into a risk-ranked finding set. Consider asset criticality, data sensitivity, exploitability, support status, exposure, and the strength of existing controls. Separate immediate containment from planned remediation and make the rationale clear enough for an approver to challenge.
1
Low
2
Moderate
3
High
4
Critical
5
Assessment incomplete
1
No immediate action
2
Monitor pending review
3
Contain within one day
4
Remediate within seven days
5
Escalate immediately
Create corrective asset action plan
Turn each material finding into a controlled action with an accountable owner, target date, success evidence, and dependency. Combine duplicates but do not hide separate risks behind a broad action. Dates should reflect organizational risk tolerance and operational constraints rather than an arbitrary universal SLA.
Validate evidence and residual exceptions
Perform an independent readiness check before approval. Confirm the source dates, sampled records, exception owners, risk decisions, action dates, and disposal evidence are internally consistent. Return incomplete items for correction and describe any residual exception the approver must knowingly accept.
1
Complete and consistent
2
Minor corrections required
3
Material evidence missing
4
Risk decisions unresolved
5
Not ready for approval
1
Approve
2
Approve with conditions
3
Return for correction
4
Escalate for risk decision
5
Defer pending evidence
Approval: IT asset review
Will be submitted for approval:
Prioritize control gaps and risks
Will be submitted
Create corrective asset action plan
Will be submitted
Validate evidence and residual exceptions
Will be submitted
Close review and schedule follow-up
Record the approved disposition, distribute the action plan to accountable owners, preserve the evidence package, and set the next review point according to the organization's risk-based cadence. Do not mark the cycle closed if approval conditions lack owners or dates.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.