After a restructuring, an insurance broker splits its IT across two new teams. The annual review of access rights appears in none of the new role descriptions, and each team thinks the other is in charge. A year later, the auditor finds dozens of active accounts belonging to former employees. During the restructuring, a responsibility that had seemed self-evident was lost. Organizational assets are the invisible framework that responsibilities, knowledge and trust hang on.
Expertise, training, established practices, values, reputation, the organizational structure and ongoing projects cannot be touched. Even so, they decide whether the organization can fulfil its tasks and whether customers trust it. Asset category AC08 brings these assets 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 seven asset classes. Together they describe what the organization knows, how it works, what it stands for and how it is structured.
- Employee expertise. Technical skills, industry knowledge and experience, for example regulatory knowledge for the pharmaceutical sector or many years of practice in selling to large accounts.
- Training programmes. In-house training modules, educational resources and certification programmes, from onboarding new employees to an internal expert certificate.
- Best practices. Internal knowledge bases, documented practices and case studies, including reviews of failed projects or past security incidents.
- Culture and values. Organizational culture, core values and ethical standards such as the code of conduct, anti-corruption rules and rules on conflicts of interest.
- Reputation. Public perception, brand image and customer trust.
- Organizational structure. Departments, teams, positions, responsibilities, hierarchy levels and roles, such as the role of the data protection officer or top management’s responsibility for information security.
- Projects. Software, organizational development, technical and product projects, meaning time-limited undertakings such as introducing an ERP system or relocating a site.
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 business assets rest. The catalogue divides this category along exactly that line: knowledge in the form of expertise, training and best practices can be a primary asset, while structure, culture, reputation and projects count as supporting. Knowledge has value of its own because it cannot be replaced at short notice. Structures and projects, for their part, carry other assets by setting responsibilities and steering change.
Organizational assets also play a part in rating consequences. In clause 6.4.3.2, the standard lists among the consequence criteria the departure of skilled people and the know-how they take with them, effects on plans and deadlines, and harm to trust and standing. If you keep reputation and expertise as assets in the register, you can attach such consequences to a concrete asset and rate their size consistently.
Typical threats
- G 0.33 Loss of Personnel: expertise is lost when experts resign or are absent for a long time.
- G 0.18 Poor Planning or Lack of Adaptation: restructurings without a handover of tasks, projects without security requirements.
- G 0.27 Lack of Resources: too little time and staff for training, documentation and project work.
- G 0.19 Disclosure of Sensitive Information: a data leak whose main damage is to reputation.
- G 0.47 Harmful Side Effects of IT-Supported Attacks: your own systems are misused for attacks on third parties, and your standing suffers.
- G 0.35 Coercion, Extortion or Corruption: breaches of your own ethical standards that become public.
In practice: recording assets in the asset register
Map the structure. Create departments, roles and responsibilities as assets and assign category, class and type (→ Asset Register in the Starter Kit). The → RACI Matrix shows who is responsible for which security tasks.
Secure knowledge. Record skills that are indispensable for operations and link them to the people who hold them. The → Competence Matrix and the → Training Register show where knowledge rests on too few shoulders.
Keep projects with an end date. Add larger projects with their duration, responsible person and security requirements. When they are complete, the results pass into the other assets.
Prepare for reputational hits. Link reputation to the risks that hit it hardest, and record how you will communicate in an emergency (→ Crisis Communication Templates).
Relations to other categories
In the catalogue, the organization defines and generates AC01 Information. It is responsible for and operates AC02 Software, AC03 Hardware and physical assets. It encompasses people (AC04 Human) and is shaped by them. Organizational assets are responsible for and plan finances, define and own AC07 Intellectual Property, implement legal requirements and are subject to them. The organization commits to environmental goals, administers and assesses the supply chain, maintains and represents AC12 Relationships, positions itself in the market and analyses it. Finally, it operates and defines AC14 Processes.
Effective controls
- A.5.9 Inventory of Information and Other Associated Assets: roles, knowledge and projects in the register, with a responsible person.
- A.5.12 Classification of Information: classify internal knowledge, case studies and project documents appropriately.
- A.5.2 Information Security Roles and Responsibilities and A.5.4 Management Responsibilities: define responsibilities and hold managers to them.
- A.6.3 Information Security Awareness, Education and Training: build and refresh security knowledge.
- A.5.8 Information Security in Project Management: security requirements in every project from the start.
- A.5.37 Documented Operating Procedures and A.5.27 Learning from Information Security Incidents: write procedures down and learn from experience.
Sources
- ISO/IEC 27005:2022, Annex A.2.2: Assets, and clause 6.4.3.2 on consequence criteria
- ISO/IEC 27002:2022, clauses 5.2, 5.4, 5.8, 5.9, 5.12, 5.27, 5.37 and 6.3
- BSI IT-Grundschutz Compendium: elementary threats G 0.18 to G 0.47