|
1 | 1 | ---
|
2 |
| -title: Azure application security groups overview |
| 2 | +title: Azure Application Security Groups Overview |
3 | 3 | titlesuffix: Azure Virtual Network
|
4 |
| -description: Learn about the use of application security groups. |
| 4 | +description: Learn how application security groups enable you to configure network security policies and group virtual machines. |
5 | 5 | author: asudbring
|
6 | 6 | ms.service: azure-virtual-network
|
7 | 7 | ms.topic: concept-article
|
8 |
| -ms.date: 07/09/2025 |
| 8 | +ms.date: 07/25/2025 |
9 | 9 | ms.author: allensu
|
10 | 10 | # Customer intent: As a network administrator, I want to configure application security groups for my virtual machines, so that I can easily manage network security policies and reduce the complexity of maintaining explicit IP addresses.
|
11 | 11 | ---
|
12 | 12 |
|
13 | 13 | # Application security groups
|
14 | 14 |
|
15 |
| -Application security groups enable you to configure network security as a natural extension of an application's structure, allowing you to group virtual machines and define network security policies based on those groups. You can reuse your security policy at scale without manual maintenance of explicit IP addresses. The platform handles the complexity of explicit IP addresses and multiple rule sets, allowing you to focus on your business logic. To better understand application security groups, consider the following example: |
| 15 | +Application security groups in Azure Virtual Network enable you to configure network security as a natural extension of an application's structure, allowing you to group virtual machines and define network security policies based on those groups. You can reuse your security policy at scale without manual maintenance of explicit IP addresses. The platform handles the complexity of explicit IP addresses and multiple rule sets, allowing you to focus on your business logic. To better understand application security groups, consider the following example: |
16 | 16 |
|
17 |
| -:::image type="content" source="./media/security-groups/application-security-groups.png" alt-text="Diagram of Application security groups."::: |
| 17 | +:::image type="content" source="./media/security-groups/application-security-groups.png" alt-text="Screenshot of Application security groups diagram showing network interfaces grouped into AsgWeb, AsgLogic, and AsgDb security groups."::: |
18 | 18 |
|
19 | 19 | In the previous picture, *NIC1* and *NIC2* are members of the *AsgWeb* application security group. *NIC3* is a member of the *AsgLogic* application security group. *NIC4* is a member of the *AsgDb* application security group. Although each network interface (NIC) in this example is a member of only one application security group, a network interface can be a member of multiple application security groups, up to the [Azure limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#azure-resource-manager-virtual-networking-limits). None of the network interfaces have an associated network security group. *NSG1* is associated to both subnets and contains the following rules:
|
20 | 20 |
|
21 | 21 | ## Allow-HTTP-Inbound-Internet
|
22 | 22 |
|
23 | 23 | This rule is needed to allow traffic from the internet to the web servers. Because inbound traffic from the internet is denied by the **DenyAllInbound** default security rule, no extra rule is needed for the *AsgLogic* or *AsgDb* application security groups.
|
24 | 24 |
|
25 |
| -|Priority|Source|Source ports| Destination | Destination ports | Protocol | Access | |
26 |
| -|---|---|---|---|---|---|---| |
27 |
| -| 100 | Internet | * | AsgWeb | 80 | TCP | Allow | |
| 25 | +| Priority | Source | Source ports | Destination | Destination ports | Protocol | Access | |
| 26 | +|----------|----------|--------------|-------------|-------------------|----------|--------| |
| 27 | +| 100 | Internet | * | AsgWeb | 80 | TCP | Allow | |
28 | 28 |
|
29 | 29 | ## Deny-Database-All
|
30 | 30 |
|
31 | 31 | Because the **AllowVNetInBound** default security rule allows all communication between resources in the same virtual network, you need this rule to deny traffic from all resources.
|
32 | 32 |
|
33 |
| -|Priority|Source|Source ports| Destination | Destination ports | Protocol | Access | |
34 |
| -|---|---|---|---|---|---|---| |
35 |
| -| 120 | * | * | AsgDb | 1433 | Any | Deny | |
| 33 | +| Priority | Source | Source ports | Destination | Destination ports | Protocol | Access | |
| 34 | +|----------|--------|--------------|-------------|-------------------|----------|--------| |
| 35 | +| 120 | * | * | AsgDb | 1433 | Any | Deny | |
36 | 36 |
|
37 | 37 | ## Allow-Database-BusinessLogic
|
38 | 38 |
|
39 | 39 | This rule allows traffic from the *AsgLogic* application security group to the *AsgDb* application security group. The priority for this rule is higher than the priority for the *Deny-Database-All* rule. As a result, this rule is processed before the *Deny-Database-All* rule, so traffic from the *AsgLogic* application security group is allowed, whereas all other traffic is blocked.
|
40 | 40 |
|
41 |
| -|Priority|Source|Source ports| Destination | Destination ports | Protocol | Access | |
42 |
| -|---|---|---|---|---|---|---| |
43 |
| -| 110 | AsgLogic | * | AsgDb | 1433 | TCP | Allow | |
| 41 | +| Priority | Source | Source ports | Destination | Destination ports | Protocol | Access | |
| 42 | +|----------|----------|--------------|-------------|-------------------|----------|--------| |
| 43 | +| 110 | AsgLogic | * | AsgDb | 1433 | TCP | Allow | |
44 | 44 |
|
45 | 45 | Network interfaces that are members of the application security group apply the network security group rules that specify it as the source or destination. The network security group rules don't affect other network interfaces. If the network interface isn't a member of an application security group, the rule doesn't apply to the network interface, even though the network security group is associated to the subnet.
|
46 | 46 |
|
|
0 commit comments