Zum Hauptinhalt springen
Asset category · Asset register

AC12 Relationships

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

An online shop notices on a Friday evening that customer data has leaked. Nobody knows which data protection authority is competent or through which channel a notification is filed. Management finds the notification form only on Monday morning, when the 72-hour deadline has almost run out. Meanwhile the first key accounts are calling, having learned about the incident from the press. Relationships with partners, customers and authorities are assets that need care and must be reachable quickly in an emergency.

Every organization sits in a web of partners, customers, initiatives and public bodies. Information, orders and trust flow through these relationships, and so do obligations and attacks. Asset category AC12 brings these relationships 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 four asset classes. They range from relationships the organization chooses freely to those it cannot avoid.

  • Partnerships. Strategic alliances, for instance for joint marketing or technology sharing, joint ventures and collaborations such as a research project with a university, joint development with a start-up or a pilot project with a key account.
  • Community engagement. Corporate social responsibility with reports and community investment, initiatives such as a sustainability or digitalization programme, and outreach programmes, for example sponsoring schools or offering apprenticeships to young people.
  • Clients and customers. Business customers, end consumers and users, and public administration as a customer, such as a city administration or a publicly owned hospital.
  • Public bodies. Supervisory authorities such as the data protection authority, the BSI, BaFin or market surveillance, administrative authorities such as the tax office, trade office, customs and patent office, law enforcement authorities, courts from the registry court to the labour court, and social insurance institutions and chambers.

Why the category matters

ISO/IEC 27005 distinguishes primary assets, meaning information and processes with value of their own, from supporting assets on which these rest. The catalogue allows partnerships to be primary assets and lists customer relationships, community engagement and public bodies as supporting assets. In Annex A.2.4.1 the standard describes the organization’s ecosystem of clients, partners, co-contractors and service providers, and points out that attackers look precisely for the most vulnerable connections within it.

The category also matters for consequences. Clause 6.4.3.2 lists adverse effects on interested parties and breached contracts or service levels among the consequence criteria. ISO 27001 requires in clause 4.2 that interested parties and their requirements be determined. If you keep your most important relationships as assets, you can judge which of them an incident would strain and which reporting channels then need to be open.

Typical threats

In practice: recording assets in the asset register

Create relationships. Create important partnerships, customer groups and public bodies as assets and assign category, class and type (→ Asset Register in the Starter Kit). Record key accounts with their own security requirements individually and all others as a group.

Link requirements. Link each relationship to the requirements it brings, such as contractual security clauses or notification duties (→ Stakeholder Requirements Register).

Record shared information. Note which information is exchanged in a partnership or with a customer, through which channel and under which agreement.

Ensure reachability. For authorities and important partners, record who makes contact in an emergency and through which channel (→ Stakeholder Communication Plan).

Relations to other categories

In the catalogue, relationships are described by AC01 Information and generate information themselves. They are enabled by AC02 Software, AC03 Hardware and physical assets, such as the customer portal, the phone system and the meeting room. People (AC04 Human) maintain and constitute them. Financial assets and AC07 Intellectual Property strengthen them, and in turn they affect finances. The organization maintains and represents them, AC09 Legal & Regulatory assets govern and protect them, and the environment influences them. The AC11 Supply Chain constitutes and enables relationships. These open up the AC13 Market, strengthen the organization’s position there and require suitable AC14 Processes.

Effective controls

Sources

Frequently asked questions

Why are authorities and courts in the asset register?

The organization does not own them, yet the relationship with them is an asset: authorities receive notifications, supervise and decide, courts keep registers and conduct proceedings. That is why the catalogue lists them as the public bodies class. If you record the competent office and the reporting channel in the register beforehand, you lose no time in an emergency.

How do customers here differ from the customer data in AC01?

This category holds the customer relationship itself, with trust, contract and revenue. The information category holds the data about customers, for example in the CRM or the support system. Link the two, and you see which relationships a data leak would strain the most.

Why can only partnerships be primary assets?

Alliances, joint ventures and collaborations create shared value, such as developments or market access, that the organization has helped to build itself. That is why the catalogue allows them to be business assets. It lists customer relationships, community engagement and public bodies as supporting assets.

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.