Concept skos:Concept Code DE.AE-03.3

The organisation shall combine event analysis with information from vulnerability scans, system performance data, monitoring of critical systems, and facility moni- toring, where feasible.

Also known as

skos:altLabel

Event and vulnerability data correlation

Note

skos:note

The goal of this control is to strengthen the organisation’s ability to detect complex or hidden threats by com- bining event analysis with other relevant data sources. This broader view supports more accurate and timely identification of suspicious activity, and the following should be considered to achieve the goal of this control:

  • Tools that collect and link data from different systems (such as SIEM, XDR, or SOAR) should be used to support this integration.
  • Security issues reported by suppliers or trusted sources should be collected quickly and reviewed for possible risks.
  • Data from different monitoring systems should be brought together to make it easier to detect patterns or problems.
  • The setup should allow fast detection and response when something unusual is found.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_DE_AE_03_3
All data (19 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

http://cyfun.data.gift/ontology#Requirement

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

A human-readable name for the subject.

DE.AE-03.3: The organisation shall combine event analysis with information from vulnerability scans, system performance data, monitoring of critical systems, and facility moni- toring, where feasible.

http://cyfun.data.gift/ontology#requirementId

DE.AE-03.3

http://cyfun.data.gift/ontology#foundIn

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p158

has broader

Relates a concept to a concept that is more general in meaning.

http://cyfun.data.gift/data/subcategory_DE.AE-03

note

A general note, for any purpose.

<div><p>The goal of this control is to strengthen the organisation’s ability to detect complex or hidden threats by com- bining event analysis with other relevant data sources. This broader view supports more accurate and timely identification of suspicious activity, and the following should be considered to achieve the goal of this control:</p><ul><li>Tools that collect and link data from different systems (such as SIEM, XDR, or SOAR) should be used to support this integration.</li><li>Security issues reported by suppliers or trusted sources should be collected quickly and reviewed for possible risks.</li><li>Data from different monitoring systems should be brought together to make it easier to detect patterns or problems.</li><li>The setup should allow fast detection and response when something unusual is found.</li></ul></div>

note

A general note, for any purpose.

The goal of this control is to strengthen the organisation’s ability to detect complex or hidden threats by com- bining event analysis with other relevant data sources. This broader view supports more accurate and timely identification of suspicious activity, and the following should be considered to achieve the goal of this control: • Tools that collect and link data from different systems (such as SIEM, XDR, or SOAR) should be used to support this integration. • Security issues reported by suppliers or trusted sources should be collected quickly and reviewed for possible risks. • Data from different monitoring systems should be brought together to make it easier to detect patterns or problems. • The setup should allow fast detection and response when something unusual is found.

note

A general note, for any purpose.

The goal of this control is to strengthen the organisation’s ability to detect complex or hidden threats by com- bining event analysis with other relevant data sources. This broader view supports more accurate and timely identification of suspicious activity, and the following should be considered to achieve the goal of this control: - Tools that collect and link data from different systems (such as SIEM, XDR, or SOAR) should be used to support this integration. - Security issues reported by suppliers or trusted sources should be collected quickly and reviewed for possible risks. - Data from different monitoring systems should be brought together to make it easier to detect patterns or problems. - The setup should allow fast detection and response when something unusual is found.

note

A general note, for any purpose.

The goal of this control is to strengthen the organisation’s ability to detect complex or hidden threats by com- bining event analysis with other relevant data sources. This broader view supports more accurate and timely identification of suspicious activity, and the following should be considered to achieve the goal of this control: - Tools that collect and link data from different systems (such as SIEM, XDR, or SOAR) should be used to support this integration. - Security issues reported by suppliers or trusted sources should be collected quickly and reviewed for possible risks. - Data from different monitoring systems should be brought together to make it easier to detect patterns or problems. - The setup should allow fast detection and response when something unusual is found.

notation

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-03.3

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

Event and vulnerability data correlation

preferred label

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 combine event analysis with information from vulnerability scans, system performance data, monitoring of critical systems, and facility moni- toring, where feasible.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025

is in scheme

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

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

http://cyfun.data.gift/ontology#level

http://cyfun.data.gift/data/level_ESSENTIAL

triple count

The number of triples associated with the subject.

17

in dataset

Specifies the dataset the subject is part of.

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

Resultaten 1 - 19 of 19

References

Inverse links to the subject.