-
|
Hello, First off, I would like to say thank you for creating the WDACConfig module, it is super helpful and easy to use! Unfortunately, I am experiencing this issue where the supplemental policy created through MDE Advanced Hunting is using only hashes for allow rules instead of Publisher type even though the files are signed. I have also watched your YouTube video on how to use WDACConfig module with Microsoft Defender for Endpoint (MDE) Advanced Hunting results to create Application Control policies and followed the steps as applicable. Is there any configuration I need to adjust or additional steps I should take to ensure all publisher fields are included when parsing from MDE Advanced Hunting events? Thank you for your support! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 12 replies
-
|
Hi, The module first tries to create FilePublisher, if necessary details aren't available then attempts to create Publisher and lastly tries Hash level rules. If the CSV contains file's signatures (Publisher Name, Publisher TBS Hash, Issuer Name, Issuer TBS Hash) then Publisher level should be used. |
Beta Was this translation helpful? Give feedback.





Hi, when i designed that function, i made it to use the most secure levels as much as possible. So it first tries to use FilePublisher level, if the logs can't satisfy the requirements for it, then it falls back to Publisher level, if that can't be satisfied it tries to use LeafCertificate, and finally it will create Hash rules.
I'm beginning to realize people (including you) want to use Publisher level primarily, especially in enterprise environments, so i will offer level selection in the command. The logics are already there, just need to take care of some minor technicalities to make it happen. Next version of the WDACConfig module will most likely offer it.