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

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

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.

Denne episoden er hentet fra en åpen RSS-feed og er ikke publisert av Podme. Den kan derfor inneholde annonser.

Episoder(71)

Welcome to Framework - ISO 27001

Welcome to Framework - ISO 27001

Dive into a fast, no-fluff overview of what this podcast delivers, who it’s for, and how each episode helps you level up with practical, real-world takeaways. In this trailer, you’ll hear the show’s p...

14 Okt 20251min

Episode 70 — A.8.33–8.34 — Test information; Protecting systems during audit testing

Episode 70 — A.8.33–8.34 — Test information; Protecting systems during audit testing

A.8.33 governs test information—data and artifacts used to verify functionality and security—so that confidentiality, integrity, and legality are preserved. For the exam, distinguish data sources and ...

14 Okt 202513min

Episode 69 — A.8.31–8.32 — Separation of dev/test/prod; Change management

Episode 69 — A.8.31–8.32 — Separation of dev/test/prod; Change management

A.8.31 enforces separation between development, test, and production to prevent inadvertent changes, data leakage, and unauthorized access. For the exam, stress environment isolation, distinct identit...

14 Okt 202511min

Episode 68 — A.8.29–8.30 — Security testing in development & acceptance; Outsourced development

Episode 68 — A.8.29–8.30 — Security testing in development & acceptance; Outsourced development

A.8.29 requires structured security testing throughout development and acceptance, proving that controls operate as intended before release. For the exam, differentiate testing modalities and purposes...

14 Okt 202513min

Episode 67 — A.8.27–8.28 — Secure system architecture & engineering; Secure coding

Episode 67 — A.8.27–8.28 — Secure system architecture & engineering; Secure coding

A.8.27 focuses on secure system architecture and engineering, requiring designs that partition trust, minimize attack surface, and enforce least privilege at every layer. For the exam, emphasize archi...

14 Okt 202514min

Episode 66 — A.8.25–8.26 — Secure development lifecycle; Application security requirements

Episode 66 — A.8.25–8.26 — Secure development lifecycle; Application security requirements

A.8.25 requires a secure development lifecycle (SDLC) that embeds security from concept to retirement, not as a late-stage gate. For the exam, describe SDLC phases with explicit security tasks: threat...

14 Okt 202514min

Episode 65 — A.8.23–8.24 — Web filtering; Use of cryptography

Episode 65 — A.8.23–8.24 — Web filtering; Use of cryptography

A.8.23 establishes web filtering to manage risk from browsing and outbound HTTP/S traffic, acknowledging that the browser is a primary threat vector. For the exam, emphasize policy-aligned controls th...

14 Okt 202515min

Episode 64 — A.8.21–8.22 — Security of network services; Segregation of networks

Episode 64 — A.8.21–8.22 — Security of network services; Segregation of networks

A.8.21 requires that network services—whether internal or provided by third parties—be specified and secured to meet business and security requirements. For the exam, think beyond raw connectivity: se...

14 Okt 202513min

Populært innen Fakta

fastlegen
dine-penger-pengeradet
relasjonspodden-med-dora-thorhallsdottir-kjersti-idem
foreldreradet
treningspodden
jakt-og-fiskepodden
rss-kunsten-a-leve
rss-kull
takk-og-lov-med-anine-kierulf
mikkels-paskenotter
sinnsyn
rss-strid-de-norske-borgerkrigene
tomprat-med-gunnar-tjomlid
hverdagspsyken
gravid-uke-for-uke
rss-sarbar-med-lotte-erik
hagespiren-podcast
smart-forklart
fryktlos
rss-bisarr-historie