Reply to thread

Message

<blockquote data-quote="ForgottenSeer 98186" data-source="post: 1026213">I was talking about Windows Home - as in typical, non-security geek users. I was also talking about a customized policy - and not the default Microsoft\Windows policy the wizzard creates.Of course you can import it with a powershell script, but like I said, how many users are going to do that? How many are going to read walls of text to learn how to use WDAC? How many people are going to exert the effort to eliminate all the things covered in the Microsoft learn walls of text that are not necessary? How many are going to import the WDAC policy, set it to audit mode, let it run, and then review logs to customize it? Very, very few. That&#039;s who.Everything I stated in my prior post is an irrefutable fact.If WDAC is so easy to use and popular, then why are you the only active member here at MT using and promoting it? Well, SpyNetGirl was promoting it too, but she&#039;s gone. She changed her GitHub to non-public.In your reply, you are deliberately leaving out steps that are required in an effort to make WDAC seems trivially simple. There are more steps than simply &quot;importing&quot; a .cip file to customize and then enforce a policy. Most of which average users want no parts of any of it.Where is your guide? Where is your GUI to make WDAC acceptable to the vast majority of home users?</blockquote>

[QUOTE="ForgottenSeer 98186, post: 1026213"] I was talking about Windows Home - as in typical, non-security geek users. I was also talking about a customized policy - and not the default Microsoft\Windows policy the wizzard creates. Of course you can import it with a powershell script, but like I said, how many users are going to do that? How many are going to read walls of text to learn how to use WDAC? How many people are going to exert the effort to eliminate all the things covered in the Microsoft learn walls of text that are not necessary? How many are going to import the WDAC policy, set it to audit mode, let it run, and then review logs to customize it? Very, very few. That's who. Everything I stated in my prior post is an irrefutable fact. If WDAC is so easy to use and popular, then why are you the only active member here at MT using and promoting it? Well, SpyNetGirl was promoting it too, but she's gone. She changed her GitHub to non-public. In your reply, you are deliberately leaving out steps that are required in an effort to make WDAC seems trivially simple. There are more steps than simply "importing" a .cip file to customize and then enforce a policy. Most of which average users want no parts of any of it. Where is your guide? Where is your GUI to make WDAC acceptable to the vast majority of home users? [/QUOTE]

Verification