Concept skos:Concept Code ID.AM-08.3

The organisation shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposition.

Also known as

skos:altLabel

Asset lifecycle accountability

Note

skos:note

The goal of this control is to ensure accountability for all business-critical assets throughout their lifecycle, including deployment, movement, and disposal, to reduce the risk of unauthorised access, data leakage, or operational disruption across ICT and OT environments. To achieve this goal:

  • Secure Assets Before Deployment Systems, hardware, software, and services should be properly configured and secured before being intro- duced into production environments.
  • Identify and Remove Redundant Assets Redundant or unused systems, software, and services that increase the attack surface should be periodically identified and removed.
  • Monitor and Document Asset Movements Movementsofbusiness-criticalassetsshouldbetracked,anddocumentationshouldbemaintainedtoensure traceability and accountability.
  • Authorise Asset Transfers Business-critical assets should onlybe allowed to enterorleave facilitieswith properAuthorisation, especially in OT environments where physical asset control is critical.
  • Dispose of Assets Securely Disposal of business-critical assets should be conducted in a secure, responsible, and auditable manner to prevent data leakage or unauthorised reuse.
  • Update Inventories Promptly Asset inventories should be updated whenever systems, hardware, software, or services are moved, trans- ferred, removed, or decommissioned.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_08_3
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-08.3: The organisation shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposition.

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

ID.AM-08.3

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p57

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p41

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure accountability for all business-critical assets throughout their lifecycle, including deployment, movement, and disposal, to reduce the risk of unauthorised access, data leakage, or operational disruption across ICT and OT environments. To achieve this goal: - Secure Assets Before Deployment Systems, hardware, software, and services should be properly configured and secured before being intro- duced into production environments. - Identify and Remove Redundant Assets Redundant or unused systems, software, and services that increase the attack surface should be periodically identified and removed. - Monitor and Document Asset Movements Movementsofbusiness-criticalassetsshouldbetracked,anddocumentationshouldbemaintainedtoensure traceability and accountability. - Authorise Asset Transfers Business-critical assets should onlybe allowed to enterorleave facilitieswith properAuthorisation, especially in OT environments where physical asset control is critical. - Dispose of Assets Securely Disposal of business-critical assets should be conducted in a secure, responsible, and auditable manner to prevent data leakage or unauthorised reuse. - Update Inventories Promptly Asset inventories should be updated whenever systems, hardware, software, or services are moved, trans- ferred, removed, or decommissioned.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure accountability for all business-critical assets throughout their lifecycle, including deployment, movement, and disposal, to reduce the risk of unauthorised access, data leakage, or operational disruption across ICT and OT environments. To achieve this goal:</p><ul><li>Secure Assets Before Deployment Systems, hardware, software, and services should be properly configured and secured before being intro- duced into production environments.</li><li>Identify and Remove Redundant Assets Redundant or unused systems, software, and services that increase the attack surface should be periodically identified and removed.</li><li>Monitor and Document Asset Movements Movementsofbusiness-criticalassetsshouldbetracked,anddocumentationshouldbemaintainedtoensure traceability and accountability.</li><li>Authorise Asset Transfers Business-critical assets should onlybe allowed to enterorleave facilitieswith properAuthorisation, especially in OT environments where physical asset control is critical.</li><li>Dispose of Assets Securely Disposal of business-critical assets should be conducted in a secure, responsible, and auditable manner to prevent data leakage or unauthorised reuse.</li><li>Update Inventories Promptly Asset inventories should be updated whenever systems, hardware, software, or services are moved, trans- ferred, removed, or decommissioned.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure accountability for all business-critical assets throughout their lifecycle, including deployment, movement, and disposal, to reduce the risk of unauthorised access, data leakage, or operational disruption across ICT and OT environments. To achieve this goal: • Secure Assets Before Deployment Systems, hardware, software, and services should be properly configured and secured before being intro- duced into production environments. • Identify and Remove Redundant Assets Redundant or unused systems, software, and services that increase the attack surface should be periodically identified and removed. • Monitor and Document Asset Movements Movementsofbusiness-criticalassetsshouldbetracked,anddocumentationshouldbemaintainedtoensure traceability and accountability. • Authorise Asset Transfers Business-critical assets should onlybe allowed to enterorleave facilitieswith properAuthorisation, especially in OT environments where physical asset control is critical. • Dispose of Assets Securely Disposal of business-critical assets should be conducted in a secure, responsible, and auditable manner to prevent data leakage or unauthorised reuse. • Update Inventories Promptly Asset inventories should be updated whenever systems, hardware, software, or services are moved, trans- ferred, removed, or decommissioned.

note

A general note, for any purpose.

The goal of this control is to ensure accountability for all business-critical assets throughout their lifecycle, including deployment, movement, and disposal, to reduce the risk of unauthorised access, data leakage, or operational disruption across ICT and OT environments. To achieve this goal: - Secure Assets Before Deployment Systems, hardware, software, and services should be properly configured and secured before being intro- duced into production environments. - Identify and Remove Redundant Assets Redundant or unused systems, software, and services that increase the attack surface should be periodically identified and removed. - Monitor and Document Asset Movements Movementsofbusiness-criticalassetsshouldbetracked,anddocumentationshouldbemaintainedtoensure traceability and accountability. - Authorise Asset Transfers Business-critical assets should onlybe allowed to enterorleave facilitieswith properAuthorisation, especially in OT environments where physical asset control is critical. - Dispose of Assets Securely Disposal of business-critical assets should be conducted in a secure, responsible, and auditable manner to prevent data leakage or unauthorised reuse. - Update Inventories Promptly Asset inventories should be updated whenever systems, hardware, software, or services are moved, trans- ferred, removed, or decommissioned.

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

alternative label

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

Asset lifecycle accountability

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 organisation shall enforce accountability for all its business-critical assets throughout the system lifecycle, including removal, transfers, and disposition.

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.