Asset inventory for ISO 27001
What you do not know, you cannot protect. The asset inventory lists your information and everything that holds it, with an owner and a protection need. The template works out the overall protection need by itself.
Examples
Eight completed entries for orientation, invented values
| Name | Type | Owner (person) |
|---|---|---|
| Customer base and orders | Information | Head of sales |
| Design data | Information | Head of development |
| Personnel files | Information | Head of HR |
| ERP system | Application | Head of finance |
| Cloud storage | Cloud service | Head of IT |
| Laptops, administration (18 units) | Hardware | Head of IT |
more columns in the file: ID · Purpose and content · Supported process · Operator (internal or service provider) · Location or data region · Integrity · Availability · Reason for protection need · Personal data · Life cycle · Last review · Next review · Remark
Extract from the Excel file with example rows · the workbook has 3 sheets, highlighted columns are calculated by the template. The example values are invented.
What the template is for
Annex A of ISO 27001 asks you to list the information you hold and the systems, devices, services and premises that hold it, with an owner for each entry (control 5.9). The controls that follow build on this: rules for use, return when someone leaves, and classification by protection need (5.10 to 5.12).
The inventory is also the basis of the risk assessment: risks attach to assets. If the inventory has gaps, so will the risk assessment.
What is in the file
- An “Instructions” sheet with steps, the asset types and the protection need scale normal, high, very high.
- An “Inventory” sheet with 80 rows: ID, name, type, purpose, supported process, owner, operator, location or data region, personal data, life cycle, review dates.
- Confidentiality, integrity and availability with drop-down lists; the template derives the overall protection need from the highest value and highlights “very high”.
- An “Examples” sheet with eight entries from the customer database to the server room. For NIS2 with services and dependencies, the knowledge area has a more detailed inventory.
How to fill it in
- 1
Start with the information, not the devices: customer data, design data, personnel files, contracts. Then the systems that hold it.
- 2
Add applications, cloud services, hardware, network, rooms and service providers. One row per asset; similar devices may be listed as a group.
- 3
Name one person as owner for each entry, not a department. Where a service provider runs the system, enter them as operator.
- 4
Rate the protection need for confidentiality, integrity and availability; the overall protection need follows the highest value.
- 5
Mark personal data; this links the inventory to the record of processing activities.
- 6
Enter review dates and update the inventory with every purchase, decommissioning and new service, and review it in full at least once a year.
The same steps are in the file on the “Instructions” sheet, together with the rating scales and the completed examples.
Common mistakes when filling it in
What most often goes wrong when filling in this file, and how to avoid it.
- Started with the devices
- If you fill the inventory from IT's device list, you have laptops and printers but no information. Start with entries of the type “Information” and then assign the systems that hold it.
- A department as owner
- “IT” or “Sales” in the “Owner (person)” column names nobody. Enter a person; a service provider that runs the system belongs in the “Operator” column.
- Protection need without a reason
- If everything says “high” and “Reason for protection need” stays empty, the classification steers nothing. One sentence per row is enough, for example what damage loss or failure would cause.
- Overall protection need set by hand
- The template calculates this column from the highest of the three values. Typing a value there deletes the formula, and the row no longer follows changes to confidentiality, integrity or availability.
- Life cycle and review dates out of date
- Retired devices still say “In operation”, and the “Next review” column is empty. The inventory then goes out of date unnoticed. Change the life cycle with every decommissioning and set a review date.
What an auditor checks for this clause and which nonconformities they often find is explained on the clause page: ISO 27001, Annex A: the controls at a glance.
ISO 27001 with IMScollect
In IMScollect you keep the inventory in the system, with a person as owner, protection need and life cycle, linked to risks. Existing Excel lists can be imported.
See it working in one system
In a free demo we show you how these lists work together in IMScollect, with your standards and your questions.
More templates
- ISO 27001Statement of Applicability (SoA)ISO 27001 clause 6.1.3 Information security risk treatment, Annex AExcel templateView
- ISO 9001ISO 14001ISO 27001Risk registerClause 6.1 Actions to address risks and opportunities (ISO 27001 also 6.1.2 and 6.1.3)Excel templateView
- ISO 9001ISO 14001ISO 27001Management reviewClause 9.3 Management reviewWord templateView
- ISO 9001ISO 14001ISO 27001Audit programmeClause 9.2 Internal auditExcel templateView
