From 6cb61097d1850bddc4c72e50328d9deac6aacf88 Mon Sep 17 00:00:00 2001 From: Venktesh Shivam Patel Date: Mon, 12 Aug 2024 16:53:42 +0100 Subject: [PATCH] update based on review comments Co-authored-by: Jon Torre <78599298+Jcahilltorre@users.noreply.github.com> Signed-off-by: Venktesh Shivam Patel --- .../integrations/app-protect-waf-v5/installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/installation/integrations/app-protect-waf-v5/installation.md b/docs/content/installation/integrations/app-protect-waf-v5/installation.md index 05f6826b87..71a477feb4 100644 --- a/docs/content/installation/integrations/app-protect-waf-v5/installation.md +++ b/docs/content/installation/integrations/app-protect-waf-v5/installation.md @@ -357,4 +357,4 @@ If you prefer not to build your own NGINX Ingress Controller image, you can use | 3.6.2 | 32_5.48 | 5.2.0 | 5.2.0 | {{% /bootstrap-table %}} -{{< note >}} Recompilation of the WAF policies upon every NIC release is recommended in order to get updates to features like threat campaigns and signature updates etc.{{< /note >}} +{{< note >}} F5 recommends to re-compile your NGINX AppProtect WAF Policy Bundles with each release of NGINX Ingress Controller. This will ensure your Policies remain compatible and are compiled with the latest Attack Signatures, Bot Signatures, and Threat Campaigns.{{< /note >}}