In order to meet the requirements of ‘Asset management’ A.8 from Annex A of ISO 27001, it is necessary to identify organisational assets and define appropriate protection responsibilities, as well as ensuring that information receives an appropriate level of protection in accordance with its importance to the organisation.
Establishing Asset Registers
When compiling your asset registers or inventories, it is recommended that you record the following information for each information asset:
- Asset type
- Asset owner
- Asset classification
- Asset location
- Asset impact levels in relation to confidentiality, integrity and availability
Establishing Asset Types
URM suggests the following basic segregation of assets:
- Information assets
- Supporting assets
– hardware
– software
– people
– buildings - Intangible assets (e.g., brand and reputation).
Identifying Asset Owners
In the process of identifying asset owners, it is important to identify a functional role that has oversight of specific types of assets.
Asset owners are responsible for:
- Identifying risks to the asset type
- Providing guidance and instructions on how the asset should be used.
- Identifying levels of protection required depending on the asset classification.
- Implementing and verifying the effectiveness of security controls in respect of that asset type.
Assigning Asset Classifications
Depending on the organisational structure, it would typically be the asset owner who would decide asset classification. The classification must be approved by top management and the criteria for protection of assets must be in line with their criticality.
Assigning Impact Levels
As with classification, impact levels need to be assigned by the asset owner. Determining the impact levels of assets can be relatively complex, but in essence, the impact level will be inherited by the information contained on or within the asset.
A short, free, non‑commitment call can help you clarify scope, understand regulatory expectations, and align your approach across standards such as ISO 42001 and NIST AI RMF. Early guidance often saves time and avoids fragmented compliance efforts.
Whether you are at an early planning stage or preparing for audit and assurance activities, we offer a free introductory call to help you assess risks, responsibilities, and the most proportionate route forward.
You do not need a fully defined programme to start the conversation. We offer a free, no‑obligation call to help you understand SOC 2 requirements, assess your current position, and identify practical next steps.
URM’s blog, produced in collaboration with BSI, discusses common mistakes we have seen in early ISO 27001:2022 transitions, and how to avoid them.
In this blog, we’re going back to basics and looking at some of the fundamentals of information security and ISO 27001.
When managing the security of your organisation’s information assets, you will need to consider the scope of what you are doing.

