wg-securing-critical-projects VS itpol

1.https://www.privacyguides.org/basics/threat-modeling/ 2. https://www.privacyguides.org/linux-desktop/overview/ 3. https://www.privacyguides.org/basics/common-threats/#common-misconceptions 4. https://madaidans-insecurities.github.io/linux.html 5. Founder of Qubes 6. https://twitter.com/justinschuh/status/1190347400885329920 7. https://github.com/ossf/wg-securing-critical-projects/blob/main/presentations/The_state_of_the_Linux_kernel_security.pdf 8. https://grsecurity.net/10_years_of_linux_security.pdf 9. https://grsecurity.net/~spender/interview_notes.txt 10. https://twitter.com/grsecurity/status/1249850031357788162 11. https://seclists.org/oss-sec/2019/q2/165 12. https://arxiv.org/abs/2105.14565 13. https://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html 14. https://chromium.googlesource.com/chromiumos/docs/+/HEAD/sandboxing.md 15. https://docs.microsoft.com/en-us/windows/uwp/security/intro-to-secure-windows-app-development#41-windows-app-model

[3] https://github.com/ossf/wg-securing-critical-projects#how-we...

It's security-specific, but I appreciate that in the wake of Heartbleed, the industry really did take things seriously, from the Linux Foundation's Core Infrastructure Initiative (now OpenSSF's Securing Critical Projects Working Group) to Project Zero, the latter of which is still quite active testing everything from Windows filesystem "filter drivers" to Apple's ImageIO library to old versions of Acroread to GhostScript sandboxing.

I am not sure point you are making here? Are you saying linux is freaking stable, not even linux kernel developers gonna agree with you! (https://github.com/ossf/wg-securing-critical-projects/blob/main/presentations/The_state_of_the_Linux_kernel_security.pdf)

Not long before malware becomes more prevalent on Linux now that more people are using it. But Linux is not some magic bullet that stops all malware, you have to practice good opsec and harden your environment too. How to do this is outside the scope of my comment. If you are concerned though there are these resources:

󠁃󠁯󠁮󠁶󠁥󠁲󠁴󠀠󠁁󠁓󠁃󠁉󠁉󠀠󠁴󠁥󠁸󠁴󠀠󠁴󠁯󠀠󠁕󠁮󠁩󠁣󠁯󠁤󠁥󠀠󠁔󠁡󠁧󠁳󠀠󠁷󠁨󠁩󠁣󠁨󠀠󠁡󠁲󠁥󠀠󠁩󠁮󠁶󠁩󠁳󠁩󠁢󠁬󠁥󠀠󠁩󠁮󠀠󠁭󠁯󠁳󠁴󠀠󠁕󠁉󠀠󠁥󠁬󠁥󠁭󠁥󠁮󠁴󠁳󠀮󠁃󠁨󠁥󠁣󠁫󠀠󠁩󠁦󠀠󠁡󠀠󠁴󠁥󠁸󠁴󠀠󠁨󠁡󠁳󠀠󠁨󠁩󠁤󠁤󠁥󠁮󠀠󠁕󠁮󠁩󠁣󠁯󠁤󠁥󠀠󠁔󠁡󠁧󠁳󠀠󠁥󠁭󠁢󠁥󠁤󠁤󠁥󠁤󠀠󠁷󠁩󠁴󠁨󠀠󠁄󠁥󠁣󠁯󠁤󠁥󠀮󠀠https://github.com/lfit/itpol/blob/master/linux-workstation-...

https://madaidans-insecurities.github.io/linux.html

Between the Arch wiki on Security and this link alone, there's enough inspiration to harden some stuff.

Linux hardening checklist Workstation security checklist

for workstation hardening, check out -- https://github.com/lfit/itpol/blob/master/linux-workstation-security.md

now, if you want a hardened workstation you should check out this -- https://github.com/lfit/itpol/blob/master/linux-workstation-security.md -- mind you, some of the data on here, like browsers and extensions/etc are out-dated but the general premise is pretty solid.

The Linux workstation security checklist would be a better recommendation. While also not targeted at home users, it gives at least some priority levels.