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)

Viewing the whole project

The top-down approach means we use the source code analysis tool to view programming flow diagrams, such as a class diagram, a call graph, or the dependency graph. The following table lists some recommended tools that will help you to analyze the source code more easily:

Tools

Description

Doxygen

It can generate documentation from the source code and also automatically visualize the relationships between modules, dependency graphs, and inheritance diagrams, by using the dot tool from Graphviz. Refer to the website at www.doxygen.org.

To be able to generate documents from the source code, it requires proper comments and tags in the source code. Here are some tips that may be worth reading. Bear in mind that the generation of documents by doxygen can take a long time. Don't tie the doxygen to parts of the compiler jobs. Check out the following...