I agree with
@anupritaisno1 on almost everything.
But
@anupritaisno1 lost me when he suggested that SRP is a solution to the issue, considering that SRP is easily bypassed, not user-friendly, runs in user-mode, is a 20 year old deprecated tech and offers zero context on each event, so no one knows if something should actually be blocked or not.
This is not a bash on H_C, and once the WDAC version of H_C is available, it will solve all of the above issues.
It is probably best to equate cybersecurity with home security and to create an analogy. For example, with allow-by-default, you leave the doors and windows unlocked and let random people roam your house, and you only kick them out if they are drunk, rowdy and break stuff. With deny-by-default you lock your doors and windows. The only caveat is that you have to figure out how to make it user-friendly for the masses.
It is important to mention that a lot of products rely HEAVILY on digital signatures, which I believe is crazy. And a lot of times they rely solely on the signer’s name, which is even more insane. They suggest that their product is zero trust, but yet they allow any item that matches a signer’s name. For example… if a new process matches a signer’s name, then allow that file, and if not sandbox it. What people do not seem to understand is that a determination has been made at this point. That is not zero trust.
And you wonder why there is a malware epidemic. I have seen people say “yeah, product x blocks less than VS”, without realizing that it is not a correct comparison when product x allows by the signers name, and VS is set to ON. If you want to correct comparison, put VS on AutoPilot.
Anyway, I could go on for days about all of this. Ultimately the real problem is that cybersecurity “professionals” love to put on a suit and play cops and robbers and make tons of money in the process. Or they like to see who can get more likes on their tweets and this whole circus is turned into a popularity contest, and the end result is that malware just simply slips by.
And all along, the cybersecurity industry knew the only thing they had to do to solve this problem was to find a way to make TRUE deny-by-default user-friendly enough for the masses.