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. |
ID.IM-03.1: The organisation shall conduct post-incident evaluations to analyse lessons learned from incident response and recovery, and consequently improve processes / proce- dures / technologies to enhance its cyber resilience. |
|
ID.IM-03.1 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p74 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p54 |
|
|
http://cyfun.data.gift/data/loc_CyFun2025_Booklet_BASIC_E_p22 |
|
|
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 enhance cyber resilience by learning from incidents. After each incident, the organisation should analyse what happened, how it was handled, and what can be improved in processes, procedures, or technologies. To achieve this goal, the following should be considered: - Conduct Post-Incident Reviews A structured evaluation should be held after each incident, involving all relevant participants. - Reflect on Key Questions The review should explore: - What happened and why - How the response was managed - What worked well and what didn’t - What actions should be taken to prevent recurrence - Document Lessons Learned Findings from the review should be documented and shared with relevant teams. - Update Policies and Procedures Cybersecuritypolicies, processes, and procedures should be reviewed and updated regularly, at least annually, to reflect lessons learned. - Improve Tools and Capabilities Where applicable, technologies and response tools should be adapted or upgraded based on insights from the incident. |
|
A general note, for any purpose. |
<div><p>The goal of this control is to enhance cyber resilience by learning from incidents. After each incident, the organisation should analyse what happened, how it was handled, and what can be improved in processes, procedures, or technologies. To achieve this goal, the following should be considered:</p><ul><li>Conduct Post-Incident Reviews A structured evaluation should be held after each incident, involving all relevant participants.</li><li>Reflect on Key Questions The review should explore:<ul><li>What happened and why</li><li>How the response was managed</li><li>What worked well and what didn’t</li><li>What actions should be taken to prevent recurrence</li></ul></li><li>Document Lessons Learned Findings from the review should be documented and shared with relevant teams.</li><li>Update Policies and Procedures Cybersecuritypolicies, processes, and procedures should be reviewed and updated regularly, at least annually, to reflect lessons learned.</li><li>Improve Tools and Capabilities Where applicable, technologies and response tools should be adapted or upgraded based on insights from the incident.</li></ul></div> |
|
A general note, for any purpose. |
The goal of this control is to enhance cyber resilience by learning from incidents. After each incident, the organisation should analyse what happened, how it was handled, and what can be improved in processes, procedures, or technologies. To achieve this goal, the following should be considered: • Conduct Post-Incident Reviews A structured evaluation should be held after each incident, involving all relevant participants. • Reflect on Key Questions The review should explore: o What happened and why o How the response was managed o What worked well and what didn’t o What actions should be taken to prevent recurrence • Document Lessons Learned Findings from the review should be documented and shared with relevant teams. • Update Policies and Procedures Cybersecuritypolicies, processes, and procedures should be reviewed and updated regularly, at least annually, to reflect lessons learned. • Improve Tools and Capabilities Where applicable, technologies and response tools should be adapted or upgraded based on insights from the incident. |
|
A general note, for any purpose. |
The goal of this control is to enhance cyber resilience by learning from incidents. After each incident, the organisation should analyse what happened, how it was handled, and what can be improved in processes, procedures, or technologies. To achieve this goal, the following should be considered: - Conduct Post-Incident Reviews A structured evaluation should be held after each incident, involving all relevant participants. - Reflect on Key Questions The review should explore: - What happened and why - How the response was managed - What worked well and what didn’t - What actions should be taken to prevent recurrence - Document Lessons Learned Findings from the review should be documented and shared with relevant teams. - Update Policies and Procedures Cybersecuritypolicies, processes, and procedures should be reviewed and updated regularly, at least annually, to reflect lessons learned. - Improve Tools and Capabilities Where applicable, technologies and response tools should be adapted or upgraded based on insights from the incident. |
|
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. |
ID.IM-03.1 |
|
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. |
Post-incident lessons learned |
|
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 conduct post-incident evaluations to analyse lessons learned from incident response and recovery, and consequently improve processes / proce- dures / technologies to enhance its cyber resilience. |
|
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. |
|
|
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. |
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