Direct links from the subject.
| Property | Value |
|---|---|
|
The subject is an instance of a class. |
|
|
The subject is an instance of a class. |
An idea or notion; a unit of thought. |
|
A human-readable name for the subject. |
ID.AM-02.1: An inventory of software, digital services, and business systems used within the organisation shall be documented, reviewed, and updated as changes occur. |
|
ID.AM-02.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p16 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p33 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p47 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
This control ensures that all software, digital services, and business systems used within the organisation are identified, tracked, and regularly updated. It focuses on the functional and intangible parts of the technology environment, such as applications, platforms, and cloud services, that operate on or interact with the under- lying infrastructure. Keeping this inventory up-to-date supports operational continuity, strengthens security, and helps meet compliance requirements. It is closely linked to ID.AM-01.1, which covers the physical and virtual infrastructure (such as servers, network devices, and cloud environments) that supports these systems. Together, both controls provide a complete view of the organisation’s technology landscape, from the founda- tional infrastructure to the applications and services that deliver business value. To achieve this goal, the following steps should be considered: • Identify Software and Services The inventory should include all applications, cloud services,APIs, and business systems (e.g. ERP, CRM, HR platforms). • Record Key Information Each entry should include version, owner, purpose, licence type, and deployment environment. • Use Automation Where Possible Automated discovery tools should be used to accurately detect and update software and services. • Maintain a Software Bill of Materials (SBOM) An SBOM should be maintained for critical or internally developed software to track components and dependencies. • Keep the Inventory up-to-date The inventoryshould be reviewed and updated regularly, especiallyafterinstallations, upgrades, orremovals. • Align with Infrastructure Inventory (ID.AM-01.1) Software records should be linked to the infrastructure they run on to provide a complete view of the tech- nology environment. |
|
A general note, for any purpose. |
This control ensures that all software, digital services, and business systems used within the organisation are identified, tracked, and regularly updated. It focuses on the functional and intangible parts of the technology environment, such as applications, platforms, and cloud services, that operate on or interact with the under- lying infrastructure. Keeping this inventory up-to-date supports operational continuity, strengthens security, and helps meet compliance requirements. It is closely linked to ID.AM-01.1, which covers the physical and virtual infrastructure (such as servers, network devices, and cloud environments) that supports these systems. Together, both controls provide a complete view of the organisation’s technology landscape, from the founda- tional infrastructure to the applications and services that deliver business value. To achieve this goal, the following steps should be considered: - Identify Software and Services The inventory should include all applications, cloud services,APIs, and business systems (e.g. ERP, CRM, HR platforms). - Record Key Information Each entry should include version, owner, purpose, licence type, and deployment environment. - Use Automation Where Possible Automated discovery tools should be used to accurately detect and update software and services. - Maintain a Software Bill of Materials (SBOM) An SBOM should be maintained for critical or internally developed software to track components and dependencies. - Keep the Inventory up-to-date The inventoryshould be reviewed and updated regularly, especiallyafterinstallations, upgrades, orremovals. - Align with Infrastructure Inventory (ID.AM-01.1) Software records should be linked to the infrastructure they run on to provide a complete view of the tech- nology environment. |
|
A general note, for any purpose. |
<div><p>This control ensures that all software, digital services, and business systems used within the organisation are identified, tracked, and regularly updated. It focuses on the functional and intangible parts of the technology environment, such as applications, platforms, and cloud services, that operate on or interact with the under- lying infrastructure. Keeping this inventory up-to-date supports operational continuity, strengthens security, and helps meet compliance requirements. It is closely linked to ID.AM-01.1, which covers the physical and virtual infrastructure (such as servers, network devices, and cloud environments) that supports these systems. Together, both controls provide a complete view of the organisation’s technology landscape, from the founda- tional infrastructure to the applications and services that deliver business value. To achieve this goal, the following steps should be considered:</p><ul><li>Identify Software and Services The inventory should include all applications, cloud services,APIs, and business systems (e.g. ERP, CRM, HR platforms).</li><li>Record Key Information Each entry should include version, owner, purpose, licence type, and deployment environment.</li><li>Use Automation Where Possible Automated discovery tools should be used to accurately detect and update software and services.</li><li>Maintain a Software Bill of Materials (SBOM) An SBOM should be maintained for critical or internally developed software to track components and dependencies.</li><li>Keep the Inventory up-to-date The inventoryshould be reviewed and updated regularly, especiallyafterinstallations, upgrades, orremovals.</li><li>Align with Infrastructure Inventory (ID.AM-01.1) Software records should be linked to the infrastructure they run on to provide a complete view of the tech- nology environment.</li></ul></div> |
|
A general note, for any purpose. |
This control ensures that all software, digital services, and business systems used within the organisation are identified, tracked, and regularly updated. It focuses on the functional and intangible parts of the technology environment, such as applications, platforms, and cloud services, that operate on or interact with the under- lying infrastructure. Keeping this inventory up-to-date supports operational continuity, strengthens security, and helps meet compliance requirements. It is closely linked to ID.AM-01.1, which covers the physical and virtual infrastructure (such as servers, network devices, and cloud environments) that supports these systems. Together, both controls provide a complete view of the organisation’s technology landscape, from the founda- tional infrastructure to the applications and services that deliver business value. To achieve this goal, the following steps should be considered: - Identify Software and Services The inventory should include all applications, cloud services,APIs, and business systems (e.g. ERP, CRM, HR platforms). - Record Key Information Each entry should include version, owner, purpose, licence type, and deployment environment. - Use Automation Where Possible Automated discovery tools should be used to accurately detect and update software and services. - Maintain a Software Bill of Materials (SBOM) An SBOM should be maintained for critical or internally developed software to track components and dependencies. - Keep the Inventory up-to-date The inventoryshould be reviewed and updated regularly, especiallyafterinstallations, upgrades, orremovals. - Align with Infrastructure Inventory (ID.AM-01.1) Software records should be linked to the infrastructure they run on to provide a complete view of the tech- nology environment. |
|
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.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Software and services inventory |
|
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. |
An inventory of software, digital services, and business systems used within the organisation shall be documented, reviewed, and updated as changes occur. |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
21 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 23 of 23
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1