SAST
Analyse source code, bytecode or binaries for security defects before the application is built or deployed.
- PL
- CO
- BU
- TE
- RE
- DE
- OP
- MO
A practical catalog of DevSecOps practices, tools, patterns, pipelines, security controls, and implementation examples.
Select a stage of the delivery lifecycle to see the practices that run there, the controls they enforce and the tools that implement them.
Threat modeling, requirements and security design decisions.
Apply language-level and framework-level practices that eliminate whole vulnerability classes.
Identify what can go wrong in a design before it is built, and record the mitigations chosen.
Design least-privilege access for humans and workloads with short-lived, auditable credentials.
Write policies and standards that are specific enough to be automated and verified.
Record, prioritise and periodically review security risks with named owners and decisions.
Analyse source code, bytecode or binaries for security defects before the application is built or deployed.
Probe a running application from the outside to find vulnerabilities that only appear at runtime.
Identify vulnerable, unmaintained or non-compliant third-party dependencies in your builds.
Find credentials, API keys and tokens committed to repositories, history, and CI configuration.
Scan container images for vulnerable packages and misconfiguration, and harden how images are built.
Analyse Terraform, Kubernetes manifests, Helm charts and CloudFormation for insecure configuration before apply.