Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
21 changes: 21 additions & 0 deletions content/nap-waf/v5/admin-guide/compiler.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,27 @@ docker run \
-dump -bundle $(pwd)/compiled_policy.tgz
```
---
## Update App Protect Signatures
---
### Update Attack Signatures
---
### Update Threat Campaigns
---
### Update Bot Signatures
---
## Global Settings
The global settings allows configuration of the following items:
Expand Down
7 changes: 6 additions & 1 deletion content/nap-waf/v5/admin-guide/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,11 @@ NGINX App Protect WAF v5 supports a range of deployment scenarios to meet variou

NGINX App Protect WAF v5 enhances deployment speed through the pre-compilation of security policies and logging profiles into bundle files.

Use the [NGINX App Protect WAF Compiler]({{< relref "/nap-waf/v5/admin-guide/compiler.md" >}}) to transform security policies and logging profiles from JSON format into a consumable bundle files.
Use the [NGINX App Protect WAF Compiler]({{< ref "/nap-waf/v5/admin-guide/compiler.md" >}}) to transform security policies and logging profiles from JSON format into a consumable bundle files.

For signature updates, read the [Update App Protect Signatures]({{< ref "/nap-waf/v5/admin-guide/compiler.md#update-app-protect-signatures" >}}) section of the compiler documentation.

---

## Transitioning from NGINX App Protect WAF v4 to v5

Expand Down Expand Up @@ -97,6 +101,7 @@ We recommend that you deploy the NGINX App Protect WAF v5 in a staging environme
1. Restart the deployment if it has already been initiated. Additionally, restart NGINX if utilizing the VM + containers deployment type. After the migrations, check that the NGINX process is running in the NGINX error log and there are no issues.


---

## Troubleshooting and FAQs

Expand Down