agemo proposes the creation of a dedicated “Security” watchable topic or tag, along with visual enhancements to the Admin Dashboard to better alert administrators about urgent security issues. The core argument is that current alerts, such as the red sad face icon, are easily ignored due to “alert fatigue,” and a more prominent mechanism is needed to reduce the window of vulnerability between a security patch release and an admin’s action.
Key suggestions include:
META Banner: A special colored “breaking ticker” banner on the forum itself to highlight urgent CVEs or Zero-Day exploits.
Dashboard Alerts: A “RED BOX” or prominent red banner in the Admin Dashboard for exceptional security updates, distinct from regular updates. This would include basic details like a countdown timer (e.g., “Patching Pending: 12 hours”) and direct links to advisories.
david suggests watching the release-notes tag, noting that every release currently includes security fixes. However, agemo argues that treating all security updates as routine is insufficient for critical threats. They emphasize the need to “force” critical update awareness to ensure admins act immediately, especially in an era where exceptional security events are becoming more common.
RGJ supports the idea of a dedicated security-notice watchable tag, noting that it would effectively cover not just Discourse core updates but also critical base image updates, which are increasingly frequent and constitute a significant part of the security landscape.
I thought I posted this suggestion weeks ago when things were getting hotter security wise, but I think I did not.
Suggestion - a Security specific high alert watchable topic/tag would be useful - what do others think?
I would also suggest to bolster this on META:
special coloured banner alert (lnews “breaking ticker” banner) reserved for urgent CVE / Zero Day security issues.
ADMIN Dashboard DISTRIBUTED Alerts
I understand there is the red sad face but easy to ignore, sometimes, a more in your face alert that has an exceptional status (is not seen often/rare) may be warranted considering the escalation of security concerns.
Red banner alert in admin dash or RED BOX the update advisory
Include basic info for e.g. Patching Pending 12 hours (set)
Thanks for that pointer. I have watched that tag. Thanks. I do update regularly and understand security fixes are always included.
I would suggest that this is still too ordinary in terms of the challenge at hand. I remember now it was was the PHP exploit news 30 days that kicked this all off, and it hasn’t stopped.
The way I see it is - you want critical alert to get to the admin before the hack does.
Maximising user base being appraised, ready and waiting status, so the update is grabbed asap.
Reducing the time vector period of attack as quickly as possible across discourse deployments.
In summary: Force Critical update watching via the dashboard more effectively
For the exceptional moments, that are becoming all too common.
I’d call these RED BOX updates.
exceptional CVE’s
critically urgent
The admin won’t see often but will grab attention beyond the smiley face status points or alert icon. Attention fatigue is a real thing. Novelty must remain novel to have its alert force remain potent.