Concept skos:Concept Code ID.AM-01.1

An inventory of physical and virtual infrastructure assets — such as hardware, net- work devices, and cloud-hosted environments — that support information process- ing shall be documented, reviewed, and updated as changes occur.

Also known as

skos:altLabel

Hardware asset inventory

Note

skos:note

The goal of this control is to ensure that critical systems and services remain available by implementing redun- dancy in line with organisational, legal, and regulatory availability requirements. While ID.AM-01.1 focuses on the infrastructure layer, this control is closelylinked to ID.AM-02.1which tracks the software and services that run on top of it, such as applications, platforms, and digital tools. Together, they provide a full picture of the organisation’s technology environment. To achieve the goal of ID.AM-01.1, the following should be considered:

  • Organisations should identify and document all physical and virtual infrastructure assets that support infor- mation processing, including servers, workstations, network devices, storage systems, and cloud-hosted resources.
  • The inventory should include key attributes such as asset type, location, owner, configuration, and lifecycle status.
  • Organisations should consider automated asset discovery and management tools where possible to ensure accuracy and real-time updates.
  • The inventory should be reviewed and updated regularly, especially following changes such as deployments, decommissions, or relocations.
  • The inventory should be accessible to relevant stakeholders and should be integrated with risk management and incident response processes.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_01_1
All data (23 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-01.1: An inventory of physical and virtual infrastructure assets — such as hardware, net- work devices, and cloud-hosted environments — that support information process- ing shall be documented, reviewed, and updated as changes occur.

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

ID.AM-01.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p31

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p15

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p45

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure that critical systems and services remain available by implementing redun- dancy in line with organisational, legal, and regulatory availability requirements. While ID.AM-01.1 focuses on the infrastructure layer, this control is closelylinked to ID.AM-02.1which tracks the software and services that run on top of it, such as applications, platforms, and digital tools. Together, they provide a full picture of the organisation’s technology environment. To achieve the goal of ID.AM-01.1, the following should be considered: • Organisations should identify and document all physical and virtual infrastructure assets that support infor- mation processing, including servers, workstations, network devices, storage systems, and cloud-hosted resources. • The inventory should include key attributes such as asset type, location, owner, configuration, and lifecycle status. • Organisations should consider automated asset discovery and management tools where possible to ensure accuracy and real-time updates. • The inventory should be reviewed and updated regularly, especially following changes such as deployments, decommissions, or relocations. • The inventory should be accessible to relevant stakeholders and should be integrated with risk management and incident response processes.

note

A general note, for any purpose.

The goal of this control is to ensure that critical systems and services remain available by implementing redun- dancy in line with organisational, legal, and regulatory availability requirements. While ID.AM-01.1 focuses on the infrastructure layer, this control is closelylinked to ID.AM-02.1which tracks the software and services that run on top of it, such as applications, platforms, and digital tools. Together, they provide a full picture of the organisation’s technology environment. To achieve the goal of ID.AM-01.1, the following should be considered: - Organisations should identify and document all physical and virtual infrastructure assets that support infor- mation processing, including servers, workstations, network devices, storage systems, and cloud-hosted resources. - The inventory should include key attributes such as asset type, location, owner, configuration, and lifecycle status. - Organisations should consider automated asset discovery and management tools where possible to ensure accuracy and real-time updates. - The inventory should be reviewed and updated regularly, especially following changes such as deployments, decommissions, or relocations. - The inventory should be accessible to relevant stakeholders and should be integrated with risk management and incident response processes.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that critical systems and services remain available by implementing redun- dancy in line with organisational, legal, and regulatory availability requirements. While ID.AM-01.1 focuses on the infrastructure layer, this control is closelylinked to ID.AM-02.1which tracks the software and services that run on top of it, such as applications, platforms, and digital tools. Together, they provide a full picture of the organisation’s technology environment. To achieve the goal of ID.AM-01.1, the following should be considered:</p><ul><li>Organisations should identify and document all physical and virtual infrastructure assets that support infor- mation processing, including servers, workstations, network devices, storage systems, and cloud-hosted resources.</li><li>The inventory should include key attributes such as asset type, location, owner, configuration, and lifecycle status.</li><li>Organisations should consider automated asset discovery and management tools where possible to ensure accuracy and real-time updates.</li><li>The inventory should be reviewed and updated regularly, especially following changes such as deployments, decommissions, or relocations.</li><li>The inventory should be accessible to relevant stakeholders and should be integrated with risk management and incident response processes.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that critical systems and services remain available by implementing redun- dancy in line with organisational, legal, and regulatory availability requirements. While ID.AM-01.1 focuses on the infrastructure layer, this control is closelylinked to ID.AM-02.1which tracks the software and services that run on top of it, such as applications, platforms, and digital tools. Together, they provide a full picture of the organisation’s technology environment. To achieve the goal of ID.AM-01.1, the following should be considered: - Organisations should identify and document all physical and virtual infrastructure assets that support infor- mation processing, including servers, workstations, network devices, storage systems, and cloud-hosted resources. - The inventory should include key attributes such as asset type, location, owner, configuration, and lifecycle status. - Organisations should consider automated asset discovery and management tools where possible to ensure accuracy and real-time updates. - The inventory should be reviewed and updated regularly, especially following changes such as deployments, decommissions, or relocations. - The inventory should be accessible to relevant stakeholders and should be integrated with risk management and incident response processes.

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-01.1

alternative label

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

Hardware asset inventory

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.

An inventory of physical and virtual infrastructure assets — such as hardware, net- work devices, and cloud-hosted environments — that support information process- ing shall be documented, reviewed, and updated as changes occur.

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

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_BASIC

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_BASIC

triple count

The number of triples associated with the subject.

21

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 23 of 23

References

Inverse links to the subject.