Skip to content

Commit 92994fa

Browse files
committed
screenshots and edit
1 parent 1e30689 commit 92994fa

File tree

7 files changed

+45
-9
lines changed

7 files changed

+45
-9
lines changed

articles/dns/dns-security-policy.md

Lines changed: 45 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -21,36 +21,72 @@ This article provides an overview of DNS security policy. Also see the following
2121
2222
## What DNS security policy?
2323

24-
DNS security policy offers the ability to filter and log DNS queries at the virtual network (VNet) level and view detailed DNS logs. Think of it like a DNS firewall for your cloud resources. You can allow, alert, or block name resolution of known or malicious domains. The logging capability enables you to gain detailed insight into your DNS traffic. DNS logs can be sent to a storage account, log analytics workspace, or event hubs.
24+
DNS security policy offers the ability to filter and log DNS queries at the virtual network (VNet) level. With DNS security policy you can:
25+
- Create rules to protect against DNS-based attacks by blocking block name resolution of known or malicious domains.
26+
- Save and view detailed DNS logs to gain inside into your DNS traffic.
27+
28+
DNS logs can be sent to a storage account, log analytics workspace, or event hubs. You can choose to allow, alert, or block DNS queries.
2529

2630
A DNS security policy has the following associated elements and properties:
27-
- **Location**: A security policy can only apply to VNets in the same region.
28-
- **DNS traffic rules**: Rules that allow, block, or alert based on priority and domain lists. Rules can be enabled or disabled.
29-
- **Virtual network links**: You can link one security policy per VNet. A security policy can be associated to multiple VNets.
30-
- **DNS domain lists**: Location-based lists of DNS domains.
31+
- **[Location](#location)**: The Azure region where the security policy is created and deployed.
32+
- **[DNS traffic rules](#dns-traffic-rules)**: Rules that allow, block, or alert based on priority and domain lists. Rules can be enabled or disabled.
33+
- **[Virtual network links](#virtual-network-links)**: A link that associates the security policy to a VNet. You can link one security policy per VNet. A single security policy can be associated to multiple VNets.
34+
- **[DNS domain lists](#dns-domain-lists)**: Location-based lists of DNS domains.
3135

3236
DNS Security Policy can be configured using Azure PowerShell or the Azure portal.
3337

3438
### Location
3539

36-
You can create any number of security policies in the same region. In the following example, two polices are created in each of two different regions (East US and Central US). Keep in mind that the policy:VNet relationship is 1:N. When you associate a VNet with a security policy (via virtual network links), that VNet can't then be associated with another security policy. However, a single DNS security policy can be associated with multiple VNets in the same region.
40+
A security policy can only apply to VNets in the same region. You can create any number of security policies in the same region. In the following example, two polices are created in each of two different regions (East US and Central US).
3741

3842
![Screenshot of the list of DNS security policies.](./media/dns-security-policy/policy-list.png)
3943

44+
Keep in mind that >the policy:VNet relationship is 1:N. When you associate a VNet with a security policy (via virtual network links), that VNet can't then be associated with another security policy. A single DNS security policy can be associated with multiple VNets in the same region.
45+
4046
### DNS traffic rules
4147

48+
To display DNS traffic rules in the Azure portal, select a DNS security policy and then under **Settings**, select **DNS Traffic Rules**. See the following example:
49+
50+
[ ![Screenshot of the list of DNS traffic rules.](./media/dns-security-policy/traffic-rules.png) ](./media/dns-security-policy/traffic-rules.png#lightbox)
51+
52+
- Rules are processed in order of **Priority** in the range 100-65000. Lower numbers are higher priority.
53+
* If a domain name is blocked in a lower priority rule, and the same domain is allowed in a higher priority rule, the domain name is allowed.
54+
* Rule priority takes precedence over the number of labels in a domain name. If contoso.com is allowed in a higher priority rule, then sub.contoso.com is allowed, even if sub.contoso.com is blocked in a lower priority rule.
55+
- You can dynamically add and delete rules from the list. Be sure to **Save** after editing rules in the portal.
56+
- During preview, up to 10 traffic rules are allowed per security policy. This limit will be increased to 100 for general availability.
57+
- Multiple **DNS Domain Lists** are allowed per rule. You must have at least one DNS domain list.
58+
- Each rule is associated with one of three **Traffic Actions**: **Allow**, **Block**, or **Alert**.
59+
* Allow: Permit the query to the associated domain lists and log the query.
60+
* Block: Block the query to the associated domain lists and log the block action.
61+
* Alert: Permit the query to the associated domain lists and log an alert.
62+
- Rules can be individually **Enabled** or **Disabled**.
63+
4264
### Virtual network links
4365

66+
DNS security policies only apply to VNets that are linked to the security policy. You can link a single security policy to multiple VNets, however a single VNet can only be linked to one DNS security policy. See the following example.
67+
68+
[ ![Screenshot of the list of virtual network links.](./media/dns-security-policy/virtual-network-links.png) ](./media/dns-security-policy/virtual-network-links.png#lightbox)
69+
70+
You can only link VNets that are in the same region as the security policy. When you link a VNet to a DNS security policy using a virtual network link, the DNS security policy applies to all resources inside the VNet.
71+
4472
### DNS domain lists
4573

74+
DNS domain lists are lists of DNS domains that you associate to traffic rules. Select **DNS Domain Lists** under **Settings** for a DNS security policy to view the current domain lists associated with the policy. See the following example:
75+
76+
[ ![Screenshot of the list of DNS domain lists.](./media/dns-security-policy/domain-list.png) ](./media/dns-security-policy/domain-list.png#lightbox)
77+
78+
You can associate a domain list to multiple DNS traffic rules in different security policies.
79+
80+
![Screenshot of domains inside a domain list.](./media/dns-security-policy/domain-list-detailed.png)
81+
82+
When viewing a DNS domain list in the Azure portal, you can also select **Settings** > **Associated DNS Traffic Rules** to see a list of all traffic rules and thye associated DNS security policies that reference the DNS domain list.
83+
84+
![Screenshot of associated domain list traffic rules.](./media/dns-security-policy/domain-list-traffic-rules.png)
4685

4786
## Requirements and restrictions
4887

4988
Virtual network restrictions:
5089
- DNS security policies can only be applied to virtual networks in the same region as the DNS security policy.
51-
- DNS security policy cannot be deleted unless the virtual network links under it are deleted.
52-
53-
5490

5591
## Related content
5692

126 KB
Loading
126 KB
Loading
87.2 KB
Loading
132 KB
Loading
168 KB
Loading
153 KB
Loading

0 commit comments

Comments
 (0)