Episode 62 — A.8.17–8.18 — Clock synchronization; Privileged utility programs

Episode 62 — A.8.17–8.18 — Clock synchronization; Privileged utility programs

A.8.17 mandates synchronized time across systems so that events recorded in different places can be reliably correlated. For the exam, stress why this matters: investigations, non-repudiation, and regulatory reporting all depend on consistent, traceable timestamps. Organizations typically standardize on secure time sources (e.g., authenticated NTP or cloud time services), designate stratum hierarchies, protect time infrastructure from spoofing, and monitor drift with thresholds that trigger correction. Time settings must align to logging and monitoring strategies, with clear documentation of time zones, daylight-savings handling, and retention of configuration changes. Candidates should highlight how unsynchronized clocks undermine evidence chains, create false sequences in incident timelines, and complicate SLA verification; therefore, clock control is not an afterthought but a foundational integrity requirement for the whole telemetry fabric.

A.8.18 covers privileged utility programs—powerful tools like debuggers, packet sniffers, firmware flashers, database consoles, and hypervisor or cloud administrative utilities that can bypass normal controls. The control expects tight governance: inventory and classification of such utilities, restricted installation and execution, approved use cases, and monitoring of invocation with full command and parameter capture where feasible. Technical enforcement may include application allow-listing, PAM-mediated launch, sandboxed consoles, and dedicated privileged workstations. Pitfalls include leaving diagnostic tools on production hosts, unmanaged portable binaries, and “break-glass” accounts with access to everything but no session recording. Strong programs pair least privilege with just-in-time elevation, segregate admin networks, and require change or incident tickets to justify use, with post-use reviews to ensure necessity and proportionality. Candidates should connect time integrity and privileged utility control to defensible investigations: you cannot trust what you cannot sequence, and you cannot attest to control effectiveness if high-power tools operate outside auditable pathways. 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