A few weeks ago, we published a blog
on how to optimize PowerBroker for Windows
rules to mitigate the threat of ransomware. We received great feedback on the success of the sample rules and also a few recommendations to fine tune them for unique environments. To that end, we have compiled the feedback into this blog so you can follow best practice recommendations to ensure you are not a victim. Check out the best practices below:
- Some applications, especially ones that are geographically based, are not digitally signed (yet) by their manufacturers and they are executed from %APPDATA% (C:\Users\*\AppData\Local\ or C:\Users\*\AppData\LocalLow\). While creating a simple wildcard passive Path Rule allows them to execute, it also can allow ransomware like TeslaCrypt to execute as well. The best recommendation is to identify each of the applications that need to execute from these locations and create Hash Rules. Hopefully, your environment only has a couple of applications that fall into this category, and we strongly recommend contacting each of these vendors and request they begin digitally signing their applications. Then, a simple Publisher can properly solve the execution issue with whatever privileges are needed.
- To ensure everything is working correctly, the Deny Rule should always be the last in the rule list. All passive and privilege rules should process first and then anything that has not matched will be denied.
- If there is a desire to block / deny applications before the last Deny Rule, consider applying rules to specific applications, paths, and temporary directories (i.e. c:\ or C:\windows\temp\).
- To ensure the best user experience, keep the rule base small, around 50 rules maximum. This will keep the performance optimized with minimal or no impact to the end user.
- All acceptable applications should have passive rules by Publisher (preferred and best practice) or a global path and subdirectory. Remember to include child applications when necessary. For example, “C:\Program Files\Custom Applications\*” as a passive rule with all children.
- If multiple applications that are unsigned and in various directories are installed, rules will be needed for each. Standardizing on a trusted directory structure would help minimize the number of rules and places malware can be deposited and executed on the system.
[caption id="attachment_17216" align="alignnone" width="728"]PowerBroker for Windows - sample rule base.
Our solutions can mitigate much more than least privilege
risks and a few simple rules can defend against the most common ransomware and exploit toolkits. If you have any other questions or recommendations for optimizing the rule base, please feel free to contact BeyondTrust Technical Support
or your Account Manager