Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing DevSecOps Practices

You're reading from   Implementing DevSecOps Practices Understand application security testing and secure coding by integrating SAST and DAST

Arrow left icon
Product type Paperback
Published in Dec 2023
Publisher Packt
ISBN-13 9781803231495
Length 258 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Vandana Verma Sehgal Vandana Verma Sehgal
Author Profile Icon Vandana Verma Sehgal
Vandana Verma Sehgal
Arrow right icon
View More author details
Toc

Table of Contents (25) Chapters Close

Preface 1. Part 1:DevSecOps – What and How?
2. Chapter 1: Introducing DevSecOps FREE CHAPTER 3. Part 2: DevSecOps Principles and Processes
4. Chapter 2: DevSecOps Principles 5. Chapter 3: Understanding the Security Posture 6. Chapter 4: Understanding Observability 7. Chapter 5: Understanding Chaos Engineering 8. Part 3:Technology
9. Chapter 6: Continuous Integration and Continuous Deployment 10. Chapter 7: Threat Modeling 11. Chapter 8: Software Composition Analysis (SCA) 12. Chapter 9: Static Application Security Testing (SAST) 13. Chapter 10: Infrastructure-as-Code (IaC) Scanning 14. Chapter 11: Dynamic Application Security Testing (DAST) 15. Part 4: Tools
16. Chapter 12: Setting Up a DevSecOps Program with Open Source Tools 17. Part 5: Governance and an Effective Security Champions Program
18. Chapter 13: License Compliance, Code Coverage, and Baseline Policies 19. Chapter 14: Setting Up a Security Champions Program 20. Part 6: Case Studies and Conclusion
21. Chapter 15: Case Studies 22. Chapter 16: Conclusion 23. Index 24. Other Books You May Enjoy

Continuous Integration and Continuous Deployment

CI/CD stands for continuous integration/continuous deployment/delivery. While CI automatically releases every change to production, CD ensures changes are production-ready but may require a manual step for deployment. It is a software development practice that involves frequently integrating code changes into a central repository and then automatically building and deploying those changes to a test or production environment.

CI is the practice of regularly merging code changes into a shared repository, where automated tests are run to catch any issues that may have been introduced.

CD is the practice of automatically deploying code changes that pass all tests to a production environment. A CI/CD pipeline automates the process of testing, building, and deploying software changes; it helps catch and fix errors early, reduces the risk of introducing bugs, and improves the overall software quality.

We will cover the following topics...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image