☁️
DevSecOps
  • DevSecOps
  • Case Study
  • The Big Picture
  • Checklist
  • 1. DevSecOps-The Big Picture
    • Understanding DevSecOps Concepts
      • DevSecOps Concept
      • DevSecOps Manifesto
      • What problem do DevSecOps solve?
      • Security as Code
      • CI/CD Pipeline Assurance
    • Identifying the Benefits of DevSecOps
      • Where is DevSecOps Appropriate?
      • Benefits of DevSecOps
      • Roles and Responsibilities
    • Designing DevSecOps for Plan, Code, and Build SDLC Phases
      • Threat Modeling - PLAN
      • Secure Code Standards
      • SAST and SCA - CODE
      • Vulnerability Scanning - BUILD
    • Designing DevSecOps for Test, Release, and Operate SDLC Phases
      • DevSecOps in the TEST Phase
      • DevSecOps in the DEPLOY Phase
      • DevSecOps in the OPERATE Phase
    • Common DevSecOps Myths
  • 2. Approaching Automated Security Testing in DevSecOps
    • Understanding Automated Security Testing
      • What Is Automated Security Testing?
      • Types of Security Testing
      • Manual vs. Automated Testing
    • Differentiating the Pros and Cons of Automated Security Testing
    • Understanding What and Where to Test during Automated Security Testing
    • Continuing
Powered by GitBook
On this page
  1. 1. DevSecOps-The Big Picture
  2. Designing DevSecOps for Plan, Code, and Build SDLC Phases

Vulnerability Scanning - BUILD

The next stage in CI/CD cycle is BUILD.

This is where the source code is taken and compiled into build code. At this point, it's good to look at vulnerability scanning against the build software.

Software Composition Analysis (SCA) - Checks Open Source components against known vulnerabilities

Dynamic Application Security Testing (DAST) - Vulnerability scanners run on completed (compiled) code

PreviousSAST and SCA - CODENextDesigning DevSecOps for Test, Release, and Operate SDLC Phases

Last updated 2 years ago