Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Azure Cloud Native Architecture Mapbook

You're reading from   The Azure Cloud Native Architecture Mapbook Explore Microsoft Cloud's infrastructure, application, data, and security architecture

Arrow left icon
Product type Paperback
Published in Feb 2021
Publisher Packt
ISBN-13 9781800562325
Length 376 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Stéphane Eyskens Stéphane Eyskens
Author Profile Icon Stéphane Eyskens
Stéphane Eyskens
Ed Price Ed Price
Author Profile Icon Ed Price
Ed Price
Ed Price Ed Price
Author Profile Icon Ed Price
Ed Price
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Section 1: Solution and Infrastructure
2. Chapter 1: Getting Started as an Azure Architect FREE CHAPTER 3. Chapter 2: Solution Architecture 4. Chapter 3: Infrastructure Design 5. Chapter 4: Infrastructure Deployment 6. Section 2: Application Development, Data, and Security
7. Chapter 5: Application Architecture 8. Chapter 6: Data Architecture 9. Chapter 7: Security Architecture 10. Section 3: Summary
11. Chapter 8: Summary and Industry Scenarios 12. Other Books You May Enjoy

Introducing cloud-native security

In light of what we have seen so far in previous chapters, we know that the cloud can help us develop and deploy solutions faster and at a better cost. However, that is only true if we also modernize the way that we secure our workloads. Cloud-native security relies on the Shift-Left principle, which consists of integrating security processes earlier in the life cycle of an asset. Considering security from the ground up prevents unexpected delays and surprises later, prior to the production deployment. However, this is easier said than done!

Often, we see developers (usually early adopters) and infrastructure engineers embracing this modernized way of working (with Infrastructure as Code (IaC)), while security remains organized in a traditional way (waterfall and reactive). Often, you must wait weeks, if not more, to have a firewall rule ticket request accepted and implemented. This way of working is the exact opposite of the Shift-Left mindset...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime