Designing and Developing Secure Azure Solutions
- Length: 528 pages
- Edition: 1
- Language: English
- Publisher: Microsoft Press
- Publication Date: 2022-11-18
- ISBN-10: 013790875X
- ISBN-13: 9780137908752
- Sales Rank: #175497 (See Top 100 Books)
Plan, build, and maintain highly secure Azure applications and workloads
As business-critical applications and workloads move to the Microsoft Azure cloud, they must stand up against dangerous new threats. That means you must build robust security into your designs, use proven best practices across the entire development lifecycle, and combine multiple Azure services to optimize security. Now, a team of leading Azure security experts shows how to do just that. Drawing on extensive experience securing Azure workloads, the authors present a practical tutorial for addressing immediate security challenges, and a definitive design reference to rely on for years. Learn how to make the most of the platform by integrating multiple Azure security technologies at the application and network layers– taking you from design and development to testing, deployment, governance, and compliance.
About You
This book is for all Azure application designers, architects, developers, development managers, testers, and everyone who wants to make sure their cloud designs and code are as secure as possible.
Discover powerful new ways to:
Improve app / workload security, reduce attack surfaces, and implement zero trust in cloud code Apply security patterns to solve common problems more easily Model threats early, to plan effective mitigations Implement modern identity solutions with OpenID Connect and OAuth2 Make the most of Azure monitoring, logging, and Kusto queries Safeguard workloads with Azure Security Benchmark (ASB) best practices Review secure coding principles, write defensive code, fix insecure code, and test code security Leverage Azure cryptography and confidential computing technologies Understand compliance and risk programs Secure CI / CD automated workflows and pipelines Strengthen container and network security
Cover Page Title Page Copyright Page Pearson’s Commitment to Diversity, Equity, and Inclusion Dedication Page Contents at a glance Contents Acknowledgments About the Authors Foreword Introduction Organization of this book Who should read this book Conventions and features in this book System requirements GitHub Repo Errata, updates, & book support Stay in touch Part I: Security principles Chapter 1. Secure development lifecycle processes Developers are the number-one source of compromises Introducing the Microsoft Security Development Lifecycle SDL components SDL tasks by sprint The human element Summary Chapter 2. Secure design The cloud, DevOps, and security IaaS vs. PaaS vs. SaaS, and the shared responsibility Zero trust for developers Thinking about secure design Security design principles applied to Azure Summary Chapter 3. Security patterns What is a pattern? Our take on Azure security patterns Authentication pattern Authorization patterns Secrets management patterns Sensitive information management patterns Availability pattern Summary Chapter 4. Threat modeling TL;DR What is threat modeling? The four main phases of threat modeling STRIDE’s threat-classification approach The trouble with threat modeling Searching for a better threat modeling process A better way to perform threat modeling: The five factors Threat-modeling tools How to threat model: A real-life example Summary Chapter 5. Identity, authentication, and authorization Identity, authentication, and authorization through a security lens Authentication vs. authorization vs. identity Modern identity and access management Identity: OpenID Connect and OAuth2 fundamentals Authentication Authorization Summary Chapter 6. Monitoring and auditing Monitoring, auditing, logging, oh my! Leveraging the Azure platform The need for intentional security monitoring and auditing Summary Chapter 7. Governance Governance and the developer Azure Security Benchmark version 3 Governance enforcement Microsoft Defender for Cloud Azure Policy Summary Chapter 8. Compliance and risk programs Something important to get out of way What is compliance? Using threat models to drive compliance artifacts Summary Part II: Secure implementation Chapter 9. Secure coding Insecure code Rule #1: All input is evil Verify explicitly Common vulnerabilities Comments about using C++ Security code review Keeping developers honest with fuzz testing Summary Chapter 10. Cryptography in Azure A truth about security Securing keys Cryptographic agility The Microsoft Data Encryption SDK Azure services and cryptography Key rotation Protecting data in transit Summary Chapter 11. Confidential computing What is confidential computing? Confidential computing processors Azure Services that use confidential computing Summary Chapter 12. Container security What are containers? Container-related services on Azure Problems with containers Securing container services Summary Chapter 13. Database security Why database security? Which databases? Thinking about database security The SQL Server Family Security in the SQL Server family Cosmos DB security Encryption of data in use: Always Encrypted SQL injection Summary Chapter 14. CI/CD security What is CI/CD? CI/CD tools Source control systems and supply chain attacks Secrets and service connections Protecting the main branch in Azure DevOps and GitHub Protecting the PROD deployment in Azure DevOps and GitHub Securing deployment agents Summary Chapter 15. Network security Azure networking primer Landing zones, hubs, and spokes NVAs and gateways PaaS and private networking Azure Kubernetes Service networking The dangling DNS problem Summary Appendix A. Core cryptographic techniques Why this appendix? Thinking about cryptography Symmetric ciphers Asymmetric ciphers Hashes Message authentication codes Digital signatures Certificates Key derivation Cryptographic vulnerabilities Index Code Snippets
Donate to keep this site alive
1. Disable the AdBlock plugin. Otherwise, you may not get any links.
2. Solve the CAPTCHA.
3. Click download link.
4. Lead to download server to download.