diff --git a/documentation/waap/analytics.md b/documentation/waap/analytics.md
index e81c4368..00984e37 100644
--- a/documentation/waap/analytics.md
+++ b/documentation/waap/analytics.md
@@ -132,7 +132,7 @@ Updating filters on the table doesn’t change the data displayed on the Web App
### Requests table
This table displays incoming requests for the past 24 hours, including good and bad ones (potential threats). Request history is retained for 30 days.
-
+
You can select multiple filters to get a more granular view of the displayed information in the table.
@@ -229,7 +229,7 @@ This page provides in-depth information about a particular request made to your
1\. In the top-right corner of the screen, click **Create rule for IP**.
-
+
2\. Choose the relevant action:
* Allow requests from this IP
@@ -245,13 +245,13 @@ The rules to block or allow requests will appear on the
+
### Top threat origins
This map and table display the origin location of bad requests (threats) from the last 24 hours. You can view the country from which requests are coming and the total number of requests for that country.
-
+
## DDoS attacks page
@@ -263,7 +263,7 @@ If there is an active DDoS attack, you’ll see a banner at the top of the page
Clicking the **View attack** link will take you to the DDoS analytics page, where you can view more details related to that specific attack.
-
+
### Attacks over time
@@ -271,25 +271,25 @@ Requests associated with DDoS attacks are presented in a plot format.
To filter DDoS request data by the timeframe of each attack, click the dropdown menu in the top-right corner of the screen and select the checkbox next to the attack you want to view. You can view up to four sets of timeframes simultaneously.
-
+
### IPs participated
This table displays a list of the top IP addresses associated with the selected DDoS attack, along with the total number of times each IP has made a request to your domain.
-
+
### URLs targeted
This table displays a list of the top URLs that were requested during a DDoS attack, along with the number of times each URL was requested.
-
+
### User agents
This table displays a list of the top clients, tools, and user agents associated with the selected DDoS attack. It also shows the total number of times each of them has made a request to your site.
-
+
### Attack requests
diff --git a/documentation/waap/api-discovery-and-protection/api-discovery.md b/documentation/waap/api-discovery-and-protection/api-discovery.md
index 53015c29..ff5b4241 100644
--- a/documentation/waap/api-discovery-and-protection/api-discovery.md
+++ b/documentation/waap/api-discovery-and-protection/api-discovery.md
@@ -142,11 +142,11 @@ After you identify the endpoint as a confirmed API, it will be moved to the API
## Scan history
-This page lists all endpoints identified by the system:
+This page the history of scans performed by the system:
-* Via automated network scan. The default scan frequency is set to 24 hours, but you can adjust it on the **Settings** page.
+* Automated network scans. The default scan frequency is set to 24 hours, but you can adjust it on the **Settings** page.
-* From the uploaded Swagger file (if you added it to the Settings page).
+* Scans of the uploaded Swagger file (if you added it to the **Settings** page).
diff --git a/documentation/waap/getting-started/configure-waap-for-a-domain.md b/documentation/waap/getting-started/configure-waap-for-a-domain.md
index fc486a42..6fd90505 100644
--- a/documentation/waap/getting-started/configure-waap-for-a-domain.md
+++ b/documentation/waap/getting-started/configure-waap-for-a-domain.md
@@ -129,7 +129,7 @@ If your domain doesn’t use a CMS, we highly recommend allowlisting the site ad
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the needed domain and click its name to open it. You'll be directed to the **Policies** page.
@@ -137,7 +137,7 @@ If your domain doesn’t use a CMS, we highly recommend allowlisting the site ad
4\. In the **Allowed IPs** section, click **Add IP/IP Range**.
-
+
5\. Enter any admin user's public IP address.
@@ -157,7 +157,7 @@ If you use content management systems, such as WordPress, allow traffic for CMS
4\. On the **Policies** page, find CMS protection, and then allow traffic for a desired content management system by enabling a toggle next to it.
-
+
@@ -175,7 +175,7 @@ Follow these steps to allow crawlers, scanners, monitoring bots, and similar too
3\. Click the **Common automated services** to expand the section and enable the desired bot.
-
+
The common automated services policy group allows a few trusted bots by default, which is why we recommend reviewing this list before enabling the protect mode.
@@ -195,4 +195,4 @@ You can
+
diff --git a/documentation/waap/getting-started/manage-domains.md b/documentation/waap/getting-started/manage-domains.md
index ee95fa4b..dc0228e9 100644
--- a/documentation/waap/getting-started/manage-domains.md
+++ b/documentation/waap/getting-started/manage-domains.md
@@ -15,7 +15,7 @@ pageDescription: Learn how to manage, delete, and deactivate domains in Gcore WA
After you activate WAAP for your domain in CDN, it will appear on the **Domains** page in the Gcore Customer Portal. Here, you can view all domains and their statuses, navigate to the CDN settings, and delete inactive domains.
-
+
A domain in WAAP can have the following statuses:
@@ -39,7 +39,7 @@ To disable WAAP protection for a domain:
2\. Next to the resource that you want to protect with WAAP, click the three-dot icon and select **Settings**.
-
+
3\. Navigate to the relevant section:
@@ -67,7 +67,7 @@ To delete an inactive domain:
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Click the three-dot icon next to the domain that you want to remove.
diff --git a/documentation/waap/getting-started/waap-modes.md b/documentation/waap/getting-started/waap-modes.md
index d77b9aec..b1cf8c25 100644
--- a/documentation/waap/getting-started/waap-modes.md
+++ b/documentation/waap/getting-started/waap-modes.md
@@ -99,7 +99,7 @@ You can also see the difference on the **Analytics** page in the
+
## Enable monitor and protect modes for your domain
@@ -115,10 +115,10 @@ Here’s an example of how to enable protect mode for your domain:
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the domain for which you want to enable a WAAP mode and click the domain name to open it. You'll be directed to the **Policies** page.
3\. In the upper-right corner of the screen, next to the WAAP mode, select **Protect** from the dropdown.
-
+
diff --git a/documentation/waap/ip-security/allow-and-block-ip-addresses.md b/documentation/waap/ip-security/allow-and-block-ip-addresses.md
index 370cecf2..ea8ee59c 100644
--- a/documentation/waap/ip-security/allow-and-block-ip-addresses.md
+++ b/documentation/waap/ip-security/allow-and-block-ip-addresses.md
@@ -15,7 +15,7 @@ Our firewall is your first line of protection to block or allow specific IP addr
All rules with allowed or blocked IPs appear on the **Firewall** page.
-
+
A rule can appear on this page in one of the following ways:
@@ -37,13 +37,13 @@ You can allow and block traffic for both IPv4 and IPv6 addresses. For each addre
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the needed domain and click its name to open it. You'll be directed to the **Policies** page.
3\. In the sidebar, click **Firewall**.
-
+
4\. Navigate to the needed section:
@@ -51,7 +51,7 @@ You can allow and block traffic for both IPv4 and IPv6 addresses. For each addre
* **Block IPs**: Deny IPs or IP ranges access to your domain.
-
+
5\. Click **Add IP/IP Range**. To allow or block traffic for an IP range, enter its first and last IP address.
@@ -91,13 +91,13 @@ To update or remove an IP or IP range:
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the needed domain and click its name to open it. You'll be directed to the **Policies** page.
3\. In the sidebar, click **Firewall**.
-
+
4\. Navigate to the needed section with the configured IP address—**Allow IPs** or **Block IPs**.
@@ -105,10 +105,10 @@ To update or remove an IP or IP range:
6\. Select the relevant action from the dropdown—**Edit** or **Delete**—and follow the instructions.
-
+
## Delete multiple rules with group actions
You can simultaneously delete multiple rules that allow or block particular IPs or IP ranges. To do so, select checkboxes next to the firewall rules you want to delete and then choose the **Delete** action from the **Actions** dropdown.
-
+
diff --git a/documentation/waap/response-pages/create-custom-response-pages.md b/documentation/waap/response-pages/create-custom-response-pages.md
index 9634081d..97f43348 100644
--- a/documentation/waap/response-pages/create-custom-response-pages.md
+++ b/documentation/waap/response-pages/create-custom-response-pages.md
@@ -61,7 +61,7 @@ Note that creating custom response pages is only available
+
### Step 4. Configure the selected response page
@@ -127,7 +127,7 @@ If you don’t enable the toggle, the page won’t be available for use on any d
1\. Select the domains where the new custom response page will appear.
-
+
2\. Click **Save** to add the page to the selected domains.
diff --git a/documentation/waap/response-pages/manage-custom-response-pages.md b/documentation/waap/response-pages/manage-custom-response-pages.md
index 9d7ce513..2342f66a 100644
--- a/documentation/waap/response-pages/manage-custom-response-pages.md
+++ b/documentation/waap/response-pages/manage-custom-response-pages.md
@@ -126,7 +126,7 @@ To delete a page:
3\. Select **Delete**.
-
+
4\. Click **Delete**.
diff --git a/documentation/waap/waap-policies/advanced-api-protection.md b/documentation/waap/waap-policies/advanced-api-protection.md
index 35983960..8326b26b 100644
--- a/documentation/waap/waap-policies/advanced-api-protection.md
+++ b/documentation/waap/waap-policies/advanced-api-protection.md
@@ -31,13 +31,13 @@ You can review the Advanced API protection policy group and enable or disable it
1\. Navigate to **WAAP** > **Domains**.
-
+
2\. Find the domain where you want to configure the policy and click the domain name to open it.
3\. On the **Policies** page that opens, click **Advanced API protection** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-policies/anti-automation-and-bot-protection.md b/documentation/waap/waap-policies/anti-automation-and-bot-protection.md
index 1441cdb2..22d00ae5 100644
--- a/documentation/waap/waap-policies/anti-automation-and-bot-protection.md
+++ b/documentation/waap/waap-policies/anti-automation-and-bot-protection.md
@@ -30,13 +30,13 @@ Our WAAP includes a pre-defined anti-automation & bot protection policy group to
1\. Navigate to **WAAP** > **Domains**.
-
+
2\. Find the domain where you want to configure the policy and click the domain name to open it.
3\. On the **Policies** page that opens, click **Anti-automation and bot protection** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-policies/behavioral-waf.md b/documentation/waap/waap-policies/behavioral-waf.md
index 08f70e5e..a15a83f5 100644
--- a/documentation/waap/waap-policies/behavioral-waf.md
+++ b/documentation/waap/waap-policies/behavioral-waf.md
@@ -29,13 +29,13 @@ You can review the Behavioral WAF policy group and enable or disable its policie
1\. Navigate to **WAAP** > **Domains**.
-
+
2\. Find the domain where you want to configure the policy and click the domain name to open it.
3\. On the **Policies** page that opens, click **Behavioral WAAP** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-policies/cms-protection.md b/documentation/waap/waap-policies/cms-protection.md
index 1185d236..a32ce0aa 100644
--- a/documentation/waap/waap-policies/cms-protection.md
+++ b/documentation/waap/waap-policies/cms-protection.md
@@ -36,13 +36,13 @@ You can review the policy group and enable or disable its policies in the **Domains**.
-
+
2\. Find the domain where you want to configure the policy and click the domain name to open it.
3\. On the **Policies** page that opens, click **CMS protection** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-policies/common-automated-services.md b/documentation/waap/waap-policies/common-automated-services.md
index b0a88eef..a6b109ad 100644
--- a/documentation/waap/waap-policies/common-automated-services.md
+++ b/documentation/waap/waap-policies/common-automated-services.md
@@ -33,11 +33,11 @@ You can review and enable relevant policies in the
+
2\. Find the domain where you want to configure the policy and click the domain name to open it.
3\. On the **Policies** page that opens, click **Common automated services** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-policies/ip-reputation.md b/documentation/waap/waap-policies/ip-reputation.md
index debf111b..c667e06d 100644
--- a/documentation/waap/waap-policies/ip-reputation.md
+++ b/documentation/waap/waap-policies/ip-reputation.md
@@ -34,13 +34,13 @@ You can review the IP reputation policy group and enable or disable its policies
1\. Navigate to **WAAP** > **Domains**.
-
+
2\. Find the domain where you want to configure the policy group and click the domain name to open it.
3\. On the **Policies** page that opens, click **IP reputation** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-policies/protocol-validation.md b/documentation/waap/waap-policies/protocol-validation.md
index 410b6f43..c4f09151 100644
--- a/documentation/waap/waap-policies/protocol-validation.md
+++ b/documentation/waap/waap-policies/protocol-validation.md
@@ -21,13 +21,13 @@ You can review the Protocol validation policy group and enable or disable its po
1\. Navigate to **WAAP** > **Domains**.
-
+
2\. Find the domain where you want to configure the policy group and click the domain name to open it.
3\. On the **Policies** page that opens, click **Protocol validation** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-policies/waf-and-owasp-top-threats.md b/documentation/waap/waap-policies/waf-and-owasp-top-threats.md
index 4aaa48a0..e44c7377 100644
--- a/documentation/waap/waap-policies/waf-and-owasp-top-threats.md
+++ b/documentation/waap/waap-policies/waf-and-owasp-top-threats.md
@@ -20,13 +20,13 @@ You can review the WAF and OWASP top threats policy group and enable or disable
1\. Navigate to **WAAP** > **Domains**.
-
+
2\. Find the domain where you want to configure the policy group and click the domain name to open it.
3\. On the **Policies** page that opens, click **WAF and OWASP top threats** to expand the section and adjust the policies.
-
+
diff --git a/documentation/waap/waap-rules/custom-rules/create-and-manage-custom-rules.md b/documentation/waap/waap-rules/custom-rules/create-and-manage-custom-rules.md
index 02e5d1c8..890ca73f 100644
--- a/documentation/waap/waap-rules/custom-rules/create-and-manage-custom-rules.md
+++ b/documentation/waap/waap-rules/custom-rules/create-and-manage-custom-rules.md
@@ -48,7 +48,7 @@ To create a new WAAP rule:
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the needed domain and click its name to open it.
@@ -76,7 +76,7 @@ If you create multiple conditions, the rule will only trigger when all condition
7\. Next to **THEN**, select an action type: Allow, Block, Captcha, JavaScript Validation, Tag.
-
+
8\. Click **Save**.
@@ -112,7 +112,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with IP range conditions
@@ -132,7 +132,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with URL conditions
@@ -158,7 +158,7 @@ To create a rule:
7\. Click **Save**.
-
+
### Rules with user agent conditions
@@ -184,7 +184,7 @@ To create a rule:
7\. Click **Save**.
-
+
### Rules with header conditions
@@ -212,7 +212,7 @@ To create a rule:
8\. Click **Save**.
-
+
### Rules with header exists conditions
@@ -232,7 +232,7 @@ To create a rule:
8\. Click **Save**.
-
+
### Rules with HTTP method conditions
@@ -252,7 +252,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with file extension conditions
@@ -272,7 +272,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with content type conditions
@@ -292,7 +292,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with country conditions
@@ -312,7 +312,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with organization conditions
@@ -332,7 +332,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with owner types conditions
@@ -352,7 +352,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with session request count conditions
@@ -372,7 +372,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with tag conditions
@@ -398,7 +398,7 @@ To create a rule:
6\. Click **Save**.
-
+
### Rules with user-defined tag conditions
@@ -418,7 +418,7 @@ To create a rule:
6\. Click **Save**.
-
+
## Create custom rate limit rules
@@ -428,7 +428,7 @@ To create a rule:
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the needed domain and click its name to open it.
@@ -491,7 +491,7 @@ You can edit the rule name and description, modify its conditions and status, an
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the needed domain and click its name to open it.
@@ -501,7 +501,7 @@ You can edit the rule name and description, modify its conditions and status, an
5\. Click **Edit**.
-
+
6\. Adjust your rule as needed and then click **Save** to apply the changes.
@@ -509,7 +509,7 @@ You can edit the rule name and description, modify its conditions and status, an
1\. In the Gcore Customer Portal, navigate to **WAAP** > **Domains**.
-
+
2\. Find the needed domain and click its name to open it.
@@ -519,7 +519,7 @@ You can edit the rule name and description, modify its conditions and status, an
5\. Click **Delete**.
-
+
6\. Click **Confirm Delete** to verify your action.
diff --git a/documentation/waap/waap-rules/custom-rules/tag-rules.md b/documentation/waap/waap-rules/custom-rules/tag-rules.md
index cfc79cbb..5572c8f1 100644
--- a/documentation/waap/waap-rules/custom-rules/tag-rules.md
+++ b/documentation/waap/waap-rules/custom-rules/tag-rules.md
@@ -35,7 +35,7 @@ We offer a
+
## Tag generating rules
@@ -47,11 +47,11 @@ The following examples demonstrate how you can apply user-defined tags.
Let's say you run an online shop that requires users to log in before checking out an order. You can create a rule that will generate a custom tag called `validuser` if the request header named `set-cookie` contains a cookie named `mycookie`, which indicates that the user is logged in.
-
+
In this case, `validuser` will be your new user-defined tag that's now available for use in a tag-based rule.
-
+
diff --git a/documentation/waap/waap-rules/custom-rules/tag-rules/reserved-tags.md b/documentation/waap/waap-rules/custom-rules/tag-rules/reserved-tags.md
index e170653e..534dd2b7 100644
--- a/documentation/waap/waap-rules/custom-rules/tag-rules/reserved-tags.md
+++ b/documentation/waap/waap-rules/custom-rules/tag-rules/reserved-tags.md
@@ -51,11 +51,11 @@ You can also use a server signal that will serve as a unique identifier and can
For example, you can create the rule that looks for the X-Registered header, which designates registered users:
-
+
Alternatively, you can inject a header for logged-in users. WAAP will use this header to tag the request. After the WAAP generates such tags, they will be integrated with our security cloud and associated with the user session. All tags that indicate harmful behavior will be cleaned for the user.
-
+
## Inspect WAAP traffic
@@ -65,7 +65,7 @@ If you want to track certain traffic on the
+
When you add the monitor tag to a request, it won't affect WAAP's behavior. If the request is potentially dangerous, it will be blocked. The monitor tag only ensures that such requests are visible on the WAAP analytics page.
@@ -85,7 +85,7 @@ As an example, create a rule that will allow you to view analytics on monitored
6\. Click **Save** to create the rule.
-
+
All monitored requests will now be displayed on the WAAP analytics page.
@@ -103,7 +103,7 @@ To allow the activity of some automation services, create a custom rule with the
4\. In the **THEN** section, select the **Tag** action and choose **Ignored Automation**.
-
+
5\. Click **Save** to create the rule.
@@ -123,7 +123,7 @@ To identify login pages for the WAAP, create the following custom rule:
4\. In the **THEN** section, select the **Tag** action and choose **Login Page**.
-
+
5\. Click **Save** to create the rule.
@@ -155,7 +155,7 @@ Using the **legitimate activity** and **malicious activity** tags, you can categ
6\. In the **THEN** section, select the **Tag** action and choose **Legitimate Activity**.
-
+
7\. Click **Save**.
@@ -187,7 +187,7 @@ To detect denial of inventory, create the following rule:
5\. In the **THEN** section, select the **Tag** action and choose the **Cart Checkout** tag.
-
+
6\. Click **Save** to create the rule.
@@ -203,7 +203,7 @@ Similarly, create a rule that will check for the number of items added to the ca
5\. In the **THEN** section, select the **Tag** action and apply the **Item Added to Cart** tag to each request that matches the specified criteria.
-
+
6\. Click **Save** to create the rule.