Skip to main content
The Asset Management module provides an inventory of your organisation’s information assets. Each asset is classified by type, assigned an owner, and scored on confidentiality, integrity, and availability. Criticality is derived automatically from these scores and drives prioritisation in the Risk Management module.

Asset inventory

The inventory is displayed as a table. Each row represents one asset with its classification attributes and calculated criticality.

Default assets

ISOwl ships with four pre-configured example assets to illustrate the data model:
IDNameTypeOwnerCIDCriticality
A001Base de Datos de ClientesInformaciónCISO333Critical
A002Servidor ERP PrincipalHardwareIT232Critical
A003Código Fuente App MóvilSoftwareDevOps321Critical
A004Despachos GerenciaInfraestructuraOperaciones111Normal
Default assets are examples only. Replace or remove them to reflect your organisation’s actual asset inventory before conducting a formal risk assessment.

Adding an asset

1

Open the Asset Management page

Navigate to Assets in the sidebar.
2

Click Add asset

Click the Add asset button in the page header to open the asset creation form.
3

Enter the asset name

Provide a descriptive name that clearly identifies the asset (e.g. Customer Database, Office Wi-Fi Network).
4

Select the asset type

Choose one of the six asset types:
TypeExamples
InformationDatabases, customer records, contracts
HardwareServers, laptops, mobile devices
SoftwareApplications, operating systems, SaaS tools
InfrastructureNetwork equipment, data centres, offices
ServicesCloud providers, outsourced services
PeopleKey personnel, roles with privileged access
5

Assign an owner

Enter the name or role of the person responsible for this asset (e.g. CISO, IT Manager).
6

Score confidentiality, integrity, and availability

Set each CIA dimension on a scale of 1 to 3:
ScoreLevelDescription
1LowBreach has minimal impact
2MediumBreach has significant but recoverable impact
3HighBreach has severe or irreversible impact
Criticality is calculated automatically as:
Criticality = max(Confidentiality, Integrity, Availability)
7

Save the asset

Click Save to add the asset to the inventory. It is immediately available in the asset selector within the Risk Management form.

Criticality levels

Criticality is derived from the highest CIA score and used to colour-code assets throughout the application:
Max CIA scoreCriticalityColor
3CriticalRose (red)
2ImportantAmber (yellow)
1NormalEmerald (green)

Editing and deleting assets

Click the edit icon on any asset row to open the asset edit form. All fields — name, type, owner, and CIA scores — can be updated. Changes take effect immediately and are reflected in any linked risk entries.
Every risk in the Risk Management module must be linked to an asset. This ensures that:
  • Risk exposure can be attributed to specific assets.
  • Deleting an asset also removes orphaned risks.
  • High-criticality assets can be prioritised for risk treatment.
To see all risks associated with a specific asset, open the Risk Management page and filter by asset name.

Frequently asked questions

Bulk import is not currently supported. Assets must be added individually through the form. You can use the default example assets as a starting point and edit them to match your inventory.
A score of 1 on availability means that short-term unavailability of this asset has minimal business impact. If the database underpins core business operations, the availability score should be 3. Ensure CIA scores reflect your actual business context.
Yes. A single asset can be linked to multiple risk entries. For example, a customer database might have separate risks for ransomware, accidental deletion, and unauthorised access.
Assets are used as the foundation for risk assessments in the Risk Management module and in Clause 6 of the Clauses module. They are not directly linked to individual Annex A controls, but high-criticality assets should inform which controls you prioritise in the SoA.

Build docs developers (and LLMs) love