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)

Questions

  1. What security assessment may apply to a new or major application release?
    1. Full assessment
    2. Assessment based on the patch scope
    3. Assessment based on the third party and the integration interfaces
    4. The security testing scope is limited to ensure no major security issues
  2. Which of the following is not one of the self-assessment activities that should be done by the product development team?
    1. Review the OWASP ASVS checklist
    2. Security awareness training program
    3. Execute defined automated security tools, such as ZAP, NMAP, and SQLmap
    4. Fix major security issues
  3. Which of the following is not the security testing approach for checking hidden communication interfaces?
    1. Listening to 0.0.0.0 is forbidden
    2. Searching for hidden hard-coded secrets, password, or hard key
    3. Searching for personal information
    4. Unnecessary system maintenance tools
  4. Which of the following communication protocols...