N1C WAF Security Dashboard Release

[sylwang]

Proposed changes

Checklist

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

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

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]

✅ Deploy Preview will be available once build job completes!

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

---

[mjang]

Big picture question: Information architecture. Should we have separate sections for

• Secure with F5 WAF for NGINX
• F5 WAF for NGINX security monitoring

My feeling: no, but I'm open to arguments on this. If I'm correct:

• I'd eliminate F5 WAF for NGINX security monitoring (and the Overview page)
• I'd include "Set up security monitoring" as a subpage of "Secure with F5 WAF for NGINX"

Question: is there duplication between "Manage log profiles" and "Default log profile"? I haven't analyzed in detail. My gut; we don't need both pages.

self-dismissal, based on Jon's work