Create your ISMS today
Start your free 14-day trial. Fill in your email to jump straight into the app. You can adjust any other settings later.
Complete your account setup later and connect e.g. to Teams, Google, or Slack.
Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
For the purpose of the notification under sub-article (1), the entities concerned shall submit to the CSIRT:
(a) without undue delay and in any event within twenty-four (24) hours of becoming aware of the incident, an early warning, which, where applicable, shall indicate whether the significant incident is suspected of being caused by unlawful or malicious acts or could have a cross-border impact;
(b) without undue delay and in any event within seventy-two (72) hours of becoming aware of the significant incident, an incident notification, which, where applicable, shall update the information referred to in paragraph (a) and indicate an initial assessment of the significant incident, including its severity and impact, as well as, where available, the indicators of compromise;
(c) upon request by a CSIRT, an interim report on relevant status updates;
(d) a final report no later than one (1) month after the submission of the incident notification under sub-article (5)(b) which shall include the following:
(e) in the event of an ongoing incident at the time of the submission of the final report referred to in paragraph (d), the entities concerned shall provide the CSIRT with a progress report at that time and a final report within one (1) month of their having handled the incident.
For the purpose of the notification under sub-article (1), the entities concerned shall submit to the CSIRT:
(a) without undue delay and in any event within twenty-four (24) hours of becoming aware of the incident, an early warning, which, where applicable, shall indicate whether the significant incident is suspected of being caused by unlawful or malicious acts or could have a cross-border impact;
(b) without undue delay and in any event within seventy-two (72) hours of becoming aware of the significant incident, an incident notification, which, where applicable, shall update the information referred to in paragraph (a) and indicate an initial assessment of the significant incident, including its severity and impact, as well as, where available, the indicators of compromise;
(c) upon request by a CSIRT, an interim report on relevant status updates;
(d) a final report no later than one (1) month after the submission of the incident notification under sub-article (5)(b) which shall include the following:
(e) in the event of an ongoing incident at the time of the submission of the final report referred to in paragraph (d), the entities concerned shall provide the CSIRT with a progress report at that time and a final report within one (1) month of their having handled the incident.
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.
In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.
When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.
Sets the overall compliance standard or regulation your organization needs to follow.
.svg)
.svg)
.svg)
Break down the framework into specific obligations that must be met.
.svg)
Concrete actions and activities your team carries out to satisfy each requirement.
Documented rules and practices that are created and maintained as a result of completing tasks.
