Explore our comprehensive IT Asset Management Process Template, designed to optimize asset tracking, security, maintenance, value assessment, and disposal.
1
Capture lifecycle event and accountable owners
2
Verify authorization and source evidence
3
Record unique asset identity
4
Record ownership custody and location
5
Record network and system association
6
Validate procurement and license records
7
Validate secure configuration and protection
8
Contain unauthorized or unmanaged asset
9
Assign or transfer asset custody
10
Record maintenance or repair outcome
11
Reconcile physical and authoritative records
12
Assess lifecycle condition and disposition
13
Prepare media sanitization and retirement
14
Verify sanitization and disposition evidence
15
Resolve exceptions and corrective actions
16
Approval: Asset control owner
17
Update authoritative records and close event
Capture lifecycle event and accountable owners
Open one run for one asset lifecycle event. Identify why the record is changing and who owns the control decision. Use the authoritative ticket or request as the trigger, avoid placing credentials or confidential data in free text, and select owners who can resolve exceptions and approve closure.
1
Acquisition
2
Deployment
3
Transfer
4
Maintenance or repair
5
Inventory audit
6
Unauthorized discovery
7
Incident quarantine
8
Return or retirement
Verify authorization and source evidence
Confirm that the asset and requested event have an authorized business basis. Compare the request with procurement, contract, change, or exception records. Record uncertainty explicitly; do not convert a missing approval into an assumed approval. Preserve evidence that another reviewer can independently inspect.
1
Approved
2
Pending approval
3
Exception approved
4
Not approved
5
Unknown
Record unique asset identity
Create or confirm the asset's unique identity at the granularity needed for accountability. Check labels against the device and source records, prevent duplicate inventory entries, and distinguish physical, virtual, cloud, software, and service assets. If an identifier is unavailable, explain why rather than inventing one.
1
End-user device
2
Server
3
Network device
4
Mobile device
5
Virtual machine
6
Cloud resource
7
Software asset
8
Non-computing or IoT device
Record ownership custody and location
Establish who is accountable, who currently holds or administers the asset, and where it can be found. Use the actual operational location, including remote, cloud, transit, and third-party custody. Resolve conflicting ownership before the workflow closes.
1
On-premises office
2
Data center
3
Remote worker
4
Colocation facility
5
Cloud or virtual environment
6
Secure storage
7
In transit
8
Third-party site
Record network and system association
Link the asset to the system or service it supports and capture identifiers needed to avoid duplicate discovery records. For non-networked assets, mark connectivity as not applicable. Validate addresses from a trusted source and never treat a dynamic address as a permanent identity.
1
Approved and connected
2
Approved not connected
3
Pending network approval
4
Not approved
5
Not network connected
6
Unknown
Validate procurement and license records
For acquisition or deployment events, reconcile the received asset with purchase, entitlement, warranty, and support records. Confirm quantities and terms without copying secret license keys into the workflow. Escalate missing ownership or entitlement evidence before deployment.
1
Valid entitlement confirmed
2
Entitlement pending verification
3
No license required
4
Open-source terms reviewed
5
Trial or evaluation only
6
Entitlement missing
Validate secure configuration and protection
Check the controls appropriate to the asset's role and data exposure. Verify evidence for the approved configuration baseline, encryption, endpoint protection, and backup or recovery coverage; do not mark a control implemented based only on intent. Document approved exceptions and their compensating controls.
1
Implemented and verified
2
Implemented not independently verified
3
Partially implemented
4
Approved exception
5
Not implemented
6
Not applicable
1
Implemented and verified
2
Implemented not independently verified
3
Planned
4
Not implemented
5
Not applicable
1
Implemented and verified
2
Implemented not independently verified
3
Planned
4
Not implemented
5
Not applicable
1
Implemented and tested
2
Implemented not tested
3
Planned
4
Not implemented
5
Not applicable
1
Public
2
Internal
3
Confidential
4
Restricted
5
Unknown
Contain unauthorized or unmanaged asset
Use this branch when the asset or its connection lacks authorization. Apply a proportionate containment action, preserve evidence, and link the incident or exception record. Avoid destructive action until ownership and evidentiary needs are understood; record who authorized any release.
1
Disconnected from network
2
Quarantined with monitoring
3
Access restricted
4
Removed from service
5
Exception temporarily approved
6
Containment not completed
Assign or transfer asset custody
For deployment or transfer events, hand the asset to the named custodian and record the effective date. Confirm the recipient understands acceptable-use, return, and security obligations. Attach acknowledgment evidence when policy requires it and keep the authoritative inventory owner unchanged unless formally transferred.
1
Accepted with evidence
2
Accepted without attachment
3
Pending recipient action
4
Declined
5
Not required
Record maintenance or repair outcome
Document the reported issue, authorized work, parts or configuration changes, and the verified outcome. Protect diagnostic evidence that may contain sensitive data. If the asset cannot return to service, carry the decision into the lifecycle assessment rather than closing the repair as successful.
1
Informational
2
Low
3
Moderate
4
High
5
Critical
1
Returned to service
2
Returned with limitation
3
Replacement required
4
Quarantined for investigation
5
Vendor service pending
6
Unable to repair
Reconcile physical and authoritative records
Compare the observed asset with the authoritative inventory and supporting systems. Check identity, owner, custodian, location, system association, and status. Record every unexplained difference and preserve verification evidence so unauthorized, missing, or duplicate records can be corrected.
1
Present and operational
2
Present with issue
3
In approved storage
4
In transit with evidence
5
Missing
6
Not physically applicable
1
Full match
2
Minor correctable difference
3
Material discrepancy
4
Missing inventory record
5
Duplicate inventory record
6
Unable to verify
Assess lifecycle condition and disposition
Decide the asset's next controlled state using business need, condition, supportability, security exposure, and cost. Separate the decision from execution: retirement or disposal still requires sanitization and transfer evidence. Explain tradeoffs and any dependencies that could delay the decision.
1
Serviceable
2
Serviceable with limitation
3
Repairable
4
Unsupported
5
Compromised or suspect
6
End of useful life
7
Unknown
1
Continue in service
2
Repair
3
Reassign
4
Upgrade
5
Quarantine
6
Return to vendor
7
Retire
8
Dispose
Prepare media sanitization and retirement
Before an asset leaves organizational control, identify all media and choose a sanitization method based on information sensitivity, media technology, reuse destination, and organizational policy. Use NIST SP 800-88 Rev. 2 terminology. Maintain chain of custody and do not rely on ordinary file deletion.
1
Magnetic hard drive
2
Solid-state drive
3
Removable flash media
4
Optical media
5
Mobile device storage
6
Embedded or IoT storage
7
Cloud or virtual storage
8
No storage media
1
Public
2
Internal
3
Confidential
4
Restricted
5
Unknown
1
Clear
2
Purge
3
Destroy
4
Cryptographic erase
5
Approved vendor-managed sanitization
6
Not applicable
Verify sanitization and disposition evidence
Independently verify that sanitization completed as planned and that final reuse, return, recycling, donation, or destruction is authorized. Retain the certificate or equivalent evidence and resolve serial-number mismatches before release. A vendor statement without asset linkage is insufficient.
1
Verified successful
2
Verified with limitation
3
Failed verification
4
Pending verification
5
Not applicable
1
Internal reuse
2
Return to supplier
3
Certified recycler
4
Approved donation
5
Physical destruction
6
Secure storage
7
Not yet completed
Resolve exceptions and corrective actions
Consolidate unresolved authorization, security, inventory, custody, or disposition exceptions. Assign a named owner, record interim controls, and set a realistic corrective-action date. Do not use this task to conceal a failed mandatory control; escalate material risk through the organization's exception process.
1
Authorization
2
Inventory accuracy
3
Ownership or custody
4
Security configuration
5
Licensing or entitlement
6
Maintenance or support
7
Sanitization or disposition
8
Other
1
Informational
2
Low
3
Moderate
4
High
5
Critical
Approval: Asset control owner
Will be submitted for approval:
Verify authorization and source evidence
Will be submitted
Record unique asset identity
Will be submitted
Record ownership custody and location
Will be submitted
Record network and system association
Will be submitted
Validate procurement and license records
Will be submitted
Validate secure configuration and protection
Will be submitted
Contain unauthorized or unmanaged asset
Will be submitted
Assign or transfer asset custody
Will be submitted
Record maintenance or repair outcome
Will be submitted
Reconcile physical and authoritative records
Will be submitted
Assess lifecycle condition and disposition
Will be submitted
Prepare media sanitization and retirement
Will be submitted
Verify sanitization and disposition evidence
Will be submitted
Resolve exceptions and corrective actions
Will be submitted
Approve the asset lifecycle event only after reviewing the authoritative identity, ownership, control, reconciliation, disposition, and exception evidence. Reject the event when material discrepancies remain unexplained or mandatory sanitization evidence is absent.
Update authoritative records and close event
After approval, update the authoritative inventory and connected records to the verified final state. Confirm that identifiers, ownership, location, system association, status, and disposition agree across systems. Link the updated record and summarize any corrective actions that remain open outside this event.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.