How to exclude third-party security programs from EPM checks from Windows from (ALL) AD & EntraID Users/Groups?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to exclude third-party security programs from EPM checks from Windows from (ALL) AD & EntraID Users/Groups?

L1 Bithead

During excluding third-party security program directory from EPM checks, I want to apply the exclusion on “All” (any AD or EntraID users/groups), like the already existing 23 Windows default exclusions. See Attached Screenshot! 

 

As according to below info from CyberArk Documentation, adding the user or group is an Optional field: -(https://docs.cyberark.com/EPM/24.2.0/en/Content/Installation/InstallAgentsOnEndpointMachines.htm#Exc...).

 

There should Not be a need for EPM Admin Utility, nor using a special guidelines format like (Domain\*) or (Domain\Group*) or else.

 

The Expectations are that it should be one of the following or both points:

  1. The same like the already existing 23 Windows default exclusions ==>> “All” any AD or EntraID users/groups, as attached screenshot.
  2. Defining the group/user assignments exclusions from Windows should be ==>> Optional, not Required.

 

So, any insights or recommendations here?

 

 

Field_Content_versions_oct20__068Ht00000Ve05HIAR.png

1 accepted solution

Accepted Solutions

L1 Bithead

@Antonino Bambino​ @Anirban Saha​ @Niv Levi​ 

 

FYI, I just found out by coincidence that most probably my raised Bug is resolved (regardless that I received No response for this raised issue), as I was able to successfully configure the assignment now the CyberArk recommended for third-party security program directory exclusions from EPM checks. 

Field_Content_versions_oct20__068Ht00000Ve9qvIAB.png

View solution in original post

13 REPLIES 13

L6 Presenter

Hi @Ram Elbokhary​,

 

generally, the "All" option is recommended because mutual exclusion impacts the program level and not the user.

 

You can also find some guidance in the document EPM - Recommended Practice - Mutual Security Software Exclusions/DFSR

 

The only advice that comes to mind is what is already reported in the documentation: "By default, the list of paths in the Exclude files from policies parameters includes the paths of several popular third-party anti-virus programs. It is important to remove paths that do not exist on endpoints from this list so that malware and intruders cannot use them."

 

 

Nino

Hi @Antonino Bambino​ ,

Thanks for your input.

Yes I want to configure it "All" like for example the already existing 23 Windows default exclusions as attached screenshot above, but the problem is that it requires using a special guidelines format like (Domain\*) or (Domain\Group*) or else. So "All" cannot be configured.

However, another point, the user or group of the processes to exclude should be an Optional field not a Required as attached screenshot above.

Hi @Ram Elbokhary​,

 

I understand what you are referring to...

 

Field_Content_versions_oct20__068Ht00000Ve2OTIAZ.png 

The default values ​​do not contain any value in the "User/Group" field but if you change them they require a mandatory value.

 

I think (but I'm not sure) that it is necessary to fill in the field because the program to be excluded could run at user level and not computer level (for example it could be necessary to exclude something in /Appdata/. This is just my hypothesis but it is strange.

 

The only solution would be to add two equal rules but with different groups ( local .\* - domain\* ).

 

@Lauren Ellis​, Is it possible to have a clarification regarding what is reported in the documentation?

 

Nino

Hi @Antonino Bambino​ ,

Unfortunately even without changing them they still require it as a mandatory field (This is a BUG).

 

Kindly you can try open any of the already existing 23 Windows default exclusions and just click on "Done" without changing anything. It will ask you to fill the User/Group field as Mandatory not Optional.

 

So my expectations were that it should be one of the following or both points:

  1. The same like the already existing 23 Windows default exclusions ==>> “All” any AD or EntraID users/groups, as attached screenshot.
  2. Defining the group/user assignments exclusions from Windows should be ==>> Optional, not Required.

L4 Transporter

It accepts this solution - add two equal rules but with different groups ( local .\* - domain\* )

L4 Transporter

It accepts this solution - add two equal rules but with different groups ( local .\* - domain\* )

Hi @Anirban Saha​ ,

Thanks for your input.

Kindly do you know why it cannot be "All" like the already existing 23 Windows default exclusions?

And why the User/Group has a Mandatory field not Optional like what is stated on the Documentation below? https://docs.cyberark.com/EPM/24.2.0/en/Content/Installation/InstallAgentsOnEndpointMachines.htm#Exc...

068Ht00000Ve2v1IAB.jpg

L4 Transporter

Raise a case for that, and let us know the recommended solution (it seems like a bug)

L4 Transporter

Raise a case for that, and let us know the recommended solution (it seems like a bug)

I agree.

Case raised already and in progress with R&D.

Initial response received was that is very likely a Bug in the agent configuration.

Thank you for updating our community members!

Can you share the relevant Known Issue Article?

@Ram Elbokhary​ 

Hi @Niv Levi​ ,

Most welcome.

There is no relevant known issue article! I founded out this Bug and raised it, R&D should be working on it since last week.

I will keep all of us posted here, once I receive a resolution.

 

L1 Bithead

@Antonino Bambino​ @Anirban Saha​ @Niv Levi​ 

 

FYI, I just found out by coincidence that most probably my raised Bug is resolved (regardless that I received No response for this raised issue), as I was able to successfully configure the assignment now the CyberArk recommended for third-party security program directory exclusions from EPM checks. 

Field_Content_versions_oct20__068Ht00000Ve9qvIAB.png

  • 1 accepted solution
  • 575 Views
  • 13 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!