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.11: Remote maintenance and diagnostic activities of organisational assets shall be pre-approved and the performance logged. |
|
ID.AM-08.11 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p61 |
|
|
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 remote maintenance and diagnostic activities are authorised, traceable, and secure. In OTenvironments, remote maintenance must be tightly controlled, as unauthorised changes can directly affect the safety and stability of physical systems. To achieve this goal, the organisation should: - Pre-Approve Activities All remote maintenance and diagnostic activities should be reviewed and approved before execution. - Log Performance Each remote session should be logged in detail, including time, duration, personnel involved, and actions taken. - Establish Logging Procedures Logging and monitoring procedures should be documented, approved, communicated, applied, and regularly reviewed, ideally on an annual basis. - Prevent Unauthorised Changes Technical and procedural measures should be implemented to detect or prevent unauthorised changes to systems, configurations, applications, or infrastructure during remote access. - Ensure Conformance and Compliance All activities should conform to internal policies and comply with applicable laws, regulations, and industry standards. |
|
A general note, for any purpose. |
The goal of this control is to ensure that remote maintenance and diagnostic activities are authorised, traceable, and secure. In OTenvironments, remote maintenance must be tightly controlled, as unauthorised changes can directly affect the safety and stability of physical systems. To achieve this goal, the organisation should: - Pre-Approve Activities All remote maintenance and diagnostic activities should be reviewed and approved before execution. - Log Performance Each remote session should be logged in detail, including time, duration, personnel involved, and actions taken. - Establish Logging Procedures Logging and monitoring procedures should be documented, approved, communicated, applied, and regularly reviewed, ideally on an annual basis. - Prevent Unauthorised Changes Technical and procedural measures should be implemented to detect or prevent unauthorised changes to systems, configurations, applications, or infrastructure during remote access. - Ensure Conformance and Compliance All activities should conform to internal policies and comply with applicable laws, regulations, and industry standards. |
|
A general note, for any purpose. |
The goal of this control is to ensure that remote maintenance and diagnostic activities are authorised, traceable, and secure. In OTenvironments, remote maintenance must be tightly controlled, as unauthorised changes can directly affect the safety and stability of physical systems. To achieve this goal, the organisation should: • Pre-Approve Activities All remote maintenance and diagnostic activities should be reviewed and approved before execution. • Log Performance Each remote session should be logged in detail, including time, duration, personnel involved, and actions taken. • Establish Logging Procedures Logging and monitoring procedures should be documented, approved, communicated, applied, and regularly reviewed, ideally on an annual basis. • Prevent Unauthorised Changes Technical and procedural measures should be implemented to detect or prevent unauthorised changes to systems, configurations, applications, or infrastructure during remote access. • Ensure Conformance and Compliance All activities should conform to internal policies and comply with applicable laws, regulations, and industry standards. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that remote maintenance and diagnostic activities are authorised, traceable, and secure. In OTenvironments, remote maintenance must be tightly controlled, as unauthorised changes can directly affect the safety and stability of physical systems. To achieve this goal, the organisation should:</p><ul><li>Pre-Approve Activities All remote maintenance and diagnostic activities should be reviewed and approved before execution.</li><li>Log Performance Each remote session should be logged in detail, including time, duration, personnel involved, and actions taken.</li><li>Establish Logging Procedures Logging and monitoring procedures should be documented, approved, communicated, applied, and regularly reviewed, ideally on an annual basis.</li><li>Prevent Unauthorised Changes Technical and procedural measures should be implemented to detect or prevent unauthorised changes to systems, configurations, applications, or infrastructure during remote access.</li><li>Ensure Conformance and Compliance All activities should conform to internal policies and comply with applicable laws, regulations, and industry standards.</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.11 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Remote maintenance pre-approval and logging |
|
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. |
Remote maintenance and diagnostic activities of organisational assets shall be pre-approved and the performance logged. |
|
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