Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying DevSecOps for Azure
  • Table Of Contents Toc
DevSecOps for Azure

DevSecOps for Azure

By : David Okeyode, Joylynn Kirui
4.8 (11)
close
close
DevSecOps for Azure

DevSecOps for Azure

4.8 (11)
By: David Okeyode, Joylynn Kirui

Overview of this book

Businesses must prioritize security, especially when working in the constantly evolving Azure cloud. However, many organizations struggle to maintain security and compliance. Attackers are increasingly targeting software development processes, making software supply chain security crucial. This includes source control systems, build systems, CI/CD platforms, and various artifacts. With the help of this book, you’ll be able to enhance security and compliance in Azure software development processes. Starting with an overview of DevOps and its relationship with Agile methodologies and cloud computing, you'll gain a solid foundation in DevSecOps principles. The book then delves into the security challenges specific to DevOps workflows and how to address them effectively. You'll learn how to implement security measures in the planning phase, including threat modeling and secure coding practices. You'll also explore pre-commit security controls, source control security, and the integration of various security tools in the build and test phases. The book covers crucial aspects of securing the release and deploy phases, focusing on artifact integrity, infrastructure as code security, and runtime protection. By the end of this book, you’ll have the knowledge and skills to implement a secure code-to-cloud process for the Azure cloud.
Table of Contents (14 chapters)
close
close
1
Part 1: Understanding DevOps and DevSecOps
4
Part 2: Securing the Plan and Code Phases of DevOps
8
Part 3: Securing the Build, Test, Release, and Operate Phases of DevOps

Addressing common coding security issues in source control

Securing our source control platform is crucial, but it is equally important to continuously test code for security and compliance within source control systems. This is necessary even if we already have pre-commit or IDE security integrations in place. The reason is simple: pre-commit code security measures can be bypassed; developers might disable git hooks or bypass checks by changing the configurations of static application security testing (SAST) or software composition analysis (SCA) tools. Security integrations in source control systems, however, provide more enforceable and reliable protection.

Also, scanning code in source control systems provides a wider coverage than IDE scans. It captures commits that might not be present in the developer’s workspace at pre-commit. This increases the chances of detecting vulnerabilities that have been missed in pre-commit scans. A third reason is that vulnerabilities are...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
DevSecOps for Azure
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon