
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.