You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Access is granted **at access time** based on identity and policy evaluation.
633
631
* Avoids reliance on network location (IP, subnet, etc.).
634
632
* Strong identity verification, least privilege access, and micro-segmentation.
@@ -648,8 +646,6 @@ flowchart TD
648
646
649
647
**Definition**: A lightweight computer that relies on a server to perform most processing tasks.
650
648
651
-
### ✅ Characteristics:
652
-
653
649
* Minimal or **no local data storage**.
654
650
* All applications and processing occur **on the server**.
655
651
* Enhances **security** and simplifies **desktop management**.
@@ -662,11 +658,12 @@ flowchart TD
662
658
663
659
**Private IPs** allow resources within an Azure Virtual Network (VNet) to communicate securely without exposure to the internet.
664
660
665
-
### ✅ Key Features:
666
-
667
661
***Non-routable** (RFC 1918 compliant).
668
662
* Used for internal communication between VMs in the same or peered VNets.
669
663
***Allocated dynamically** or statically from the VNet’s address space.
664
+
* IPs are associated with NICs via Azure Resource Manager (ARM) configurations, not manually or directly by the admin.
665
+
For load balancers, IPs are assigned to frontend configurations, not directly to the NIC.
666
+
670
667
671
668
**🔎 Tip**: Private IPs are the default addressing method inside Azure VNets. Public IPs are required only for external communication.
672
669
@@ -683,7 +680,7 @@ flowchart TD
683
680
684
681
**Purpose**: Automatically mitigates distributed denial of service (DDoS) attacks.
685
682
686
-
### ✅ How It Works:
683
+
By examining network traffic patterns and looking for any irregularities that could point to a DDoS assault, Azure DDoS Protection Standard operates. To build a baseline of typical traffic behavior, it employs traffic profiling and machine learning techniques. A suspicious alert is raised for any traffic that deviates from this baseline.
687
684
688
685
* Monitors network traffic to build a **baseline** of normal behavior.
689
686
* Uses **machine learning** to detect **anomalies**.
@@ -718,18 +715,15 @@ graph LR
718
715
To allow HTTP (port 80) and block SSH (port 22) to Marketing VMs:
719
716
720
717
* Create an **Application Rule** to allow HTTP.
721
-
*Create a **Network Rule** to **block SSH**.
718
+
*SSH traffic is already denied by default rules.
722
719
723
-
**🔎 Best Practice**: Use Application Rules for web-based FQDN filtering and Network Rules for lower-level IP filtering.
724
720
725
721
---
726
722
727
723
## 6. Azure Firewall Manager
728
724
729
725
**Purpose**: Centralized management for Azure Firewall policies across regions/subscriptions.
730
726
731
-
### ✅ Benefits:
732
-
733
727
* Unified visibility and **policy enforcement**.
734
728
* Consistency across **multiple firewalls**.
735
729
* Integration with **Secure Virtual Hub** in Azure Virtual WAN.
@@ -742,8 +736,6 @@ To allow HTTP (port 80) and block SSH (port 22) to Marketing VMs:
742
736
743
737
**Definition**: A private, dedicated connection between on-premises infrastructure and Azure.
744
738
745
-
### ✅ Features:
746
-
747
739
***Bypasses the public internet** for secure, low-latency communications.
748
740
* Supported via **IP VPN** (MPLS) or Ethernet connections.
749
741
* Offers **layer 2 and layer 3 connectivity** options.
@@ -756,8 +748,6 @@ To allow HTTP (port 80) and block SSH (port 22) to Marketing VMs:
756
748
757
749
**Azure VPN Gateway** allows encrypted communication over public networks.
758
750
759
-
### ✅ Uses:
760
-
761
751
***Site-to-site VPNs** (on-prem to Azure).
762
752
***VNet-to-VNet VPNs** (intra-Azure region).
763
753
* Supports **IKEv2 and IPsec** protocols.
@@ -776,8 +766,6 @@ graph TD
776
766
777
767
**Definition**: A VM-based appliance offering advanced networking capabilities like IDS/IPS, WAF, or custom routing.
778
768
779
-
### ✅ Use Case:
780
-
781
769
* Performs **deep packet inspection**.
782
770
***Controls inbound and outbound** traffic.
783
771
* Useful when built-in services like Azure Firewall don’t meet specific requirements.
@@ -790,8 +778,6 @@ graph TD
790
778
791
779
**Forced Tunneling**: Routes **all** Azure VNet traffic destined for the internet through on-premises via a VPN connection.
792
780
793
-
### ✅ Purpose:
794
-
795
781
* Enforce **centralized security inspection**.
796
782
* Ensure **logging and compliance**.
797
783
* Directs outbound traffic via on-prem **proxy or firewall**.
0 commit comments