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. |
RS.MI-01.2: The organisation shall detect unauthorised access or data leakage and take appropriate mitigation actions, including monitoring of critical systems at external boundaries and key internal points. |
|
RS.MI-01.2 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p174 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p116 |
|
|
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 detect unauthorised access and data leakage in a timely manner and to take appropriate mitigation actions. This should help protect the confidentiality, integrity, availability, and safety of data, whether it is stored, being transmitted, or actively used, across both Information Technology (IT) and Operational Technology (OT) environments. To achieve this goal, the organisation should: - Monitor Critical Systems Monitoring should be implemented at external network boundaries and key internal points to detect anomalies or unauthorised access attempts. - Protect Data in All States Data should be protected using encryption, digital signatures, and cryptographic hashes to ensure confi- dentiality and integrity during storage, transmission, and use. - Control Outgoing Communications Outbound communications containing sensitive data should be automatically blocked or encrypted based on data classification. - Restrict Use of Personal Services Access to personal communication platforms (e.g. personal email, file-sharing services) from organisational systems should be restricted to reduce the risk of data leakage. - Prevent Data Reuse in Non-Production Environments Sensitive production data should not be reused in development or testing environments unless properly anonymised or masked. - Clear Temporary Data Sensitive data should be cleared from memory or temporary storage once it is no longer needed. - Audit Identity and Access Management Systems such as MicrosoftActive Directory should be regularly audited, with a focus on privileged accounts and access control consistency. - Ensure OT-Specific Feasibility In OT environments, detection and mitigation measures should be adapted to avoid disrupting safety or operational continuity. Passive monitoring and interface-level logging may be used where direct integration is not feasible. - Align with ENISA Guidance These practices align with ENISA’s Threat Landscape Reports and Information Leakage Guidance, which provide recommendations for detecting and mitigating data breaches and unauthorised access. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to detect unauthorised access and data leakage in a timely manner and to take appropriate mitigation actions. This should help protect the confidentiality, integrity, availability, and safety of data, whether it is stored, being transmitted, or actively used, across both Information Technology (IT) and Operational Technology (OT) environments. To achieve this goal, the organisation should:</p><ul><li>Monitor Critical Systems Monitoring should be implemented at external network boundaries and key internal points to detect anomalies or unauthorised access attempts.</li><li>Protect Data in All States Data should be protected using encryption, digital signatures, and cryptographic hashes to ensure confi- dentiality and integrity during storage, transmission, and use.</li><li>Control Outgoing Communications Outbound communications containing sensitive data should be automatically blocked or encrypted based on data classification.</li><li>Restrict Use of Personal Services Access to personal communication platforms (e.g. personal email, file-sharing services) from organisational systems should be restricted to reduce the risk of data leakage.</li><li>Prevent Data Reuse in Non-Production Environments Sensitive production data should not be reused in development or testing environments unless properly anonymised or masked.</li><li>Clear Temporary Data Sensitive data should be cleared from memory or temporary storage once it is no longer needed.</li><li>Audit Identity and Access Management Systems such as MicrosoftActive Directory should be regularly audited, with a focus on privileged accounts and access control consistency.</li><li>Ensure OT-Specific Feasibility In OT environments, detection and mitigation measures should be adapted to avoid disrupting safety or operational continuity. Passive monitoring and interface-level logging may be used where direct integration is not feasible.</li><li>Align with ENISA Guidance These practices align with ENISA’s Threat Landscape Reports and Information Leakage Guidance, which provide recommendations for detecting and mitigating data breaches and unauthorised access.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to detect unauthorised access and data leakage in a timely manner and to take appropriate mitigation actions. This should help protect the confidentiality, integrity, availability, and safety of data, whether it is stored, being transmitted, or actively used, across both Information Technology (IT) and Operational Technology (OT) environments. To achieve this goal, the organisation should: • Monitor Critical Systems Monitoring should be implemented at external network boundaries and key internal points to detect anomalies or unauthorised access attempts. • Protect Data in All States Data should be protected using encryption, digital signatures, and cryptographic hashes to ensure confi- dentiality and integrity during storage, transmission, and use. • Control Outgoing Communications Outbound communications containing sensitive data should be automatically blocked or encrypted based on data classification. • Restrict Use of Personal Services Access to personal communication platforms (e.g. personal email, file-sharing services) from organisational systems should be restricted to reduce the risk of data leakage. • Prevent Data Reuse in Non-Production Environments Sensitive production data should not be reused in development or testing environments unless properly anonymised or masked. • Clear Temporary Data Sensitive data should be cleared from memory or temporary storage once it is no longer needed. • Audit Identity and Access Management Systems such as MicrosoftActive Directory should be regularly audited, with a focus on privileged accounts and access control consistency. • Ensure OT-Specific Feasibility In OT environments, detection and mitigation measures should be adapted to avoid disrupting safety or operational continuity. Passive monitoring and interface-level logging may be used where direct integration is not feasible. • Align with ENISA Guidance These practices align with ENISA’s Threat Landscape Reports and Information Leakage Guidance, which provide recommendations for detecting and mitigating data breaches and unauthorised access. |
|
A general note, for any purpose. |
The goal of this control is to detect unauthorised access and data leakage in a timely manner and to take appropriate mitigation actions. This should help protect the confidentiality, integrity, availability, and safety of data, whether it is stored, being transmitted, or actively used, across both Information Technology (IT) and Operational Technology (OT) environments. To achieve this goal, the organisation should: - Monitor Critical Systems Monitoring should be implemented at external network boundaries and key internal points to detect anomalies or unauthorised access attempts. - Protect Data in All States Data should be protected using encryption, digital signatures, and cryptographic hashes to ensure confi- dentiality and integrity during storage, transmission, and use. - Control Outgoing Communications Outbound communications containing sensitive data should be automatically blocked or encrypted based on data classification. - Restrict Use of Personal Services Access to personal communication platforms (e.g. personal email, file-sharing services) from organisational systems should be restricted to reduce the risk of data leakage. - Prevent Data Reuse in Non-Production Environments Sensitive production data should not be reused in development or testing environments unless properly anonymised or masked. - Clear Temporary Data Sensitive data should be cleared from memory or temporary storage once it is no longer needed. - Audit Identity and Access Management Systems such as MicrosoftActive Directory should be regularly audited, with a focus on privileged accounts and access control consistency. - Ensure OT-Specific Feasibility In OT environments, detection and mitigation measures should be adapted to avoid disrupting safety or operational continuity. Passive monitoring and interface-level logging may be used where direct integration is not feasible. - Align with ENISA Guidance These practices align with ENISA’s Threat Landscape Reports and Information Leakage Guidance, which provide recommendations for detecting and mitigating data breaches and unauthorised access. |
|
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. |
RS.MI-01.2 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Unauthorised access and data leakage mitigation |
|
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 detect unauthorised access or data leakage and take appropriate mitigation actions, including monitoring of critical systems at external boundaries and key internal points. |
|
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. |
|
|
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. |
|
|
1 |
|
|
The number of triples associated with the subject. |
21 |
|
Specifies the dataset the subject is part of. |
Resultaten 1 - 23 of 23
Inverse links to the subject.
| Property | Subject |
|---|---|
|
Relates a concept to a concept that is more specific in meaning. |
Resultaten 1 - 1 of 1