Does PTA require account discovery to be enabled to detect Unmanaged Privileged Accounts if it is already receiving EventIDs 4624, 4732 and 4720?

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Does PTA require account discovery to be enabled to detect Unmanaged Privileged Accounts if it is already receiving EventIDs 4624, 4732 and 4720?

L0 Member

We are receiving EventIDs 4624, 4732 and 4720 and able to parse it correctly on PTA. However we are not getting an Unmanaged Privileged Account alert for all cases that we were expecting:

 

  • WORKING - Non-Vaulted account (local or domain) added to a privileged group (e.g. Local Admin)
  • WORKING - Login of a Non-Vaulted Domain Admin account on a member server
  • NOT WORKING - Login of a Non-Vaulted Local/Domain account with Local Administrator privileges on a member server (we have an alert for added to group but not for the Windows Logon)

 

I would assume that if PTA gets the 4732 User Added to Group, it should be able to identify when that privileged user performs a Login and should also trigger an additional alert.

 

Since CyberArk also has the Account Discovery, do I need to enable that to CyberArk detect what unmanaged accounts/ local privileges I have on member servers, to trigger an alert for Windows Logon?

2 REPLIES 2

L7 Applicator

Hi @David Mestre​ 

 

The PTA doesn’t require Account Discovery to be enabled in order to detect Unmanaged Privileged Accounts, rather such accounts can be detected using the Logon Events from the target systems.

 

PTA won’t be tracking local admin account unless it’s part of local admin group and it relies on historical event correlation between 4624 ‘Logon’ and prior 4732 ‘Added to Privileged Group’ logs.

 

Remove and add the user to local admin group to see if an alert is generated.

 

In addition please verify that the PTA is receiving Event ID 4672 for local admin authentication.

 

Also check that the logs from DC’s member servers are reaching PTA.

 

Hope it helps!

 

 

 

 

L4 Transporter

Hi @David Mestre​ 

 

It seems that Malhar provided an answer to your question. Could you kindly let us know if this solution helped?

If so, please mark the answer as 'Select as Best' to assist other community members.

 

Thank you, Liad

  • 165 Views
  • 2 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!