Hands-On Security in DevOps

Ensure continuous security, deployment, and delivery with DevSecOps

Tony Hsu

• Editorial: Packt Publishing
• Año: 2018
• ISBN:
  9781788992411
• Edición: 1
• Categoría: Informatica
• Categoría: Sicurezza informatica

Protect your organization's security at all levels by introducing the latest strategies for securing DevOps

Key Features

• Integrate security at each layer of the DevOps pipeline
• Discover security practices to protect your cloud services by detecting fraud and intrusion
• Explore solutions to infrastructure security using DevOps principles

Book Description

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.

What you will learn

• Understand DevSecOps culture and organization
• Learn security requirements, management, and metrics
• Secure your architecture design by looking at threat modeling, coding tools and practices
• Handle most common security issues and explore black and white-box testing tools and practices
• Work with security monitoring toolkits and online fraud detection rules
• Explore GDPR and PII handling case studies to understand the DevSecOps lifecycle

Who this book is for

Hands-On Security in DevOps is for system administrators, security consultants, and DevOps engineers who want to secure their entire organization. Basic understanding of Cloud computing, automation frameworks, and programming is necessary.

DevSecOps - Challenges, Tips, and FAQs

The adoption of DevSecOps is a continuous learning process and takes a lot of stakeholder involvement, process optimization, business priority conflicts, and customization of security tools, as well as a security knowledge learning curve. The intention of this chapter is to give you some hands-on tips, challenges, and FAQs based on a functional roles perspective.

We will cover the following topics in this chapter:

• DevSecOps FAQs for security management
• DevSecOps FAQs for the development team
• DevSecOps FAQs for the testing team
• DevSecOps FAQs for the operations team

DevSecOps for security management

Q: Are there any suggested industry best practices for secure development and deployment in DevOps?

The OWASP SAMM (Software Assurance Maturity Model), Microsoft Security Development Lifecycle (SDL) and the SafeCode provide practical security practices for the DevOps or agile development.

• OWASP SAMM: https://github.com/OWASP/samm
• Microsoft SDL for Agile: https://www.microsoft.com/en-us/SDL/Discover/sdlagile.aspx
• SafeCode: https://safecode.org/publications/

Q: What are the security risks of a cloud service?

The CSA has defined the top threats to cloud computing on their website (https://cloudsecurityalliance.org/group/top-threats/), which are listed as follows:

• Data Breaches
• Insufficient identity, credential, and access management
• Insecure interfaces and APIs
• System vulnerabilities
• Account hijacking
• Malicious insiders
• Advanced persistent threats
• Data loss
• Insufficient due diligence
• Abuse and nefarious use of cloud services
• Denial of service
• Shared technology vulnerabilities

Q: What are the security requirements in terms of GDPR compliance?

The following table lists the GDPR security requirements for a software/service of the data processor and data controller:

GDPR requirements	Data processor	Data controller
Provide a data privacy declaration	Must	Must
Data collection requires a user's explicit consent to allow data collection and also to allow the user to disable the data collection	Must	Must
For the purposes of error troubleshooting, the user must be informed whether the collection of logs includes personal information	Must	Must
The collection of a user's cookies requires the user's consent. Refer to https://www.cookielaw.org/the-cookie-law/ for more details.	Must	Must
If the data is collected for marketing analysis purposes, the application must allow users to disable the analysis	Recommended	Must
Provide the ability to remove data securely after the data expires	Must	Must
If the data will be provided to third-party partners, it must have the user's explicit consent	Recommended	Must
Provide the ability for the user to query and update the data	Recommended	Must
Delete any temporary data that is no longer in use	Recommended	Must
Provide the ability to export the data	Recommended	Must
Secure data transmission	Must	Must
Secure local data storage with encryption, access control, and logging security controls	Must	Must

DevSecOps for the development team

Q: What are the recommended security architecture patterns?

• Open Security Architecture Patterns: http://www.opensecurityarchitecture.org/cms/library/patternlandscape
• Security and privacy reference a...