Skip to content

featrue: F5 dos for nginx 4.9#1863

Open
rnitzan wants to merge 11 commits intomainfrom
nap-dos-4.9
Open

featrue: F5 dos for nginx 4.9#1863
rnitzan wants to merge 11 commits intomainfrom
nap-dos-4.9

Conversation

@rnitzan
Copy link
Copy Markdown
Contributor

@rnitzan rnitzan commented Apr 19, 2026

Proposed changes

F5 Dos for NGINX v4.9 release over NGINX Plus R37

  • Align with NGINX Plus R37
  • Adding RHEL 10 support
  • Adding Debian 13 support
  • Docker and k8s documentation update

Checklist

Before sharing this pull request, I completed the following checklist:

Footnotes

  1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content.

@github-actions github-actions Bot added documentation Improvements or additions to documentation product/dos Issues related to F5 DoS for NGINX labels Apr 19, 2026
@github-actions
Copy link
Copy Markdown

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/docs/1863/

rnitzan and others added 8 commits April 19, 2026 12:28
…ent (#1871)

* added Google site verification file for Google Search Console enablement

* moved to /static

---------

Co-authored-by: Lam Nguyen <la.nguyen@f5.com>
)

* Add instructions that shows a user how update an existing license

* Minor change to kubectl param

* Correct param
…r security monitoring (#1861)

* docs(nginx-one): improve security monitoring setup verification

-  Clarify where to place the secops_dashboard logging directives in the NGINX
  configuration and expand the verification flow into a concrete end-to-end
  check using the Security Dashboard Event Logs tab.

- Add labeled example test requests for common attack patterns (XSS, path
  traversal, SQL injection) so operators can generate sample security events
  while setting up the default blocking policy. Document that customized or
  transparent policies may alert instead of block.

* docs(nginx-one): add local security monitoring troubleshooting guide

- Add a new local data plane troubleshooting guide for NGINX One security
  monitoring to help customers diagnose why F5 WAF for NGINX security events
  do not appear in the dashboard after setup.

- The new guide covers four checks:
  - invalid secops_dashboard log profile errors in the embedded collector log
  - port 1514 ownership for local syslog delivery
  - presence of the generated security log pipeline in the collector config
  - optional debug exporter configuration for collector-side verification

  Also update the main security monitoring setup guide to improve verification,
  add labeled example attack requests for generating test events, and link to
  the new troubleshooting workflow. Update the section landing page so the new
  guide is discoverable from the security monitoring docs.

* Update content/nginx-one-console/waf-integration/waf-security-dashboard/local-dataplane-troubleshooting.md

Update as recommended

Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>

---------

Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>
@github-actions github-actions Bot added product/nic Issues related to NGINX Ingress Controller product/nginx-one-console Issues related to NGINX One Console labels Apr 23, 2026
@rnitzan rnitzan marked this pull request as ready for review April 23, 2026 11:03
@rnitzan rnitzan requested a review from a team as a code owner April 23, 2026 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation product/dos Issues related to F5 DoS for NGINX product/nginx-one-console Issues related to NGINX One Console product/nic Issues related to NGINX Ingress Controller

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants