Don't Sleep on Blackberry's Cylance Protect!
Use Cases and Deployment Scope
We use this as one of many pieces of security software to protect all of our endpoints (be it laptops or servers (both physical and virtual)). There are multiple "policies" that we have in place, some completely block PowerShell from running on a specific users' machine while another one allows it for specific people based on their job functions.
Pros
- Blocks PowerShell Scripting (when in a specific policy)
- Blocks unwanted programs from running
- Is able to determine what is used on a regular basis and allows it to run safely.
Cons
- I wish it would be easier to safelist things based on install location (have a somewhat recurring issue with PhotoShop getting blocked after an update)
- It can sometimes be a little over protective (which I guess isn't necessarily a bad thing)
Likelihood to Recommend
The policies that you make is where it's key. The "less you let people do, the better it will be" so to speak. So if you really clamp down on a policy and don't let people do specific things, then it'll be better for you. It also helps to protect the "not so tech savvy" people as well.
Basically the same thing as above, if you have users that need more flexibility, on occasion the policies might come into play and interfere if you're not careful.
