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.
The trouble is that there are so many security issues in all software products these days, that it’s hard to distinguish them.
This week’s NGINX and Ruby vulnerabilities seem bad, and have received a lot of press attention, but AFAIK there are no published proofs-of-concept outside of lab environments (yet). There are many other recent vulnerabilities in Discourse and other packages which have presented far more risk for Discourse communities.
When we update something in the base image which is known to be critical for Discourse (e.g. the libheic updates a few weeks ago), we aim to cut a core version around the same time, so it’s all covered through the same notification system. Most people don’t come to Meta, so releases.discourse.org, the admin dashboard, and the automatic notification emails are the main way we distribute that information.
My advice would be that everyone should be applying every update as soon as possible after they receive a notification. Every one should be considered critical. The speed of vulnerability discovery and potential exploitation is so fast these days - waiting is not an option.