- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
08-15-2024 11:02 AM
Currently, we have the Ransomware Protection policy in Detect Mode only. There are several applications and file types that have been categorized as Ransomware. How does EPM Categorize these as Ransomware? What is the process behind this?
08-15-2024 12:42 PM
https://docs.cyberark.com/epm/latest/en/Content/EPM/Server%20User%20Guide/PrivMgmnt-Ransomware-NewUI.htm#Overview
"This policy does not block or elevate unhandled applications in either mode." - If the policy does not elevate or block, but only blocks ransomeware attacks, how is it determined what is considered Ransomware? Just trying to understand that aspect of the policy. Thanks!
08-19-2024 06:34 AM
Hi @Martin Carlos ,
Restrict in the context of ransomware protection is referring to the prevention of the application performing a read/write on a filetype specified in the ransomware policy. So while the policy is not blocking the application, its blocking the applications ability to interact with files; which would therefore include an attempt to encrypt the file.
The policy itself only applies to unhandled applications, which is important to understand when deciding to enable the feature or not. You will need to have established your allow list first, ideally. Applications in the Authorized Applications group are considered handled, in the context of the ransomware policy.
So any application that is not handled by a policy or exists in the Authorized applications group (for example, one"caught" by a default policy) will trigger the ransomware policy, if it attempts to interact with a file type listed in the ransomware policy.
08-19-2024 08:17 AM
@Duncan Keir,
Unfortunately, only applications in the Authorized applications group are exempted from the ransomware policy, not those handled by other policies. Many of us have found and reported that coverage under other policies (e.g. an Advanced or Trust policy) does NOT exempt it from the Ransomware policy. So many of us have decided not to use this default ransomware policy because it doubles the work of the EPM administrator. You have to create a policy for the app for normal handling, then have to also add it to the Authorized applications group for exempting it from the ransomware policy. With a lot of applications in use, this creates a significant amount of extra work.
Therefore, I have created an Enhancement Request to correct this functionality. Please see and upvote:
ER - Excluding applications from Ransomware policy using existing policies (cyberark.com)
-rwm
08-20-2024 02:09 PM
Thank you. I have upvoted. This does become cumbersome with thousands of application files.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

