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.8: The organisation shall pre-approve, monitor and enforce maintenance tools for use on its critical systems. |
|
ID.AM-08.8 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p60 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p43 |
|
|
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 maintenance tools used on critical systems are pre-approved, monitored, and enforced to protect system integrity, safety, and operational continuity. In OT environments, improper tool use can interfere with physical processes, making control over tool approval and usage essential for oper- ational safety and reliability. To achieve this goal, the organisation should: - Identify Critical Systems Systems that impact safety, quality, regulatory compliance, or operational throughput should be classified as critical. Metrics such as Mean Time to Repair (MTTR) and Mean Time Between Failures (MTBF) should support this classification. - Pre-Approve Tools Only maintenance tools that have been reviewed and approved should be allowed for use on critical systems. This includes both hardware and software tools such as diagnostic devices, packet sniffers, and laptops. - Monitor Usage The use of maintenance tools on critical systems should be actively monitored to detect unauthorised or unsafe activity. - Enforce Controls Policies and technical controls should be in place to prevent the use of unapproved tools and to ensure con- formance with internal procedures and compliance with applicable laws and regulations. |
|
A general note, for any purpose. |
The goal of this control is to ensure that maintenance tools used on critical systems are pre-approved, monitored, and enforced to protect system integrity, safety, and operational continuity. In OT environments, improper tool use can interfere with physical processes, making control over tool approval and usage essential for oper- ational safety and reliability. To achieve this goal, the organisation should: - Identify Critical Systems Systems that impact safety, quality, regulatory compliance, or operational throughput should be classified as critical. Metrics such as Mean Time to Repair (MTTR) and Mean Time Between Failures (MTBF) should support this classification. - Pre-Approve Tools Only maintenance tools that have been reviewed and approved should be allowed for use on critical systems. This includes both hardware and software tools such as diagnostic devices, packet sniffers, and laptops. - Monitor Usage The use of maintenance tools on critical systems should be actively monitored to detect unauthorised or unsafe activity. - Enforce Controls Policies and technical controls should be in place to prevent the use of unapproved tools and to ensure con- formance with internal procedures and compliance with applicable laws and regulations. |
|
A general note, for any purpose. |
The goal of this control is to ensure that maintenance tools used on critical systems are pre-approved, monitored, and enforced to protect system integrity, safety, and operational continuity. In OT environments, improper tool use can interfere with physical processes, making control over tool approval and usage essential for oper- ational safety and reliability. To achieve this goal, the organisation should: • Identify Critical Systems Systems that impact safety, quality, regulatory compliance, or operational throughput should be classified as critical. Metrics such as Mean Time to Repair (MTTR) and Mean Time Between Failures (MTBF) should support this classification. • Pre-Approve Tools Only maintenance tools that have been reviewed and approved should be allowed for use on critical systems. This includes both hardware and software tools such as diagnostic devices, packet sniffers, and laptops. • Monitor Usage The use of maintenance tools on critical systems should be actively monitored to detect unauthorised or unsafe activity. • Enforce Controls Policies and technical controls should be in place to prevent the use of unapproved tools and to ensure con- formance with internal procedures and compliance with applicable laws and regulations. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that maintenance tools used on critical systems are pre-approved, monitored, and enforced to protect system integrity, safety, and operational continuity. In OT environments, improper tool use can interfere with physical processes, making control over tool approval and usage essential for oper- ational safety and reliability. To achieve this goal, the organisation should:</p><ul><li>Identify Critical Systems Systems that impact safety, quality, regulatory compliance, or operational throughput should be classified as critical. Metrics such as Mean Time to Repair (MTTR) and Mean Time Between Failures (MTBF) should support this classification.</li><li>Pre-Approve Tools Only maintenance tools that have been reviewed and approved should be allowed for use on critical systems. This includes both hardware and software tools such as diagnostic devices, packet sniffers, and laptops.</li><li>Monitor Usage The use of maintenance tools on critical systems should be actively monitored to detect unauthorised or unsafe activity.</li><li>Enforce Controls Policies and technical controls should be in place to prevent the use of unapproved tools and to ensure con- formance with internal procedures and compliance with applicable laws and regulations.</li></ul></div> |
|
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.8 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Maintenance tools approval and monitoring |
|
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 pre-approve, monitor and enforce maintenance tools for use on its critical systems. |
|
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