Skip to content

waf/ update security update doc #2033

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

Open
dkleinF5 wants to merge 1 commit into
base: main
Choose a base branch
from
+15 −4
Open

waf/ update security update doc #2033

Show file tree
Hide file tree
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
13 changes: 12 additions & 1 deletion content/waf/install/update-signatures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,4 +32,15 @@ They will be named something in the following list:
- `app-protect-bot-signatures`
- `app-protect-threat-campaigns`

You can update these packages independently of the core F5 WAF for NGINX packages, ensuring you always have the latest signatures.
You can update these packages independently of the core F5 WAF for NGINX packages, ensuring you always have the latest signatures.

## Apply the updated signatures

Updated signatures don't take effect until you reload NGINX. Until you reload, F5 WAF for NGINX keeps running the previous signatures.
Copy link
Copy Markdown
Contributor

@JTorreG JTorreG Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this paragraph and the next could be improved. The first 2 sentences are a bit redundant


A reload is enough. You don't need to restart NGINX.

To apply the updated signatures, run one of the following commands:

- On all platforms: `nginx -s reload`
- On systemd-based platforms (Amazon Linux, Debian, Oracle Linux, RHEL, Rocky Linux, Ubuntu): `sudo systemctl reload nginx`
6 changes: 3 additions & 3 deletions content/waf/install/virtual-environment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -427,10 +427,10 @@ server {

{{< /tabs >}}

Once you have updated your configuration files, you can reload NGINX to apply the changes. You have two options depending on your environment:
Once you have updated your configuration files, reload NGINX to apply the changes:

- `nginx -s reload`
- `sudo systemctl reload nginx`
- On all platforms: `nginx -s reload`
Copy link
Copy Markdown
Contributor

@JTorreG JTorreG Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Al platforms or all except the ones in the next step?

For the ones in the next step are both commands necessary?

- On systemd-based platforms (Amazon Linux, Debian, Oracle Linux, RHEL, Rocky Linux, Ubuntu): `sudo systemctl reload nginx`

## Post-installation checks

Expand Down
Loading