Hands-On Security in DevOps
Ensure continuous security, deployment, and delivery with DevSecOps
- 356 pages
- English
- ePUB (mobile friendly)
- Available on iOS & Android
Hands-On Security in DevOps
Ensure continuous security, deployment, and delivery with DevSecOps
About This Book
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.
Frequently asked questions
Information
DevSecOps - Challenges, Tips, and FAQs
- 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
- 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/
- 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
| 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
- Open Security Architecture Patterns: http://www.opensecurityarchitecture.org/cms/library/patternlandscape
- Security and privacy reference a...
Table of contents
- Title Page
- Copyright and Credits
- Packt Upsell
- Contributors
- Preface
- DevSecOps Drivers and Challenges
- Security Goals and Metrics
- Security Assurance Program and Organization
- Security Requirements and Compliance
- Case Study - Security Assurance Program
- Security Architecture and Design Principles
- Threat Modeling Practices and Secure Design
- Secure Coding Best Practices
- Case Study - Security and Privacy by Design
- Security-Testing Plan and Practices
- Whitebox Testing Tips
- Security Testing Toolkits
- Security Automation with the CI Pipeline
- Incident Response
- Security Monitoring
- Security Assessment for New Releases
- Threat Inspection and Intelligence
- Business Fraud and Service Abuses
- GDPR Compliance Case Study
- DevSecOps - Challenges, Tips, and FAQs
- Assessments
- Other Books You May Enjoy