Skip to content

Commit 5d08494

Browse files
committed
known issue
1 parent 39768b8 commit 5d08494

File tree

1 file changed

+11
-5
lines changed

1 file changed

+11
-5
lines changed

content/nginx-one/secure-your-fleet/secure.md renamed to content/nginx-one/secure-your-fleet/set-up-security-alerts.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -136,14 +136,20 @@ You've now set up F5 Distributed Cloud to send you alerts from NGINX One Console
136136

137137
## Known issues
138138

139-
When you set up an email alert that recognizes a problem, you'll see the alert in:
139+
When you set up an email alert for a problem, you'll see the alert in:
140140

141-
- The F5 Distributed Cloud Console, in **Audit Logs & Alerts**, under **Notifications > Alerts**.
142-
- An email with a subject line like **<number> Alert Requires Action**.
141+
- The F5 Distributed Cloud Console, under **Notifications > Alerts** in **Audit Logs & Alerts**
142+
- An email with a subject like **<number> Alert Requires Action**
143143

144-
As defined in our [Alert Reference](https://docs.cloud.f5.com/docs-v2/platform/reference/alerts-reference), after a certain period of time, you may also receive an "Alert Resolved" email.
144+
You may also get a follow-up email with the subject **Alert Resolved**.
145145

146-
For CVEs, the authoritative source is in **NGINX One**, under **Manage > Instances > <Instance hostname>.** See the list of CVEs on the dashboard details for that instance.
146+
> **Important:** Sometimes an **Alert Resolved** email is sent even though the issue is still active.
147+
To check the current status, go to the NGINX One Console.
148+
149+
For CVEs, the trusted source is:
150+
- **NGINX One Console > Manage > Instances > <Instance hostname>**
151+
152+
Open the instance dashboard to see the latest list of CVEs. Use the Console, not email, to confirm whether an issue is resolved.
147153

148154
## Summary
149155

0 commit comments

Comments
 (0)