Hardware, software and information assets #

One registry, three families #

RiskPilot retains one asset entity with an explicit family:

• Hardware (HARDWARE): servers, workstations, network equipment, mobile devices and media;
• Software (SOFTWARE): applications, systems, cloud services, components and licences;
• Information (INFORMATION): data, documents, databases, flows and archives.

Routes /assets/hardware, /assets/software and /assets/information filter the registry without duplicating relationships to risks, incidents, continuity or dependencies.

In the navigation, expand the collapsible Assets group: All assets opens the cross-family register, while the other three entries apply a family filter. The group opens automatically when an asset route is active.

Create and classify an asset #

Choose family, type, scope, owner, criticality and status. Record confidentiality, integrity and availability, then useful relationships. The migration classifies historical assets deterministically; review ambiguous legacy types.

Daily use #

Each view supports listing, search, creation, editing, archiving and export according to permissions. Search and relationships remain cross-family: a software service may depend on a hardware server and process an information asset.

Controls #

All relationships must stay in the same organization. Prefer archiving over deletion when an asset carries history. Review family, type, owner, scope and CIA values regularly.