Zum Hauptinhalt springen
Asset category · Asset register

AC14 Processes

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

An electrical wholesaler falls victim to a ransomware attack. IT restores the systems in the order in which they appear on the server list: first the intranet, then time recording, then the document archive. Order processing, through which all revenue flows, waits until day four, because nobody had recorded which systems it relies on. Processes are the yardstick for which systems, data and people are protected and restored first.

Business processes combine all other assets into what the organization exists for: taking orders, developing products, issuing invoices, fulfilling obligations. When a process fails, it becomes clear how many assets depend on it. Asset category AC14 brings the processes together so that you can name them in the asset register, assign them to a responsible person and rate them by their protection needs.

What belongs to it?

The catalogue splits the category into two asset classes. The split follows the classic question of whether a process creates value for customers and the mission or makes other processes possible.

  • Primary business processes. Core processes such as order-to-cash, onboarding of new employees or product development. On top of these come secret processes and processes involving proprietary technology, for instance a special blending method or particular manufacturing steps, and processes required by contracts, laws or supervisors, such as deleting personal data, anti-money-laundering checks or the annual financial audit.
  • Secondary business processes. Supporting processes such as the IT help desk, maintenance by facility management or internal mail and document distribution.

Measured by the number of asset types, this is the smallest category in the catalogue. In the risk assessment it is nevertheless often the most important, because many other assets depend on every process.

Why the category matters

ISO/IEC 27005 distinguishes primary assets, also called business assets, from supporting assets. The standard explicitly names information and processes as primary assets, and the catalogue allows three of the four asset types to be primary assets. In the event-based approach, exactly these business assets are at the centre: you ask which events can hit them and what the consequences would be.

The standard shows the importance of processes in an example of its own. There, a process for handling orders and invoices depends on a web portal, a server, the network, an IT maintenance service and an administrator. If one of these supporting assets fails, the process stops. The standard recommends capturing such dependencies in a graph, so that no risk is overlooked and none is assessed twice. BSI IT-Grundschutz also starts its structure analysis with the business processes and derives protection needs from there to applications, systems and rooms.

Typical threats

In practice: recording assets in the asset register

Create processes with clear responsibility. Create each core process as an asset, assign category, class and type and name a process owner (→ Asset Register in the Starter Kit).

Map dependencies. Link each process to the information, applications, devices, people and service providers it needs. This produces the dependency graph the standard recommends.

Determine criticality. Use the → Business Impact Analysis to determine how long a process may be down and what damage an outage causes. These values feed into the protection needs and set the order in the → Business Continuity Plan.

Accompany changes. When a process is redesigned, outsourced or newly digitized, review its links and protection needs again.

Relations to other categories

In the catalogue, processes generate, consume and document AC01 Information. They are automated by AC02 Software, enabled by AC03 Hardware and executed and approved by people (AC04 Human). Physical assets enable them, and processes in turn restrict how those assets are used. Processes control and generate financial assets, protect and generate AC07 Intellectual Property and are operated and defined by the organization (AC08 Organizational). They fulfil the obligations arising from AC09 Legal & Regulatory assets, deplete environmental resources and measure environmental effects. They consume services from the AC11 Supply Chain and trigger new ones, are fulfilled through AC12 Relationships and address the AC13 Market.

Effective controls

Sources

Frequently asked questions

Why are processes almost always primary assets?

ISO 27005 explicitly names processes alongside information as business assets. The catalogue follows this and allows core processes, secret processes and legally required processes to be primary assets. Only supporting processes such as the help desk or facility management are listed as supporting assets.

How granular should processes be in the asset register?

At the level of your process map, meaning where responsibility and recovery time change, for example "order processing", "payroll" or "product development". Individual work steps stay in the process description. This keeps the register clear and the links to systems and data meaningful.

How do processes relate to the business impact analysis?

The business impact analysis determines how quickly a process must be running again after a disruption and what an outage costs. These values set the availability needs of the process in the register. Through the links, the systems, data and service providers the process relies on inherit them.

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.