Updated security reporting methods

[Maryna-f5]

Proposed changes

Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue using one of the supported keywords here in this description (not in the title of the PR).

Checklist

Before creating a PR, run through this checklist and mark each as complete:

• I have read the CONTRIBUTING document
• If applicable, I have added tests that prove my fix is effective or that my feature works
• If applicable, I have checked that any relevant tests pass after adding my changes

[Copilot]

Pull request overview

This PR updates the project’s security policy documentation to simplify how users report security vulnerabilities, directing reports to F5’s official vulnerability reporting page.

Changes:

• Replaces the previous multi-bullet reporting instructions with a single link-based reporting directive.

Comments suppressed due to low confidence (1)

SECURITY.md:21

• The vulnerability reporting sentence is split across two lines and omits the qualifier “security”, which makes the guidance read a bit incomplete. Consider making it a single, complete sentence and (while touching the block) remove the trailing whitespace on the following blank line.

Please report any vulnerabilities
[directly to F5](https://www.f5.com/services/support/report-a-vulnerability).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[route443]

LGTM

[VadimZhestikov]

Looks good