ALZ Zero Trust hub and spoke (#1270)
Co-authored-by: jemitche <jemitche@microsoft.com> Co-authored-by: Jack Tracey <41163455+jtracey93@users.noreply.github.com>
This commit is contained in:
Родитель
e3bc610ef4
Коммит
289d4b9082
|
@ -0,0 +1,49 @@
|
|||
## Azure landing zone portal accelerator deployment with Zero Trust network principles
|
||||
|
||||
This guide will review how to deploy the Azure landing zone portal accelerator with a jump start on Zero Trust Networking Principles for Azure landing zones. If you are looking for a complete walkthrough of the Azure landing zones portal accelerator select one of the deployment guides in the wiki nvaigation on the right of this page under "Deploying Enterprise-Scale". For more information on Zero Trust security model and principles visit [Embrace proactive security with Zero Trust](/security/business/zero-trust). Let's review the [Zero Trust aligned networking](/security/zero-trust/deploy/networks) configurations in the [Azure landing zone portal accelerator](/azure/cloud-adoption-framework/ready/landing-zone/#azure-landing-zone-portal-accelerator).
|
||||
|
||||
## Deploy networking topology and Connectivity
|
||||
|
||||
On the "Network Topology and Connectivity" section of the Azure landing zone portal accelerator select "Hub and spoke with Azure Firewall" radio button. Next, Select the platform connectivity subscription from the drop down. Confirm or update the address space and first networking hub region, in this case East US.
|
||||
|
||||
![Zero Trust Network Topology](./media/zt1.png)
|
||||
|
||||
Hub and spoke is the primary topology option for Zero Trust Organizations. These deployments should have traffic coming in to Azure, going between spokes, or leaving Azure be inspected and only permitted when explicitly allowed. Spoke networks should be segmented into smaller islands with their own ingress and egress controls in minimize "blast radius".
|
||||
|
||||
## Enable Threat protection
|
||||
|
||||
In the next section you will want to leave the defaults to "Enable DDoS Network Protection" and "Deploy Azure Firewall" as these are pivotal requirements for threat protection. It's also recommended to select at least two availability zones for Azure Firewall, but ideally all 3, if the region has availability zone support.
|
||||
|
||||
![Zero Trust enable Threat protection](./media/zt2.png)
|
||||
|
||||
These selections help to segment and enforce external and internal boundaries.
|
||||
|
||||
## Protect the Identity subscription
|
||||
|
||||
On the "Identity" section, ensure the default (Yes) is selected on "Prevent inbound RDP from internet" and "Ensure subnets are associated with NSG".
|
||||
|
||||
![Zero Trust protect the identity subscription](./media/zt3.png)
|
||||
|
||||
Here we are enforcing network protection on resources in the identity subscription (like domain controllers) and what protocols can reach them with Network Security Groups. The current deployment enforces NSGs, but does not have specific rules as these would be managed post-deployment.
|
||||
|
||||
## Secure Application landing zones
|
||||
|
||||
On the "landing zones configuration" section ensure the default (Yes) is selected on:
|
||||
|
||||
"Enable DDoS Network Protection"
|
||||
|
||||
"Prevent usage of Public Endpoints for Azure PaaS services in the corp connected landing zones"
|
||||
|
||||
![Zero Trust enable secure application landing zones](./media/zt4.png)
|
||||
|
||||
"Ensure subnets are associated with NSG"
|
||||
|
||||
"Prevent inbound RDP from internet"
|
||||
|
||||
![Zero Trust enable secure application landing zones](./media/zt5.png)
|
||||
|
||||
"Ensure secure connections (HTTPS) to storage accounts"
|
||||
|
||||
![Zero Trust enable secure application landing zones](./media/zt6.png)
|
||||
|
||||
These configurations ensure that the spokes in your topology that are hosting applications start following zero trust networking principles and practices to enhance and improve their security posture.
|
|
@ -24,6 +24,7 @@
|
|||
* [Telemetry Tracking Using Customer Usage Attribution (PID)](./Deploying-ALZ-CustomerUsage)
|
||||
* [Deploy without hybrid connectivity to on-premises](./Deploying-ALZ-Foundation)
|
||||
* [Deploy with a hub and spoke based network topology](./Deploying-ALZ-HubAndSpoke)
|
||||
* [Deploy with a hub and spoke based network topology with Zero Trust principles](./Deploying-ALZ-ZTNetwork)
|
||||
* [Deploy with an Azure Virtual WAN based network topology](./Deploying-ALZ-VWAN)
|
||||
* [Deploy for Small Enterprises](./Deploying-ALZ-BasicSetup)
|
||||
* [Operating the Azure platform using AzOps (Infrastructure as Code with GitHub Actions)](./Deploying-ALZ-Platform-DevOps#operating-the-azure-platform-using-azops-infrastructure-as-code-with-github-actions)
|
||||
|
|
Двоичный файл не отображается.
После Ширина: | Высота: | Размер: 98 KiB |
Двоичный файл не отображается.
После Ширина: | Высота: | Размер: 53 KiB |
Двоичный файл не отображается.
После Ширина: | Высота: | Размер: 94 KiB |
Двоичный файл не отображается.
После Ширина: | Высота: | Размер: 17 KiB |
Двоичный файл не отображается.
После Ширина: | Высота: | Размер: 14 KiB |
Двоичный файл не отображается.
После Ширина: | Высота: | Размер: 7.9 KiB |
Загрузка…
Ссылка в новой задаче