Delivery Fundamentals for DevSecOpss
Delivery fundamentals are the engineering base DevSecOps builds on: CI/CD pipelines and Git workflows that take code to production, plus containers and Linux hardening such as least-privilege users, minimal images and restricted capabilities. Security controls are added to these existing steps, so you need to understand them first.
Stage: Foundations · Part of the DevSecOps roadmap · Last reviewed 19 November 2026
What to learn in Delivery Fundamentals
- Describe the stages of a CI/CD pipeline from commit to deploy
- Use branch protection and pull request reviews in Git
- Build a container image and run it as a non-root user
- Drop Linux capabilities and use read-only filesystems for containers
- Harden SSH and user permissions on a Linux host
- Explain where each security check fits in a pipeline
Delivery Fundamentals interview questions
Why should containers not run as root?
If an attacker escapes the application, a root process inside the container has more power on the host, especially with misconfigured mounts or capabilities. A non-root user limits the damage and is required by many cluster policies.
Where should security scans run in a pipeline?
Run fast checks such as secrets and linting on every commit, SAST and dependency scans on pull requests, image scans after the build and DAST against a staging deployment. Early and quick checks give developers fast feedback without slowing delivery.
Where Delivery Fundamentals fits in the DevSecOps roadmap
Delivery Fundamentals belongs to the Foundations stage (beginner level), which takes about 6 hours. Security and delivery fundamentals.
Other units in this stage
Back to the full DevSecOps roadmap