Saltar al contenido

Episode 36 — A.5.27–5.28 — Learning from incidents; Collection of evidence

14 de octubre de 2025 · 13 min

Notas del episodio

A.5.27 requires organizations to institutionalize learning from incidents, transforming individual events into durable improvements. For the exam, emphasize that “learning” goes beyond a retrospective; it means capturing root causes, systemic contributors, and control gaps, then updating policies, baselines, training, and detection logic. The objective is to reduce recurrence probability and impact, while improving detection fidelity and response speed. A.5.28 complements this by mandating proper collection of evidence during events, ensuring that data relevant to investigations and potential legal action is identified, preserved, and protected against tampering. Candidates should connect these controls to governance: defined ownership for lessons learned, prioritized remediation backlogs, and chain-of-custody practices that maintain evidentiary weight.

In practice, mature programs run blameless post-incident reviews that produce actionable findings, measurable tasks, and deadlines tied to risk. Playbooks include evidence preservation steps—log snapshotting, memory captures, disk imaging, and cloud artifact exports—selected according to system type and legal requirements. Tools and processes must ensure integrity with hashing, time synchronization, secure storage, and access controls; documentation should include who collected what, when, from where, and how. Common pitfalls include ad hoc note-taking, overwritten logs due to short retention, and fixes implemented without verifying that detections also improved. Effective teams track remediation completion, regression test outcomes, and the percentage of incidents that resulted in controls, training, or architecture changes. Candidates should be ready to explain how these controls intersect with privacy, HR, and legal teams; how evidence handling supports external investigations or litigation; and how continuous feedback closes the PDCA loop by converting incident pain into long-term organizational learning. Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.

Todos los episodios de Framework – ISO 27001 (Cyber)

Ajustes

Visualización

Idioma

Determina qué emisoras ves primero en la página de inicio.

Historial

Las emisoras y episodios escuchados recientemente y tus últimas búsquedas solo se guardan en este navegador.

Avisos

Un breve aviso cuando un pódcast que sigues tiene un episodio nuevo. Puedes desactivar pódcast concretos con la campana de su página.

Cuenta

Guarda tus favoritos: en la app y en la web.

Atajos de teclado

/
Abrir búsqueda
Espacio
Reproducir o pausar
← →
En el reproductor: 15 s atrás, 30 s adelante (episodios) · en una fila: siguiente tarjeta
↑ ↓
En una fila: destino dentro de la tarjeta
Inicio / Fin
En una fila: primera o última tarjeta
Esc
Cerrar ventana o menú
?
Este resumen
Reproduciendo ahora

Ir a la emisora

A continuación

    Añade episodios con «A continuación»: sonarán después del episodio actual.