Zum Hauptinhalt springen
Asset category · Asset register

AC02 Software

Updated on 6 min Reviewed by: Cenedril Editorial
ISO 27001ISO/IEC 27005BSI IT-Grundschutz

An online retailer lists the servers, the laptops and the ERP system in its first asset register. The shop itself, a service provider’s payment interface and a small script that reconciles stock levels every night are missing. When the interface starts rejecting orders after the provider pushes an update, the team spends two days looking for the cause, because nobody knew the dependency existed. The software category shows which programs and services actually carry your operations.

Today, software is involved in almost every step of work: as purchased standard applications, as cloud services, as products you build yourself or as AI models. Asset category AC02 brings all of this together so that you can name every application in the asset register, assign it to a responsible person and rate it by its protection needs.

What belongs to it?

The catalogue splits the category into five asset classes. The split follows the question of who owns the software and who develops it further, because that decides what you can secure yourself.

  • Software owned by others. Enterprise applications such as ERP and CRM, productivity software, web browsers, mobile apps, operating systems, plus third-party services and interfaces, for example for payments, maps or text messaging. The vendor decides when updates arrive; your job is to install them promptly and keep the configuration under control.
  • Software, open source or owned. Products and components you develop, in-house applications for internal use, licensed software, open source software, development tools, your own APIs and your own mobile apps. For in-house developments you are responsible for the whole life cycle; for open source at least for selection, updates and licence obligations.
  • Website. Company and product websites, web databases, SaaS applications, contact forms, customer forums and online help desks. They can be reached from outside and are therefore usually the first attack surface.
  • Artificial intelligence. Training data, trained models and AI agents, such as an agent that pre-checks incoming invoices. Risks of their own come on top, for example poisoned training data, and depending on the use case obligations under the AI Act (→ AI Register).
  • Cloud and collaboration services. Cloud infrastructure and cloud storage, plus platforms for chat, video conferencing and shared workspaces.

Why the category matters

ISO/IEC 27005 distinguishes primary assets, also called business assets, from supporting assets. Primary assets are information and processes that are valuable to the organization in themselves; supporting assets are the components these business assets are built on. Software sits right on this boundary. Purchased standard software is usually a supporting asset, while software you build, sell or use to serve customers can be a business asset itself. The catalogue reflects this and notes for each asset type whether it can be recorded as a primary asset.

This has practical consequences for the risk assessment. You derive the protection needs of a standard application from the information and processes it carries: an ERP system holding payroll and financial data inherits their high needs. For your own customer platform, the value of the software itself counts as well, meaning the development effort invested, the revenue that depends on it and the trust of your customers. The standard recommends documenting such dependencies between assets. That way you see which application carries which business process, and you do not assess the same risk twice.

Typical threats

In practice: recording assets in the asset register

Record at application level. Create one asset per application or service and assign category, class and type (→ Asset Register in the Starter Kit). Libraries, modules and plugins belong to the application that uses them.

Clarify responsibility. Every application needs a responsible person who decides on access, updates and changes. For cloud services this person often sits in the business department, while technical support lies with IT or the provider.

Record dependencies. Link each application to the information it processes, to the hardware or cloud environment it runs on and to the processes it supports. Its protection needs follow from these links.

Think in life cycles. Record the version, the end of vendor support and the licence model. Software without security updates calls for a decision: replace it, isolate it or knowingly accept the risk. For in-house development, the → Secure Software Development Policy sets the frame.

Relations to other categories

In the catalogue, software is connected to every other category. It processes, generates and stores AC01 Information, runs on AC03 Hardware and at the same time controls and monitors it. It authorizes and supports AC04 Human assets, enforces organizational rules and automates AC14 Processes. Software implements AC07 Intellectual Property and is itself licensed. It is obtained through the AC11 Supply Chain, is subject to legal requirements and also helps to comply with them. On top of that it processes financial transactions, controls and monitors physical facilities, consumes energy and reaches the market with your own products.

Effective controls

Sources

Frequently asked questions

Why is purchased standard software usually a supporting asset?

An ERP system or an office suite is valuable to you mainly because it carries information and processes. If it fails, the real damage happens to the data and workflows behind it. That is why the catalogue lists these types as supporting assets. Software you develop yourself or sell to customers, on the other hand, can be a business asset in its own right.

Do cloud services and SaaS applications belong in the software category?

Yes. The catalogue keeps cloud and collaboration services as a class of their own and lists SaaS applications in the website class. What matters is that you link the service to its provider, the contract and the information it processes. You also record the provider itself in the supply chain category.

How granular should my software entries be?

Record software at the level where responsibility and protection needs change: the ERP system as a whole, the customer platform, the internal ticketing system. Libraries and modules usually go with the application they belong to. For an overview of individual components and their versions, a software bill of materials (SBOM) is a better tool than the asset register.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.