-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion] Add an FAQ to explain the default templates and recommended configurations #213
Comments
Hi @dennyamarojr, Can you see whether our official docs answer your questions:
|
That's a good documentation and I checked the informations but I couldn't find which Policy Rules in the Table 1. Windows Defender Application Control policy - policy rule options is recommended to use. To explain my point, for example I fully managed device as described in the 3 link in common scenarios and for Lightly manage device is This could be useful for beginners and also if the template is described which one is recommended to use for the scenario, since in the link 2, we just have the description for templates but in the third link I couldn't see which templates is used for each scenario. |
For a fully managed system:
For lightly managed system
|
Hi,
This is my second issue here, and this time I come to make an suggestion to WDAC Toolkit. I see that have a lot of templates available and also in the WDAC Policy Wizard has some templates, Default windows mode, Allow Microsoft mode and Signed and reputable mode. Which is good templates to use as a start point, but we also have the templates of WDAC in windows, and this could have some trouble for beginners to decide which one is the best and what is the best for the environment of the user. Policy rules is another one that we may need some information, to decide which are the best rules for enforced and some explanation of each one (maybe have in the official documentation) , and also tell which are the rules to troubleshoot any issues in the environment.
The text was updated successfully, but these errors were encountered: