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 automation in Jenkins

In this section, we will discuss how to configure Jenkins to trigger the automated testing, and also introduce some of the security plugins.

The following table shows an example of how to configure the command-line ZAP, which can be triggered periodically and remotely by a predefined URL:

Steps

Configuration steps

New item

New Item | Enter an Item Name | "Security Testing" | Freestyle Project | OK

General

Project Name: "Security Testing"

Build Trigger

The automation testing can be triggered by the schedule in the following ways. The Build Trigger defines how the tasks can be triggered. There are two modes supported: one is the scheduled mode and the other is the remote trigger by the REST API:

Build Periodically: 45 9-17/2 * * 1-5

The automation testing can also be triggered remotely...