DevSecOps notes and differnce btween devops vs devdecops.pptx
trivedicropconnect
3 views
20 slides
Oct 17, 2025
Slide 1 of 20
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
About This Presentation
DevSecOps notes and difference between devops vs devdecops.pptx
Size: 685.61 KB
Language: en
Added: Oct 17, 2025
Slides: 20 pages
Slide Content
Continuous Delivery Continuous delivery is a practice where code changes are automatically prepared for a release to production
Continuous Delivery
Continuous Delivery
Continuous Delivery
Traditional Builds
Traditional Builds
Continuous Integration CI is a practice that helps to frequently integrate code changes into a central repository and then automate Builds
Continuous Integration
Production Grade DevSecOps Build Pipeline
Production Grade DevSecOps Build Pipeline Stage 1: Build & Unit Test Generate Artifacts Unit test Tools: Maven
Production Grade DevSecOps Build Pipeline Stage 2: Code Coverage How Many lines of code you tested? Unused code Tools: Jacoco
Production Grade DevSecOps Build Pipeline Stage 3: Software composition analysis Identify Vulnerabilities introduced by open-source or 3rd party libraries used in code Tools: OWASP Dependency-check
Production Grade DevSecOps Build Pipeline Stage 4: Static Application Security Testing Identify Vulnerabilities in proprietary code Insecure coding practice Tools: Sonarqube
Production Grade DevSecOps Build Pipeline Stage 5: Quality Gates Check if application meets the quality standards Tools: Sonarqube Quality profile
Production Grade DevSecOps Build Pipeline Stage 7: Scan Docker Image Identify Vulnerabilities in Image layers Tools: Trivy
Production Grade DevSecOps Build Pipeline Stage 8: Smoke Test Verify if the Image is built properly Determine if Image/Application is ready for testing Tools: Docker Container
Production Grade DevSecOps Build Pipeline Stage 8: Smoke Test Verify if the Image is built properly Determine if Image/Application is ready for testing Tools: Docker Container
Continuous Integration CI is a practice that helps to frequently integrate code changes into a central repository and then automate Builds