Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EDU-6108] AI documentation update - 2025-01-24 - configure waf allowed rules #1462

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[EDU-6108] AI documentation update - 2025-01-24 - configure waf allowed rules #1462

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 22 additions & 2 deletions src/content/docs/en/pages/guides/waf/configure-allowed-rules.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,17 @@ To instantiate Custom Allowed Rules in a WAF Rule Set, you must have:

---

## Creating a Network List for IPs to Bypass WAF Rules

1. Access [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/).
2. Navigate to **Network Lists** under **Edge Libraries**.
3. Click the **+ New Network List** button.
4. Enter a name and description for the Network List.
5. Add IP addresses or IP ranges that should bypass WAF rules.
6. Save the Network List.

---

## Configuring a WAF Custom Allowed Rule

<Tabs client:visible>
Expand Down Expand Up @@ -75,8 +86,17 @@ To instantiate Custom Allowed Rules in a WAF Rule Set, you must have:

</Tabs>

## GMUD Process for Implementing New WAF Configurations

When implementing new WAF configurations, follow the GMUD (Change Management) process:

1. Draft a detailed plan outlining the changes to be made, including potential impacts and rollback procedures.
2. Submit the plan for approval to the Change Advisory Board (CAB).
3. Once approved, schedule a maintenance window for implementing the changes.
4. Implement the changes during the scheduled window, ensuring all changes are logged.
5. Monitor the system for any issues post-implementation.
6. Document the outcome and close the change request.

:::tip
You can configure a Custom Allowed Rule based on the WAF Tuning records. Consult the guide on [How to tune WAF](/en/documentation/products/guides/secure/tune-waf/) for more information.
:::