Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Commit

Permalink
adding new fw recommendations (#343)
Browse files Browse the repository at this point in the history
Co-authored-by: Eric Henry <[email protected]>
  • Loading branch information
cshea-msft and ejhenry authored Mar 26, 2024
1 parent ef32fb3 commit a66f083
Show file tree
Hide file tree
Showing 3 changed files with 50 additions and 0 deletions.
48 changes: 48 additions & 0 deletions docs/content/services/networking/firewall/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ The presented resiliency recommendations in this guidance include Firewall and a
| [AFW-2 - Monitor Azure Firewall metrics](#afw-2---monitor-azure-firewall-metrics) | Monitoring | Medium | Verified | Yes |
| [AFW-3 - Configure DDoS Protection on the Azure Firewall VNet](#afw-3---configure-ddos-protection-on-the-azure-firewall-vnet) | Access & Security | High | Verified | Yes |
| [AFW-4 - Leverage Azure Policy inheritance model](#afw-4---leverage-azure-policy-inheritance-model) | Governance | Medium | Verified | No |

{{< /table >}}

{{< alert style="info" >}}
Expand Down Expand Up @@ -129,3 +130,50 @@ Azure Firewall policy allows you to define a rule hierarchy and enforce complian
{{< /collapse >}}

<br><br>

### AFW-5 - Configure 2-4 PIPs for SNAT Port utilization

**Category: Availability**

**Impact: Medium**

**Guidance**

Configure a minimum of two to four public IP addresses per Azure Firewall to avoid SNAT exhaustion. Azure Firewall provides SNAT capability for all outbound traffic traffic to public IP addresses. Azure Firewall provides 2,496 SNAT ports per each additional PIP.

**Resources**

- [Azure Well-Architected Framework review - Azure Firewall](https://learn.microsoft.com/en-us/azure/well-architected/service-guides/azure-firewall#recommendations)

**Resource Graphy Query/Scripts**

{{< collapse title="Show/Hide Query/Script" >}}

{{< code lang="sql" file="code/afw-5/afw-5.kql" >}} {{< /code >}}

{{< /collapse >}}

<br><br>

### AFW-6 - Monitor AZFW Latency Probes metric

**Category: Monitoring**

**Impact: Medium**

**Guidance**

Create the metric to monitor latency probes 20ms over a long period of time ( > 30mins ). When the latency probe is over a long period of time, it means the firewall instance CPUs are stressed and could possible be causing issues.

**Resources**

- [Azure Well-Architected Framework review - Azure Firewall](https://learn.microsoft.com/azure/well-architected/service-guides/azure-firewall#recommendations)
- [Azure Firewall metrics overview](https://learn.microsoft.com/azure/firewall/metrics)

**Resource Graphy Query/Scripts**

{{< collapse title="Show/Hide Query/Script" >}}

{{< code lang="sql" file="code/afw-6/afw-6.kql" >}} {{< /code >}}

{{< /collapse >}}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
// under development
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
// under development

0 comments on commit a66f083

Please sign in to comment.