Skip to content

Commit 990043c

Browse files
committed
Learn Editor: Update traffic-analytics-zero-trust.md
1 parent 5193108 commit 990043c

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/network-watcher/traffic-analytics-zero-trust.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,6 @@ ms.date: 06/04/2025
1313

1414

1515

16-
## What is Zero Trust ?
17-
1816
Zero Trust is a security strategy. It isn't a product or a service, but an approach in designing and implementing the following set of security principles.
1917

2018
|Principle|Description|
@@ -71,10 +69,10 @@ Traffic patterns are visualized using built-in dashboards, with flexibility to c
7169

7270
As a first critical step to deploy Zero Trust Segmentation over existing or new Azure deployment user needs to
7371

74-
- **Start with default deny posture**: It starts with removing or disabling all existing inbound and outbound rules that allows traffic broadly (eg., Allow All, Allow, etc.,) and adding explicit deny rules for both inbound and outbound traffic.
75-
7672
- **Observe the patterns through Traffic Analytics**: Analyze Flow Logs to identify the traffic patterns that are essential for your workload.
7773

74+
- **Start with default deny posture**: It starts with removing or disabling all existing inbound and outbound rules that allows traffic broadly (eg., Allow All, Allow) and adding explicit deny rules for both inbound and outbound traffic
75+
7876
- **Create selective allow rules**: Based on insights from Traffic Analytics, define rules that explicitly allow only the observed and necessary traffic. This approach ensures that only validated, required traffic is permitted, aligning with Zero Trust principle of Verifying explicitly.
7977

8078
The following sections highlight key scenarios where traffic analytics supports segmentation to help implement Zero Trust principles in Azure.

0 commit comments

Comments
 (0)