Book Image

Strategizing Continuous Delivery in the Cloud

By : Garima Bajpai, Thomas Schuetz
Book Image

Strategizing Continuous Delivery in the Cloud

By: Garima Bajpai, Thomas Schuetz

Overview of this book

Many organizations are embracing cloud technology to remain competitive, but implementing and adopting development processes while modernizing a cloud-based ecosystem can be challenging. Strategizing Continuous Delivery in Cloud helps you modernize continuous delivery and achieve infrastructure-application convergence in the cloud. You’ll learn the differences between cloud-based and traditional delivery approaches and develop a tailored strategy. You’ll discover how to secure your cloud delivery environment, ensure software security, run different test types, and test in the pre-production and production stages. You’ll also get to grips with the prerequisites for onboarding cloud-based continuous delivery for organizational and technical aspects. Then, you’ll explore key aspects of readiness to overcome core challenges in your cloud journey, including GitOps, progressive delivery controllers, feature flagging, differences between cloud-based and traditional tools, and implementing cloud chaos engineering. By the end of this book, you’ll be well-equipped to select the right cloud environment and technologies for CD and be able to explore techniques for implementing CD in the cloud.
Table of Contents (18 chapters)
1
Part 1: Foundation and Preparation for Continuous Delivery in the Cloud
6
Part 2: Implementing Continuous Delivery
11
Part 3: Best Practices and the Way Ahead

Security best practices

We discussed security-related topics in the previous chapter. In this section, we will add some more best practices that we have found useful when it comes to securing delivery processes.

Supply-c Levels for Software Artifacts (SLSA)

SLSA (pronounced salsa) is a security framework of best practices for ensuring the integrity of software artifacts throughout the entire software supply chain. It consists of incrementally adopted security guidelines for the software supply chain, offering a four-level hierarchy of maturity, where the fourth level is the desired end state:

  1. SLSA 1: Indicates adoption of fully scripted/automated build processes and generate provenance statements. They display evidence of how the artifact was built, including the build process and the dependencies.
  2. SLSA 2: Indicates adoption of version-controlled deliveries and a hosted build service that generates provenance.
  3. SLSA 3: Indicates adoption of source and that the...