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. |
DE.AE-02.1: Cybersecurity and information security events shall be reviewed and analysed to identify potential attack targets and methods, in accordance with applicable laws, regulations, standards, and policies. |
|
DE.AE-02.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p155 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p103 |
|
|
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 cybersecurity and information security events are reviewed and analysed to detect attack targets and methods. This enables organisations to respond effectively to threats while maintaining compliance with legal, regulatory, and policy requirements. To achieve this goal, consider the following: - Organisations should follow relevant federal and regional laws, industry regulations, standards, and internal policies when reviewing security events. - Log analysis tools should be used to generate reports and identify suspicious activity. - System and application logs should be regularlyreviewed to detect signs ofsecuritythreats, such as repeated failed login attempts or unusual data transfers. - Logs should be analysed for patterns that indicate attempted or ongoing attacks. - Threat intelligence should be used to stay informed about emerging threats and attack techniques, and security measures should be adjusted accordingly. - Regular audits and assessments should be conducted to evaluate the organisation’s security posture. - The results of these audits should be used to improve monitoring and analysis processes. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to ensure that cybersecurity and information security events are reviewed and analysed to detect attack targets and methods. This enables organisations to respond effectively to threats while maintaining compliance with legal, regulatory, and policy requirements. To achieve this goal, consider the following:</p><ul><li>Organisations should follow relevant federal and regional laws, industry regulations, standards, and internal policies when reviewing security events.</li><li>Log analysis tools should be used to generate reports and identify suspicious activity.</li><li>System and application logs should be regularlyreviewed to detect signs ofsecuritythreats, such as repeated failed login attempts or unusual data transfers.</li><li>Logs should be analysed for patterns that indicate attempted or ongoing attacks.</li><li>Threat intelligence should be used to stay informed about emerging threats and attack techniques, and security measures should be adjusted accordingly.</li><li>Regular audits and assessments should be conducted to evaluate the organisation’s security posture.</li><li>The results of these audits should be used to improve monitoring and analysis processes.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to ensure that cybersecurity and information security events are reviewed and analysed to detect attack targets and methods. This enables organisations to respond effectively to threats while maintaining compliance with legal, regulatory, and policy requirements. To achieve this goal, consider the following: • Organisations should follow relevant federal and regional laws, industry regulations, standards, and internal policies when reviewing security events. • Log analysis tools should be used to generate reports and identify suspicious activity. • System and application logs should be regularlyreviewed to detect signs ofsecuritythreats, such as repeated failed login attempts or unusual data transfers. • Logs should be analysed for patterns that indicate attempted or ongoing attacks. • Threat intelligence should be used to stay informed about emerging threats and attack techniques, and security measures should be adjusted accordingly. • Regular audits and assessments should be conducted to evaluate the organisation’s security posture. • The results of these audits should be used to improve monitoring and analysis processes. |
|
A general note, for any purpose. |
The goal of this control is to ensure that cybersecurity and information security events are reviewed and analysed to detect attack targets and methods. This enables organisations to respond effectively to threats while maintaining compliance with legal, regulatory, and policy requirements. To achieve this goal, consider the following: - Organisations should follow relevant federal and regional laws, industry regulations, standards, and internal policies when reviewing security events. - Log analysis tools should be used to generate reports and identify suspicious activity. - System and application logs should be regularlyreviewed to detect signs ofsecuritythreats, such as repeated failed login attempts or unusual data transfers. - Logs should be analysed for patterns that indicate attempted or ongoing attacks. - Threat intelligence should be used to stay informed about emerging threats and attack techniques, and security measures should be adjusted accordingly. - Regular audits and assessments should be conducted to evaluate the organisation’s security posture. - The results of these audits should be used to improve monitoring and analysis processes. |
|
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. |
DE.AE-02.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Security event analysis |
|
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. |
Cybersecurity and information security events shall be reviewed and analysed to identify potential attack targets and methods, in accordance with applicable laws, regulations, standards, and policies. |
|
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