Skip to content

Commit 1c6176c

Browse files
authored
feat: Brute force doc fixes (#181)
1 parent 96d8185 commit 1c6176c

File tree

2 files changed

+8
-4
lines changed

2 files changed

+8
-4
lines changed

content/nap-waf/v4/configuration-guide/configuration.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -660,7 +660,8 @@ systematic, username/password combinations to discover legitimate authentication
660660
To prevent brute force attacks, NGINX App Protect WAF monitors IP addresses, usernames, and the number of failed login attempts beyond a maximum threshold.
661661
When brute force patterns are detected, the NGINX App Protect WAF policy either trigger an alarm or block the attack if the failed
662662
login attempts reached a maximum threshold for a specific username or coming from a specific IP address.
663-
To enable brute force protection, at least one login page must be created.
663+
To enable brute force protection, at least one login page must be created.
664+
The login page entity is created separately and is not included in the brute force configuration block.
664665

665666
---
666667

@@ -722,7 +723,8 @@ Example1: A single brute force configuration is applied universally to all login
722723
}
723724
```
724725

725-
Example2: Different brute force configurations can be defined for individual login pages.
726+
Example2: Different brute force configurations can be defined for individual login pages.
727+
With each configuration referencing a specific login page.
726728
```json
727729
{
728730
"policy": {

content/nap-waf/v5/configuration-guide/configuration.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -798,7 +798,8 @@ systematic, username/password combinations to discover legitimate authentication
798798
To prevent brute force attacks, NGINX App Protect WAF monitors IP addresses, usernames, and the number of failed login attempts beyond a maximum threshold.
799799
When brute force patterns are detected, the NGINX App Protect WAF policy either trigger an alarm or block the attack if the failed
800800
login attempts reached a maximum threshold for a specific username or coming from a specific IP address.
801-
To enable brute force protection, at least one login page must be created.
801+
To enable brute force protection, at least one login page must be created.
802+
The login page entity is created separately and is not included in the brute force configuration block
802803

803804
---
804805

@@ -861,7 +862,8 @@ Example1: A single brute force configuration is applied universally to all login
861862
}
862863
```
863864

864-
Example2: Different brute force configurations can be defined for individual login pages.
865+
Example2: Different brute force configurations can be defined for individual login pages.
866+
With each configuration referencing a specific login page.
865867
```json
866868
{
867869
"policy": {

0 commit comments

Comments
 (0)