Concept skos:Concept Code ID.AM-05.1

The organisation’s assets shall be prioritised based on classification, criticality, and business value.

Also known as

skos:altLabel

Asset classification and prioritisation

Note

skos:note

The goal of this control is to ensure that all organisational assets, such as devices, systems, services, data, and business processes, are prioritised based on their classification, criticality, and business value. This prioritisation helps direct protection efforts toward the most important assets, supporting operational continuity, security, and compliance. To make this happen, the following steps should be considered:

  • Asset Identification All relevant assets, including devices, systems, software, cloud services, data, employees, and business processes, should be identified and recorded in a central inventory.
  • Asset Classification Each asset should be classified based on its role:
    • Primary assets should be defined as those directly supporting core business functions.
    • Secondary assets should be defined as those that support, protect, or enable primary assets.
  • CriticalityAssessment
    • The organisation should assess how critical each asset is to business continuity.
    • The assessment should consider potential impacts such as operational disruption, financial loss, legal or regulatory consequences, safety risks, and reputational damage.
  • Prioritisation Method A consistent scoring or ranking method should be used to prioritise assets based on classification, criticality, and business value.
  • Ownership Assignment Each asset should have an assigned owner responsible for maintaining accurate and up-to-date information.
  • Regular Review Asset classifications and priorities should be reviewed at least annually or when significant changes occur (e.g. new systems, business restructuring).
  • Documentation and Evidence
    • The asset register should include classification, prioritisation criteria, assigned owners, and evidence of regular reviews.
    • Definitions of primary and secondary assets should be clearly documented.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_05_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-05.1: The organisation’s assets shall be prioritised based on classification, criticality, and business value.

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

ID.AM-05.1

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p17

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p53

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p37

has broader

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

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

note

A general note, for any purpose.

The goal of this control is to ensure that all organisational assets, such as devices, systems, services, data, and business processes, are prioritised based on their classification, criticality, and business value. This prioritisation helps direct protection efforts toward the most important assets, supporting operational continuity, security, and compliance. To make this happen, the following steps should be considered: - Asset Identification All relevant assets, including devices, systems, software, cloud services, data, employees, and business processes, should be identified and recorded in a central inventory. - Asset Classification Each asset should be classified based on its role: - Primary assets should be defined as those directly supporting core business functions. - Secondary assets should be defined as those that support, protect, or enable primary assets. - CriticalityAssessment - The organisation should assess how critical each asset is to business continuity. - The assessment should consider potential impacts such as operational disruption, financial loss, legal or regulatory consequences, safety risks, and reputational damage. - Prioritisation Method A consistent scoring or ranking method should be used to prioritise assets based on classification, criticality, and business value. - Ownership Assignment Each asset should have an assigned owner responsible for maintaining accurate and up-to-date information. - Regular Review Asset classifications and priorities should be reviewed at least annually or when significant changes occur (e.g. new systems, business restructuring). - Documentation and Evidence - The asset register should include classification, prioritisation criteria, assigned owners, and evidence of regular reviews. - Definitions of primary and secondary assets should be clearly documented.

note

A general note, for any purpose.

The goal of this control is to ensure that all organisational assets, such as devices, systems, services, data, and business processes, are prioritised based on their classification, criticality, and business value. This prioritisation helps direct protection efforts toward the most important assets, supporting operational continuity, security, and compliance. To make this happen, the following steps should be considered: - Asset Identification All relevant assets, including devices, systems, software, cloud services, data, employees, and business processes, should be identified and recorded in a central inventory. - Asset Classification Each asset should be classified based on its role: - Primary assets should be defined as those directly supporting core business functions. - Secondary assets should be defined as those that support, protect, or enable primary assets. - CriticalityAssessment - The organisation should assess how critical each asset is to business continuity. - The assessment should consider potential impacts such as operational disruption, financial loss, legal or regulatory consequences, safety risks, and reputational damage. - Prioritisation Method A consistent scoring or ranking method should be used to prioritise assets based on classification, criticality, and business value. - Ownership Assignment Each asset should have an assigned owner responsible for maintaining accurate and up-to-date information. - Regular Review Asset classifications and priorities should be reviewed at least annually or when significant changes occur (e.g. new systems, business restructuring). - Documentation and Evidence - The asset register should include classification, prioritisation criteria, assigned owners, and evidence of regular reviews. - Definitions of primary and secondary assets should be clearly documented.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that all organisational assets, such as devices, systems, services, data, and business processes, are prioritised based on their classification, criticality, and business value. This prioritisation helps direct protection efforts toward the most important assets, supporting operational continuity, security, and compliance. To make this happen, the following steps should be considered:</p><ul><li>Asset Identification All relevant assets, including devices, systems, software, cloud services, data, employees, and business processes, should be identified and recorded in a central inventory.</li><li>Asset Classification Each asset should be classified based on its role:<ul><li>Primary assets should be defined as those directly supporting core business functions.</li><li>Secondary assets should be defined as those that support, protect, or enable primary assets.</li></ul></li><li>CriticalityAssessment<ul><li>The organisation should assess how critical each asset is to business continuity.</li><li>The assessment should consider potential impacts such as operational disruption, financial loss, legal or regulatory consequences, safety risks, and reputational damage.</li></ul></li><li>Prioritisation Method A consistent scoring or ranking method should be used to prioritise assets based on classification, criticality, and business value.</li><li>Ownership Assignment Each asset should have an assigned owner responsible for maintaining accurate and up-to-date information.</li><li>Regular Review Asset classifications and priorities should be reviewed at least annually or when significant changes occur (e.g. new systems, business restructuring).</li><li>Documentation and Evidence<ul><li>The asset register should include classification, prioritisation criteria, assigned owners, and evidence of regular reviews.</li><li>Definitions of primary and secondary assets should be clearly documented.</li></ul></li></ul></div>

note

A general note, for any purpose.

The goal of this control is to ensure that all organisational assets, such as devices, systems, services, data, and business processes, are prioritised based on their classification, criticality, and business value. This prioritisation helps direct protection efforts toward the most important assets, supporting operational continuity, security, and compliance. To make this happen, the following steps should be considered: • Asset Identification All relevant assets, including devices, systems, software, cloud services, data, employees, and business processes, should be identified and recorded in a central inventory. • Asset Classification Each asset should be classified based on its role: o Primary assets should be defined as those directly supporting core business functions. o Secondary assets should be defined as those that support, protect, or enable primary assets. • CriticalityAssessment o The organisation should assess how critical each asset is to business continuity. o The assessment should consider potential impacts such as operational disruption, financial loss, legal or regulatory consequences, safety risks, and reputational damage. • Prioritisation Method A consistent scoring or ranking method should be used to prioritise assets based on classification, criticality, and business value. • Ownership Assignment Each asset should have an assigned owner responsible for maintaining accurate and up-to-date information. • Regular Review Asset classifications and priorities should be reviewed at least annually or when significant changes occur (e.g. new systems, business restructuring). • Documentation and Evidence o The asset register should include classification, prioritisation criteria, assigned owners, and evidence of regular reviews. o Definitions of primary and secondary assets should be clearly documented.

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

alternative label

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

Asset classification and prioritisation

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’s assets shall be prioritised based on classification, criticality, and business value.

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.