DE.AE-3: Event data are collected and correlated from multiple sources and sensors.

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

The activity logging functionality of protection / detection hardware or software (e.g. firewalls, anti-virus)
shall be enabled, backed-up and reviewed.
Guidance
- Logs should be backed up and saved for a predefined period.
- The logs should be reviewed for any unusual or unwanted trends, such as a large use of social media
websites or an unusual number of viruses consistently found on a particular computer. These trends
may indicate a more serious problem or signal the need for stronger protections in a particular area.

The organization shall ensure that event data is compiled and correlated across its critical
systems using various sources such as event reports, audit monitoring, network monitoring,
physical access monitoring, and user/administrator reports.

The organization shall integrate analysis of events where feasible with the analysis of
vulnerability scanning information; performance data; its critical system's monitoring, and
facility monitoring to further enhance the ability to identify inappropriate or unusual
activity.

This requirement is part of the framework:  
CyberFundamentals (Belgium)
Best practices
How to implement:
DE.AE-3: Event data are collected and correlated from multiple sources and sensors.
This policy on
DE.AE-3: Event data are collected and correlated from multiple sources and sensors.
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

The activity logging functionality of protection / detection hardware or software (e.g. firewalls, anti-virus)
shall be enabled, backed-up and reviewed.
Guidance
- Logs should be backed up and saved for a predefined period.
- The logs should be reviewed for any unusual or unwanted trends, such as a large use of social media
websites or an unusual number of viruses consistently found on a particular computer. These trends
may indicate a more serious problem or signal the need for stronger protections in a particular area.

The organization shall ensure that event data is compiled and correlated across its critical
systems using various sources such as event reports, audit monitoring, network monitoring,
physical access monitoring, and user/administrator reports.

The organization shall integrate analysis of events where feasible with the analysis of
vulnerability scanning information; performance data; its critical system's monitoring, and
facility monitoring to further enhance the ability to identify inappropriate or unusual
activity.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
DE.AE-3: Event data are collected and correlated from multiple sources and sensors.
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
DE.AE-3: Event data are collected and correlated from multiple sources and sensors.
of the framework  
CyberFundamentals (Belgium)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Deployment and regular analysis of security system logs
Critical
High
Normal
Low
39
requirements
Technical cyber security
Security systems and logging

Deployment and regular analysis of security system logs

This task helps you comply with the following requirements

Identification and monitoring of event sources
Critical
High
Normal
Low

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.