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. |
PR.PS-03.1: Hardware used in business-critical environments shall be maintained, replaced, or removed based on its associated security and operational risk. |
|
PR.PS-03.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p123 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p85 |
|
|
Relates a concept to a concept that is more general in meaning. |
|
|
A general note, for any purpose. |
The goal of this control is to ensure that hardware used in business-critical environments remains secure, reli- able, and fit for purpose by managing it based on operational and security risks. To achieve this goal, the organisation should consider to: - Regularly assess whether hardware supports required security features (e.g. encryption, secure boot, firm- ware updates); replace hardware that cannot meet these needs. - Phase out end-of-life or unsupported hardware in a controlled manner. - Define and maintain a hardware lifecycle plan, including: - Inventory tracking - End-of-life timelines - Replacement schedules - Secure disposal procedures - Perform preventive maintenance and timely replacements to avoid unexpected failures that could impact operations or security. - Ensure hardware can support secure, up-to-date software; address any limitations that prevent this. |
|
A general note, for any purpose. |
The goal of this control is to ensure that hardware used in business-critical environments remains secure, reli- able, and fit for purpose by managing it based on operational and security risks. To achieve this goal, the organisation should consider to: • Regularly assess whether hardware supports required security features (e.g. encryption, secure boot, firm- ware updates); replace hardware that cannot meet these needs. • Phase out end-of-life or unsupported hardware in a controlled manner. • Define and maintain a hardware lifecycle plan, including: o Inventory tracking o End-of-life timelines o Replacement schedules o Secure disposal procedures • Perform preventive maintenance and timely replacements to avoid unexpected failures that could impact operations or security. • Ensure hardware can support secure, up-to-date software; address any limitations that prevent this. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that hardware used in business-critical environments remains secure, reli- able, and fit for purpose by managing it based on operational and security risks. To achieve this goal, the organisation should consider to:</p><ul><li>Regularly assess whether hardware supports required security features (e.g. encryption, secure boot, firm- ware updates); replace hardware that cannot meet these needs.</li><li>Phase out end-of-life or unsupported hardware in a controlled manner.</li><li>Define and maintain a hardware lifecycle plan, including:<ul><li>Inventory tracking</li><li>End-of-life timelines</li><li>Replacement schedules</li><li>Secure disposal procedures</li></ul></li><li>Perform preventive maintenance and timely replacements to avoid unexpected failures that could impact operations or security.</li><li>Ensure hardware can support secure, up-to-date software; address any limitations that prevent this.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that hardware used in business-critical environments remains secure, reli- able, and fit for purpose by managing it based on operational and security risks. To achieve this goal, the organisation should consider to: - Regularly assess whether hardware supports required security features (e.g. encryption, secure boot, firm- ware updates); replace hardware that cannot meet these needs. - Phase out end-of-life or unsupported hardware in a controlled manner. - Define and maintain a hardware lifecycle plan, including: - Inventory tracking - End-of-life timelines - Replacement schedules - Secure disposal procedures - Perform preventive maintenance and timely replacements to avoid unexpected failures that could impact operations or security. - Ensure hardware can support secure, up-to-date software; address any limitations that prevent this. |
|
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. |
PR.PS-03.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Hardware lifecycle risk management |
|
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. |
Hardware used in business-critical environments shall be maintained, replaced, or removed based on its associated security and operational risk. |
|
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. |
http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT |
|
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. |
19 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 21 of 21
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1