Zum Hauptinhalt springen
Asset category · Asset register

AC04 Human

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

In a mechanical engineering company with 80 employees, only one administrator knows the credentials for the firewall, the virtualization platform and the backup system. When he is off work for six weeks after a cycling accident, nobody can renew an expired certificate, and remote access for the field sales team stays blocked for days. The asset register listed the server and the firewall; the person without whom neither of them worked was missing. People are supporting assets, and a single person often carries more than the organization chart reveals.

Employees, managers, external staff and contractually connected partners hold knowledge, permissions and responsibility. They are where workflows succeed or fail, and at the same time the favourite target of attackers. Asset category AC04 brings these groups of people together so that you can name them in the asset register, make their dependencies visible and rate their protection needs.

What belongs to it?

The catalogue splits the category into four asset classes. They differ mainly in how closely a person is bound to the organization and which rules therefore apply to them.

  • Employees. Permanent staff, temporary staff and contract workers, for example seasonal warehouse pickers during the peak season or an IT specialist who joins the team for a migration project.
  • Executives and management. C-level executives, department heads and middle management. They decide on budgets and approvals and often hold far-reaching access rights.
  • Consultants and contractors. External consultants, freelancers and independent contractors, for instance for graphic design, copywriting or software development. They often work with internal data without being part of internal routines.
  • Contractually connected stakeholders. Investors, board members such as non-executive directors or members of an audit committee, and partners such as resellers, technology partners or joint venture partners.

Why the category matters

ISO/IEC 27005 separates primary assets, meaning information and processes with value of their own, from supporting assets on which these rest. The catalogue lists all 11 asset types of this category as supporting assets, because people carry business assets by running processes and using information. The standard picks exactly this case in its own example of dependencies between assets: an administrator appears there as a human resource, and if he lacks the necessary training, the risk is passed on to the business process he looks after.

For the assessment this means that the protection needs of a role follow from the processes and information that depend on it. An accountant who is the only one able to run the payment cycle has high availability needs. An administrator with full access to all systems has high integrity and confidentiality needs, because a mistake or a successful deception immediately affects many assets. The standard also points out that misjudging how much an asset is worth distorts the picture of both consequences and likelihood.

Typical threats

In practice: recording assets in the asset register

Create roles and groups. Create entries for roles and groups of people and assign category, class and type (→ Asset Register in the Starter Kit). Employee data is personal data, so only what the risk assessment needs belongs in the register.

Identify key people and deputies. Record where knowledge or permissions depend on a single person and name a deputy. The → Competence Matrix shows who can take over which tasks.

Cover the life cycle. Joining, moving and leaving change permissions and duties. The → HR Security Policy governs screening, confidentiality and the return of assets.

Bind external parties by contract. Consultants, freelancers and partners need confidentiality agreements, limited access and a clear end to the engagement.

Relations to other categories

In the catalogue, people need and generate AC01 Information. They use and develop AC02 Software, use and service AC03 Hardware and are responsible for buildings and equipment. People administer money, create and own AC07 Intellectual Property and are part of the organization (AC08 Organizational): they belong to units, shape the culture and hold positions. They are subject to legal duties and responsible for complying with them, administer the supply chain, maintain and represent AC12 Relationships and analyse the market. Above all, they execute AC14 Processes, are responsible for them and approve them.

Effective controls

Sources

Frequently asked questions

Do I have to list every person by name in the asset register?

Roles and groups such as "management", "administrators" or "temporary warehouse staff" are usually enough. You record by name only key people whose knowledge or permissions cannot easily be covered by someone else. That keeps the register lean and the amount of employee data small.

Why are investors and partners in the human category?

The catalogue lists them as contractually connected stakeholders, because they receive information and hold rights towards the organization. An investor with access to the data room or a sales partner with customer lists carries risks into the organization and out of it. You record the partnership as a whole in the relationships category as well.

How do I rate the protection needs of a role?

Through the assets that depend on it. Ask which processes come to a halt if the role is unavailable, which information it knows and which permissions it holds. A trained deputy lowers the need for availability, while far-reaching rights raise the need for integrity and confidentiality.

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.