Asset Registration

IRAP assessment requires a clear asset inventory. Register your systems and assets so evidence maps correctly to ISM controls and assessors can see what's in scope.

Why Assets Matter

  • Assets define the boundary of your IRAP assessment
  • Evidence is collected against registered assets
  • Unregistered assets won't have automated evidence
  • Your asset register is a compliance artefact itself
Assessors expect to see a maintained asset register.

Asset Types

These are the four types you can choose when you register an asset by hand. Integrations can also create assets of other types, such as repositories, devices and identities.

Type Examples
Cloud Resource EC2 instances, S3 buckets, RDS databases, Lambda
Hardware Laptops, servers, network equipment, mobile devices
Software/SaaS Applications, services, third-party tools
Data Store Databases, file shares, document management

Automatic vs Manual Registration

Automatic Collection

  • Integrations collect assets during pipeline runs
  • GitHub: repositories as assets
  • Mosyle: managed devices as assets
  • AWS: cloud resources as assets

Learn more about integrations

Manual Registration

  1. Go to Inventory → Assets (the Asset Register) and click Add Asset
  2. Choose the asset type, then enter the name and, optionally, an asset ID and description
  3. Choose the IRAP Classification and Criticality
  4. Optionally link the asset to a System, and add owner, location and provider details
  5. Click Create Asset

Data Classification

The form calls this field IRAP Classification.

Level Description Example
Unofficial Public information Marketing website
Official Routine business Internal tools
Official: Sensitive Requires safeguards Customer data, HR records
Protected High business impact Financial systems, PII stores
Secret Very high business impact Rare outside government work
Most IRAP assessments target Official: Sensitive. The form defaults to Official, so set the classification deliberately for each asset.

Linking Assets to Systems

  • Assets belong to systems
  • Systems run pipelines that collect findings and evidence
  • Organise assets by application or service boundary
  • One system can have many assets

Maintaining Your Register

  • Run pipeline scans regularly to refresh automated assets
  • Update manual assets when infrastructure changes
  • Set decommissioned assets to the Decommissioned status rather than deleting them, which keeps the audit trail
  • Review classifications when data handling changes