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.13: The organisation shall require remote maintenance diagnostic services to be per- formed from a system that implements security features similar to the security features implemented on the equivalent organisation's critical system. |
|
ID.AM-08.13 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p62 |
|
|
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 services are performed from sys- tems that implement securityfeatures equivalent to those of the organisation’s critical systems. In Operational Technology (OT) environments, this alignment is essential to maintain a consistent security posture, prevent the introduction of vulnerabilities, and protect the safety, reliability, and continuity of physical operations. To achieve this goal, the organisation should: • Use StrongAuthentication: Remote systems should implement multi-factor authentication to ensure access is restricted to authorised personnel. • Maintain Activity Records: Detailed logs of all remote maintenance activities should be maintained and reviewed regularly to detect anomalies or unauthorised actions. • Align Tools and Procedures: All tools and procedures used during remote maintenance should align with organisational policies and be documented in the relevant cybersecurity or information security plans. • TerminateSessions: Remote sessions should be properlyterminated once maintenance is complete, to prevent lingering access. • Ensure Conformance and Compliance: Remote systems and activities should conform to internal security requirements 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 services are performed from sys- tems that implement securityfeatures equivalent to those of the organisation’s critical systems. In Operational Technology (OT) environments, this alignment is essential to maintain a consistent security posture, prevent the introduction of vulnerabilities, and protect the safety, reliability, and continuity of physical operations. To achieve this goal, the organisation should: - Use StrongAuthentication: Remote systems should implement multi-factor authentication to ensure access is restricted to authorised personnel. - Maintain Activity Records: Detailed logs of all remote maintenance activities should be maintained and reviewed regularly to detect anomalies or unauthorised actions. - Align Tools and Procedures: All tools and procedures used during remote maintenance should align with organisational policies and be documented in the relevant cybersecurity or information security plans. - TerminateSessions: Remote sessions should be properlyterminated once maintenance is complete, to prevent lingering access. - Ensure Conformance and Compliance: Remote systems and activities should conform to internal security requirements 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 services are performed from sys- tems that implement securityfeatures equivalent to those of the organisation’s critical systems. In Operational Technology (OT) environments, this alignment is essential to maintain a consistent security posture, prevent the introduction of vulnerabilities, and protect the safety, reliability, and continuity of physical operations. To achieve this goal, the organisation should:</p><ul><li>Use StrongAuthentication: Remote systems should implement multi-factor authentication to ensure access is restricted to authorised personnel.</li><li>Maintain Activity Records: Detailed logs of all remote maintenance activities should be maintained and reviewed regularly to detect anomalies or unauthorised actions.</li><li>Align Tools and Procedures: All tools and procedures used during remote maintenance should align with organisational policies and be documented in the relevant cybersecurity or information security plans.</li><li>TerminateSessions: Remote sessions should be properlyterminated once maintenance is complete, to prevent lingering access.</li><li>Ensure Conformance and Compliance: Remote systems and activities should conform to internal security requirements and comply with applicable laws, regulations, and industry standards.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that remote maintenance and diagnostic services are performed from sys- tems that implement securityfeatures equivalent to those of the organisation’s critical systems. In Operational Technology (OT) environments, this alignment is essential to maintain a consistent security posture, prevent the introduction of vulnerabilities, and protect the safety, reliability, and continuity of physical operations. To achieve this goal, the organisation should: - Use StrongAuthentication: Remote systems should implement multi-factor authentication to ensure access is restricted to authorised personnel. - Maintain Activity Records: Detailed logs of all remote maintenance activities should be maintained and reviewed regularly to detect anomalies or unauthorised actions. - Align Tools and Procedures: All tools and procedures used during remote maintenance should align with organisational policies and be documented in the relevant cybersecurity or information security plans. - TerminateSessions: Remote sessions should be properlyterminated once maintenance is complete, to prevent lingering access. - Ensure Conformance and Compliance: Remote systems and activities should conform to internal security requirements and comply with applicable laws, regulations, and industry standards. |
|
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.13 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Remote maintenance system security equivalence |
|
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 require remote maintenance diagnostic services to be per- formed from a system that implements security features similar to the security features implemented on the equivalent organisation's critical system. |
|
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