Saltar al contenido

Episode 61 — A.8.15–8.16 — Logging; Monitoring activities

14 de octubre de 2025 · 13 min

Notas del episodio

A.8.15 requires that logging be planned, consistent, and comprehensive enough to reconstruct significant actions affecting information security. For the exam, connect logging scope to risk and classification: higher-value systems need richer telemetry—authentication results, admin actions, configuration changes, data access decisions, process creation, and network flows—captured with sufficient context to attribute events to identities, devices, and sessions. Logs must include time stamps, outcome codes, source/destination details, and object references, stored in tamper-evident repositories with defined retention aligned to legal and business needs. Candidates should emphasize secure collection (forwarding over protected channels), integrity controls (hashing, append-only storage), and privacy considerations (masking or minimizing personal data while preserving investigative value). The aim is not “log everything,” but to log the right things at the right fidelity so that incidents can be detected, triaged, and investigated without drowning in noise or exposing sensitive information unnecessarily.

A.8.16 extends this into active monitoring: the purposeful review and analysis of logs and signals to detect anomalies, policy violations, or attacks. Practical implementations combine rule-based detections, statistical baselines, and threat-informed use cases mapped to common techniques, with alerting tuned to minimize false positives. Evidence includes documented monitoring plans, use case catalogs tied to risks, dashboards, alert runbooks, and metrics such as mean time to detect and investigate. Pitfalls include uncorrelated silos (endpoint, identity, cloud, network) that hide lateral movement, or high-volume alerts without ownership or response procedures. Strong programs enrich events with identity and asset context, synchronize clocks, and maintain a defensible chain from alert to ticket to resolution, including periodic tuning driven by post-incident reviews. Candidates should be prepared to explain how logging and monitoring feed PDCA: plans define required signals, operations generate and protect them, reviews validate effectiveness, and improvements refine coverage and detections as the environment changes. 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.