Mitigating-Web-Shells VS spectre-meltdown-checker

The NSA provides publicly to everyone a GitHub Repository to mitigate back doors that other nation-state threat actors are using. Your statement "the sheer number of backdoors and exploits the NSA has and if revealed, would stop probably all malicious programs" implies that nation-state threat actors are using the same back doors, so why would they do this?

There is likely a Cobalt Strike BEACON acting as C2 now even if you've patched. I recommend full incident response mode, probably want to isolate the server. Run an integrity check against a known good config with WinDiff or NSA's dirChecker to find other anomolies. https://github.com/nsacyber/Mitigating-Web-Shells

I tried the latest SMC from https://github.com/speed47/spectre-meltdown-checker and all were in green. :-)

How is this project different spectre-meltdown-checker?

OpenBSD will disable all but the first thread on any Intel processor by default. I'm assuming that these models are too old to have microcode updates addressing the Spectre exploits (Meltdown, Foreshadow, Fallout, Zombieload, RIDL etc.), and disabling SMT/HT might be the most secure thing to do by default.

This script produces a good assessment of Spectre problems for a wide variety of CPUs. I know that they are difficult to exploit, and the mitigations are disabled by many because of their performance impact.

https://github.com/speed47/spectre-meltdown-checker

You can confirm the status of the mitigations using InSpectre for Windows, or Spectre & Meltdown Checker if you're on a unix based system.

You can run https://github.com/speed47/spectre-meltdown-checker

He's probably referring to the class of vulnerabilities checked by this script: https://github.com/speed47/spectre-meltdown-checker. It's not just Intel CPUs that were affected, AMD and ARM also have some vulnerabilities (I just ran it on an ARM v7 to see) although maybe not as many.

utilise microcode updates (should be by default, check)