Concept skos:Concept Code ID.AM-02.2

The inventory reflecting which software, services and systems are used in the organisation shall reflect changes in the organisation’s context and include all information necessary for effective accountability.

Also known as

skos:altLabel

Software inventory accuracy and completeness

Note

skos:note

The goal of this control is to ensure that inventories of software, services, and systems remain current and complete, enabling traceability, responsible ownership, and alignment with changes in the organisation’s operational and risk context. To achieve this goal:

  • Include Key Inventory Details Inventories should capture relevant attributes such as software title, publisher, initial install or use date, business purpose, version, deployment method, and decommission date. URLs or app store sources should be included where applicable.
  • Support Accountability Inventory records should enable traceability of actions and decisions, ensuring that responsible roles can be identified and held answerable for the use and management of software and services.
  • Reflect Organisational Changes Inventories should be updated to reflect changes such as new deployments, upgrades, or removals, including those affecting OT systems and embedded software components.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_02_2
All data (21 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

http://cyfun.data.gift/ontology#Requirement

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

A human-readable name for the subject.

ID.AM-02.2: The inventory reflecting which software, services and systems are used in the organisation shall reflect changes in the organisation’s context and include all information necessary for effective accountability.

http://cyfun.data.gift/ontology#requirementId

ID.AM-02.2

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p48

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p34

has broader

Relates a concept to a concept that is more general in meaning.

http://cyfun.data.gift/data/subcategory_ID.AM-02

note

A general note, for any purpose.

The goal of this control is to ensure that inventories of software, services, and systems remain current and complete, enabling traceability, responsible ownership, and alignment with changes in the organisation’s operational and risk context. To achieve this goal: • Include Key Inventory Details Inventories should capture relevant attributes such as software title, publisher, initial install or use date, business purpose, version, deployment method, and decommission date. URLs or app store sources should be included where applicable. • Support Accountability Inventory records should enable traceability of actions and decisions, ensuring that responsible roles can be identified and held answerable for the use and management of software and services. • Reflect Organisational Changes Inventories should be updated to reflect changes such as new deployments, upgrades, or removals, including those affecting OT systems and embedded software components.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that inventories of software, services, and systems remain current and complete, enabling traceability, responsible ownership, and alignment with changes in the organisation’s operational and risk context. To achieve this goal:</p><ul><li>Include Key Inventory Details Inventories should capture relevant attributes such as software title, publisher, initial install or use date, business purpose, version, deployment method, and decommission date. URLs or app store sources should be included where applicable.</li><li>Support Accountability Inventory records should enable traceability of actions and decisions, ensuring that responsible roles can be identified and held answerable for the use and management of software and services.</li><li>Reflect Organisational Changes Inventories should be updated to reflect changes such as new deployments, upgrades, or removals, including those affecting OT systems and embedded software components.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that inventories of software, services, and systems remain current and complete, enabling traceability, responsible ownership, and alignment with changes in the organisation’s operational and risk context. To achieve this goal: - Include Key Inventory Details Inventories should capture relevant attributes such as software title, publisher, initial install or use date, business purpose, version, deployment method, and decommission date. URLs or app store sources should be included where applicable. - Support Accountability Inventory records should enable traceability of actions and decisions, ensuring that responsible roles can be identified and held answerable for the use and management of software and services. - Reflect Organisational Changes Inventories should be updated to reflect changes such as new deployments, upgrades, or removals, including those affecting OT systems and embedded software components.

note

A general note, for any purpose.

The goal of this control is to ensure that inventories of software, services, and systems remain current and complete, enabling traceability, responsible ownership, and alignment with changes in the organisation’s operational and risk context. To achieve this goal: - Include Key Inventory Details Inventories should capture relevant attributes such as software title, publisher, initial install or use date, business purpose, version, deployment method, and decommission date. URLs or app store sources should be included where applicable. - Support Accountability Inventory records should enable traceability of actions and decisions, ensuring that responsible roles can be identified and held answerable for the use and management of software and services. - Reflect Organisational Changes Inventories should be updated to reflect changes such as new deployments, upgrades, or removals, including those affecting OT systems and embedded software components.

notation

A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme.

ID.AM-02.2

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

Software inventory accuracy and completeness

preferred label

A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.

The inventory reflecting which software, services and systems are used in the organisation shall reflect changes in the organisation’s context and include all information necessary for effective accountability.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_IMPORTANT

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

http://cyfun.data.gift/ontology#level

http://cyfun.data.gift/data/level_IMPORTANT

triple count

The number of triples associated with the subject.

19

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 21 of 21

References

Inverse links to the subject.