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)

Security culture

The organization's culture may impact security practices and execution. The term culture may be quite vague, but generally speaking, there are two kinds of security culture. One is the strict process type, and the other is empowering the team. In the strict process, there is almost no room for flexibility. Once the expected security baselines are defined, they are all compulsory. Detailed security checklists are defined for every project to follow. No violation is allowed. On the other hand, the empowering the team type means the organization only defines general security guidelines, while project teams may define their own security checklists based on project needs.

A strict-process culture fits an environment that requires high-level controls, such as the military or banking. There are defined Standard Operating Procedures (SOPs) and checklists for every...