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: unit and integration tests that encode security invariants; SAST for code weaknesses; DAST and IAST for runtime behavior; software composition analysis for dependencies; fuzzing and negative testing for robustness; and targeted penetration testing to validate exploitability and compensating controls. Acceptance must include verification of logging, alerting, and recovery paths—not only functional success. The control expects test plans, coverage criteria, environmental parity, and defect lifecycles with severity-driven SLAs. Candidates should note evidence expectations: reproducible results, traceability from risk to test case, and sign-off records that justify release decisions.

A.8.30 addresses outsourced development, recognizing unique risks in third-party or staff-augmented engineering. Security requirements must flow down contractually: background screening, secure coding standards, toolchain controls, IP ownership, confidentiality, vulnerability disclosure, and rights to assess or audit. Access should be least-privilege, time-bound, and brokered through managed repositories and build systems; secrets must never be shared outside approved vaulting. Pitfalls include broad repository access, unmanaged contractor devices, and opaque subcontracting chains that dilute accountability. Effective programs standardize secure workspaces (VDI or managed dev environments), require signed commits and protected branches, and integrate vendor work into the same CI/CD gates and SAST/SCA policies used internally. Candidates should connect outsourced development to supply-chain assurance and incident readiness, explaining how contracts, onboarding checklists, and technical guardrails combine to make third-party contributions verifiable, revocable, and resilient against compromise. 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 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
rss-strid-de-norske-borgerkrigene
sinnsyn
tomprat-med-gunnar-tjomlid
hverdagspsyken
gravid-uke-for-uke
rss-bisarr-historie
hagespiren-podcast
rss-mind-body-podden
level-up-med-anniken-binz
fryktlos