Secure Software Delivery: DevSecOps, Pipeline, and Supply Chain Security Questions
Embedding security into how software is built, assembled from dependencies, and shipped. Covers shift-left and secure-SDLC practices, infrastructure-as-code security, CI/CD pipeline and secrets management, integrating security scanning into build and deploy, and configuration and secret management across environments, together with software supply chain security: software composition analysis (SCA), dependency and open-source vulnerability management, build-provenance and artifact integrity, and mitigating supply-chain attack vectors. The 'secure the delivery pipeline and everything it pulls in' discipline, distinct from vendor-risk governance.
You receive a large SCA report showing hundreds of transitive vulnerabilities across dependencies used by a monolith and multiple microservices. Describe a practical triage and remediation plan: how you would prioritize which findings actually get fixed first, how to schedule the work, what you'd automate, and how remediation in the monolith differs from remediation across the microservices.
Explain 'policy-as-code' in the CI/CD context. Provide a simple example rule (textual) that would prevent merges if a commit contains high-severity SCA findings or secrets, and name two tools that can enforce such rules in pipelines.
Describe supply chain attacks against software: how attackers compromise dependencies, CI/CD pipelines, or vendor updates. Provide two historical examples, indicators of compromise to hunt for, and three proactive controls you would implement across procurement and engineering to reduce risk.
As a Security Architect building an enterprise secure-SDLC blueprint, enumerate the attack vectors you consider the most common ways a CI/CD pipeline actually gets compromised in practice, and propose at least one practical mitigation for each vector you name.
Compare SAST, DAST, and SCA: for each type describe what artifacts it analyzes, at what stage(s) of the SDLC it is most effective, typical false-positive and false-negative trade-offs, and one practical example tool you would run in a CI pipeline. Also explain where each should be run (pre-merge, post-merge, nightly, or runtime) to optimize developer velocity and security coverage.
Unlock Full Question Bank
Get access to all 35 Secure Software Delivery: DevSecOps, Pipeline, and Supply Chain Security interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.