Statement of applicability template
Fill in the 4 blank fields for each of the 15 rows. What you type stays in this browser. When you finish, download your answers as a CSV file that opens in Excel.
Specification
- Process type
- life cycle
- Objective summary
- Requirements are requested and analyzed, and alternatives are evaluated.
- Always included
- No
Acquisition
- Process type
- life cycle
- Objective summary
- Assets in scope are acquired in a controlled way and recorded.
- Always included
- No
Development
- Process type
- life cycle
- Objective summary
- Software the organization builds takes ITAM requirements into account.
- Always included
- No
Release
- Process type
- life cycle
- Objective summary
- Releases are planned and run in a way that supports ITAM.
- Always included
- No
Deployment
- Process type
- life cycle
- Objective summary
- Deployment and redeployment support ITAM requirements.
- Always included
- No
Operation
- Process type
- life cycle
- Objective summary
- Day-to-day use, monitoring and optimization of assets support ITAM.
- Always included
- No
Retirement
- Process type
- life cycle
- Objective summary
- Assets leave use, and are repurposed, recycled or disposed of under policy, with records kept.
- Always included
- No
Management of change
- Process type
- functional
- Objective summary
- Planned changes are controlled and unplanned changes are reviewed.
- Always included
- Yes
- In scope
- yes
- Justification
- Required by 19770-1 clause 8
Core data management
- Process type
- functional
- Objective summary
- Required data on every core asset is accurate through its life, with an authorized-or-not record.
- Always included
- Yes
- In scope
- yes
- Justification
- Required by 19770-1 clause 8
License management
- Process type
- functional
- Objective summary
- License, entitlement and usage data is accurate, and reconciled and verified periodically.
- Always included
- Yes
- In scope
- yes
- Justification
- Required by 19770-1 clause 8
Security management
- Process type
- functional
- Objective summary
- Security, including access and integrity controls, is managed within ITAM and verified periodically.
- Always included
- Yes
- In scope
- yes
- Justification
- Required by 19770-1 clause 8
Relationship and contract management
- Process type
- functional
- Objective summary
- Supplier and internal relationships and all contracts for assets in scope are managed.
- Always included
- No
Financial management
- Process type
- functional
- Objective summary
- Costs and values of assets are monitored and managed, including cost-effectiveness.
- Always included
- No
Service level management
- Process type
- functional
- Objective summary
- Service levels that ITAM depends on are defined, recorded and managed.
- Always included
- No
Other risk management
- Process type
- functional
- Objective summary
- Risks not covered by another process are managed and the treatment is checked.
- Always included
- No
Notes
Pre-filled with the 15 processes in Annex A. For each, say whether it is in scope and why. The standard asks for a justification for every inclusion and exclusion.
- Change, core data, license and security management are marked "always included". The standard says their objectives are already part of clause 8.
tier: fill in from Annex B, Figure B.2 of your copy of the standard.evidence_location: where an auditor can see the process working.