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. Does Microsoft SDL stand for Security Development Lifecycle?
  2. According to SDL, what activities should be done during the design stages?
    1. Establishing design requirements
    2. Performing attack surface analysis reduction
    3. User threat modeling
    4. All of the above
  1. In OWASP SAMM, what security practice is not part of security governance
    1. Security and metrics
    2. Education and guidance
    3. Secure architecture
    4. Policy and compliance
  2. In OWASP SAMM, which security practice is not part of security operations?
    1. Issue Management
    2. Security requirements
    3. Environment hardening
    4. Operational enablement
  3. What is not one of the characteristics of the security office under CTO?
    1. Large security team size—over 100 members
    2. No dedicated CSO
    3. The security team serves all projects
    4. The security team...