Zum Hauptinhalt springen
Asset category · Asset register

AC01 Information

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

A craft business lists its server, twenty laptops and the phone system in its first asset register. The quote calculations, the customer database and the customers’ building plans are missing. When the server fails, the hardware is replaced within two days; what is really gone is the data, for which there was no backup. The information category shows what protection is actually about.

In most organizations, information is both the most valuable and the least visible asset. It is spread across databases, mailboxes, chats and filing cabinets. Asset category AC01 brings it together so that you can name it 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 six asset classes. Each class groups information that is created and used in a similar way and therefore carries similar risks.

  • Business data and databases. Financial records, transactional and product data, plus the login and account data of employees. This is where the figures live that the organization works and decides with.
  • Documents. Contracts, policies, manuals, operating procedures, research reports, official presentations, standards, laws and specifications from customers and suppliers. They record what applies and what has been agreed.
  • Records. Emails, personnel files, calendars, chats, meeting notes, internal presentations, audit logs and archives. They document what has happened and often serve as evidence towards authorities or courts.
  • Customer data. Account and CRM data, support histories, loyalty programmes, personal details, purchase history, preferences, login data and survey results. Here business value and privacy meet head on.
  • Health policies. Occupational safety rules, health promotion programmes and health insurance plans for employees.
  • Information security systems. Firewalls and VPNs, the systems that protect all the other information.

Why the category matters

ISO/IEC 27005 distinguishes two kinds of assets. Primary assets, also called business assets, are information and processes that are valuable to the organization in themselves. Supporting assets are the components these business assets rest on: systems, networks, rooms, people. Information is therefore almost always the starting point from which the risk assessment moves on to the supporting assets.

The protection needs of a server follow from the information stored on it. A file server holding canteen menus needs less protection than one holding design data. Without rating the information, the protection needs of the technology can only be guessed. The standard also recommends recording the dependencies between assets, so that one risk does not end up in the assessment twice, first on the server and again on the data it holds.

Typical threats

In practice: recording assets in the asset register

Form bodies of information. Group information into bodies that share a responsible person and similar protection needs, such as “payroll data” or “quotes and calculations”. Assign each body a category, class and type (→ Asset Register in the Starter Kit).

Rate the protection needs. For each body, assess what a loss of confidentiality, integrity and availability would mean. Your organization’s classification levels provide the frame (→ Information Classification & Labelling Policy).

Link the storage locations. Record on which software, which hardware and with which service providers a body of information resides. Only this link shows which systems inherit the protection needs of the information.

Keep it up to date. New applications, new customer groups and new partnerships create new bodies of information. Review the register at least once a year and with every larger project.

Relations to other categories

In the catalogue, information is connected to almost all other categories. Software processes information, hardware stores it, and information configures both. People need information for their work and are empowered by it. Information describes and controls physical assets, represents financial assets, constitutes intellectual property, defines the organization, fulfils legal duties and is subject to them, measures environmental assets and controls the supply chain. These relations are the thread to follow when you move from a body of information to the assets that carry it.

Effective controls

Sources

Frequently asked questions

Why are firewalls and VPNs filed under the information category?

Because the catalogue keeps the systems that protect information as a class right next to the information itself. Protected asset and protective measure sit side by side, and when you record your assets you notice if an important data store has no protection attached. Technically, firewalls and VPNs are supporting assets, so the catalogue does not offer them as primary assets.

Do I have to record every file as an asset of its own?

No. You record bodies of information that differ in protection needs and responsibility, such as "customer data in the CRM" or "personnel files". A single file only becomes an asset of its own if it needs special protection by itself, for example a key repository or an acquisition plan.

How does information relate to the other categories?

Almost every other category carries, processes or uses information: software processes it, hardware stores it, people need it for their work. That is why the information category is often where the risk assessment starts. From there you trace which systems and which people hold it.

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.