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-08.5: The organisation shall ensure that disposal actions are approved, tracked, docu- mented, and verified. |
|
ID.AM-08.5 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p58 |
|
|
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 all disposal actions involving information systems, data, or physical assets are properly authorised, traceable, and verifiable to reduce risks, maintain compliance, and protect sensitive information, especially in operational technology (OT) environments. To achieve this goal, the following steps should be considered: • Approval: Disposal actions should be reviewed and approved by authorised personnel before execution. This ensures alignment with internal policies and external regulations. • Tracking: Each disposal action should be logged with key details, including the asset or media type, disposal method, date, and individuals involved. • Documentation: All steps, from approval to verification, should be clearly documented. This includes approval records, tracking logs, and any supporting evidence. • Verification: Disposal should be verified to confirm it was completed correctly. This may involve checking that data was securely wiped or that physical destruction was effective. This structured approach helps maintain accountability and security, particularly in OT environments where improper disposal can lead to operational disruptions or safety risks. |
|
A general note, for any purpose. |
The goal of this control is to ensure that all disposal actions involving information systems, data, or physical assets are properly authorised, traceable, and verifiable to reduce risks, maintain compliance, and protect sensitive information, especially in operational technology (OT) environments. To achieve this goal, the following steps should be considered: - Approval: Disposal actions should be reviewed and approved by authorised personnel before execution. This ensures alignment with internal policies and external regulations. - Tracking: Each disposal action should be logged with key details, including the asset or media type, disposal method, date, and individuals involved. - Documentation: All steps, from approval to verification, should be clearly documented. This includes approval records, tracking logs, and any supporting evidence. - Verification: Disposal should be verified to confirm it was completed correctly. This may involve checking that data was securely wiped or that physical destruction was effective. This structured approach helps maintain accountability and security, particularly in OT environments where improper disposal can lead to operational disruptions or safety risks. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that all disposal actions involving information systems, data, or physical assets are properly authorised, traceable, and verifiable to reduce risks, maintain compliance, and protect sensitive information, especially in operational technology (OT) environments. To achieve this goal, the following steps should be considered:</p><ul><li>Approval: Disposal actions should be reviewed and approved by authorised personnel before execution. This ensures alignment with internal policies and external regulations.</li><li>Tracking: Each disposal action should be logged with key details, including the asset or media type, disposal method, date, and individuals involved.</li><li>Documentation: All steps, from approval to verification, should be clearly documented. This includes approval records, tracking logs, and any supporting evidence.</li><li>Verification: Disposal should be verified to confirm it was completed correctly. This may involve checking that data was securely wiped or that physical destruction was effective. This structured approach helps maintain accountability and security, particularly in OT environments where improper disposal can lead to operational disruptions or safety risks.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that all disposal actions involving information systems, data, or physical assets are properly authorised, traceable, and verifiable to reduce risks, maintain compliance, and protect sensitive information, especially in operational technology (OT) environments. To achieve this goal, the following steps should be considered: - Approval: Disposal actions should be reviewed and approved by authorised personnel before execution. This ensures alignment with internal policies and external regulations. - Tracking: Each disposal action should be logged with key details, including the asset or media type, disposal method, date, and individuals involved. - Documentation: All steps, from approval to verification, should be clearly documented. This includes approval records, tracking logs, and any supporting evidence. - Verification: Disposal should be verified to confirm it was completed correctly. This may involve checking that data was securely wiped or that physical destruction was effective. This structured approach helps maintain accountability and security, particularly in OT environments where improper disposal can lead to operational disruptions or safety risks. |
|
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.5 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Asset disposal approval and tracking |
|
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 ensure that disposal actions are approved, tracked, docu- mented, and verified. |
|
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_IMPORTANT_to_ESSENTIAL |
|
Relates a resource (for example a concept) to a concept scheme in which it is included. |
|
|
The number of triples associated with the subject. |
17 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 19 of 19
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1