Book Image

Hands-On Security in DevOps

By : Tony Hsiang-Chih Hsu
Book Image

Hands-On Security in DevOps

By: Tony Hsiang-Chih Hsu

Overview of this book

DevOps has provided speed and quality benefits with continuous development and deployment methods, but it does not guarantee the security of an entire organization. Hands-On Security in DevOps shows you how to adopt DevOps techniques to continuously improve your organization’s security at every level, rather than just focusing on protecting your infrastructure. This guide combines DevOps and security to help you to protect cloud services, and teaches you how to use techniques to integrate security directly in your product. You will learn how to implement security at every layer, such as for the web application, cloud infrastructure, communication, and the delivery pipeline layers. With the help of practical examples, you’ll explore the core security aspects, such as blocking attacks, fraud detection, cloud forensics, and incident response. In the concluding chapters, you will cover topics on extending DevOps security, such as risk assessment, threat modeling, and continuous security. By the end of this book, you will be well-versed in implementing security in all layers of your organization and be confident in monitoring and blocking attacks throughout your cloud services.
Table of Contents (23 chapters)

Threat modeling practices

Threat modeling is a security practice for the team to identify threats, attacks, and risks based on the existing architecture design, and also to mitigate these potential security risks. There are a few key points to clarify in threat modeling before we discuss them further:

  • It's a team activity. It's not just the developer's job. It will be more effective with QA, operation, architect, and security team involvement.
  • Threat modeling may be the only security practice that is not recommended to be done by automation. It's a team exercise.
  • The purpose of threat modeling is not to offer a comprehensive threat list, but to identify high-risk threats with key modules such as authentication, authorization, purchases, or customer info handling.
  • It's suggested to do threat modeling when the architecture design is done or before the detailed...