A user at the beginning of this thread asked about recourse usage but did not get an answer.
Here is a truth about creating videos by testing security software. If you were doing this and found a program that stopped everything in its tracks, you might not promote it because further videos might become useless and the what fun would that be/
danb has no answer, other than to take shots at products designed for enterprise\not consumers and those that use them, and then state they are flawed with no basis
he has thiis weird obsession with appguard (and srp - andy ful) and rails against protection models that have been developed and vetted over decades by the nsa, the nist, the dod, microsoft, linux groups - and tell them they're doing it all wrong - that his dynamic security profiles are the answer
next he uses completely flawed opinion polls as evidence that his product is superior, meanwhile the poll respondents have no idea what they are looking at in the list of products
voodooshield would fail miserably if it were tested on the basis of enterprise requirements and policies, such as integration with active directory\group policy\different security policies per ip address or users\ensuring defined groups only have access to programs per the applicable standard, of course products such as appguard and wdac already have all this integration because they are desinged for windows enterprise admins\not home users
in enterprise, scripts must be run sometimes with admin privileges, other times with standard user privileges, sometimes with delegation, uac must be blocked except for certain admins, such a policy needs to be enforced by access protocol (the policy will block all access except when, for example, powershell remote tunneled through SSH and JEA used), ip address, group membership, a product like appgaurd works within these context
this and a whole lot more policies can be implemented and distrbuted witha click of a button across hundreds of thousands of endpoints
any company that must meet nist 800-53 must apply the principle of least funcationality defined as blocking globally and permanently disabling lolbins, disabling services, disabling ports, disabling user acces to control panel, and so on
i could write a whole book but you get the point, i'm not saying anything you don't already know
try harder danb you have a lot of catching up to do