Skip to content

Brute force doc fixes #181

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

Merged
merged 4 commits into from
Feb 10, 2025
Merged

Brute force doc fixes #181

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
086b7f4
fix: some comments from PM
ohad-perets Feb 10, 2025
2a3bc3c
fix: some comments from PM
ohad-perets Feb 10, 2025
76d0b52
Merge branch 'main' into brute_force_updates
ADubhlaoich Feb 10, 2025
32d1c9a
Merge branch 'main' into brute_force_updates
ADubhlaoich Feb 10, 2025
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
6 changes: 4 additions & 2 deletions content/nap-waf/v4/configuration-guide/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -660,7 +660,8 @@ systematic, username/password combinations to discover legitimate authentication
To prevent brute force attacks, NGINX App Protect WAF monitors IP addresses, usernames, and the number of failed login attempts beyond a maximum threshold.
When brute force patterns are detected, the NGINX App Protect WAF policy either trigger an alarm or block the attack if the failed
login attempts reached a maximum threshold for a specific username or coming from a specific IP address.
To enable brute force protection, at least one login page must be created.
To enable brute force protection, at least one login page must be created.
The login page entity is created separately and is not included in the brute force configuration block.

---

Expand Down Expand Up @@ -722,7 +723,8 @@ Example1: A single brute force configuration is applied universally to all login
}
```

Example2: Different brute force configurations can be defined for individual login pages.
Example2: Different brute force configurations can be defined for individual login pages.
With each configuration referencing a specific login page.
```json
{
"policy": {
Expand Down
6 changes: 4 additions & 2 deletions content/nap-waf/v5/configuration-guide/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -798,7 +798,8 @@ systematic, username/password combinations to discover legitimate authentication
To prevent brute force attacks, NGINX App Protect WAF monitors IP addresses, usernames, and the number of failed login attempts beyond a maximum threshold.
When brute force patterns are detected, the NGINX App Protect WAF policy either trigger an alarm or block the attack if the failed
login attempts reached a maximum threshold for a specific username or coming from a specific IP address.
To enable brute force protection, at least one login page must be created.
To enable brute force protection, at least one login page must be created.
The login page entity is created separately and is not included in the brute force configuration block

---

Expand Down Expand Up @@ -861,7 +862,8 @@ Example1: A single brute force configuration is applied universally to all login
}
```

Example2: Different brute force configurations can be defined for individual login pages.
Example2: Different brute force configurations can be defined for individual login pages.
With each configuration referencing a specific login page.
```json
{
"policy": {
Expand Down
Loading