The only issue I have is that the firewall is setup as Default-allow, and create rules for malicious processes. This would be an exercise in futility because there are thousands if not millions of malicious processes in existence. Is it not better to setup as Default-deny, and create rules for safe applications that require outbound comms? This way nothing is allowed, except for those applications/processes installed on the device that are deemed safe. So much easier to manage.
That said, Defender firewall without some sort of functionality interface such as Windows Firewall Control is a cumbersome joke to configure. Also, it has a terrible limitation in that it can't handle wildcards in path rules.
The Defender firewall being terminated is concerning, especially as it seems, correct me if I'm wrong, the DANGER(.)exe was launched without elevated privileges. But @oldschool has sound advice as usual Somehow preventative measures must be put in place to prevent the malicious process from launching in the first place.
Please, allow me to paste the same comment I made to your other similar post:
In general, I totally agree with your comment.
But comms is just the tip of the iceberg. If the device is infected, firewall can do almost nothing to solve the problem. Here a real modern antivirus/malware is needed.
Also, take the example of Comodo, an abandonware since 2017 + full of unfixed bugs... by default, Comodo Firewall allows comms for "safe files", where "safe files" is just an arbitrary list made by Comodo (last update 15 years ago). Under this category you will find SYSTEM, Windows Services, SVCHOST etc etc etc... I repeat, all allowed by Comodo default. And in real life, it's possible to find thousand of cases where virus/malware hijacked all these "safe files" allowed by Comodo, and managed to have comms. And considering that Comodo can't customize fiirewall rules for Windows Services, Svchost etc, "default deny" doesn't work here.
Again, I agree with you, I'm just complementing by saying that "default deny" is not the panacea, not for files, nor for comms. And average users have zero chance to deal with "default deny" strategies.