Broker bypass controls as a preventative control

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

Broker bypass controls as a preventative control

L4 Transporter

I am curious about methods used to block logins that bypass the PSM. Let's assume we are talking about Windows target servers, which are onboarded to CyberArk and admins are expected to use PSM to access them. Further, lets assume a bad actor has a username and password with admin privileges on the target server (eg a backdoor account created by a server admin)

 

Clearly PTA can help detect a login that bypasses PSM, but that's a detective control not preventative.

 

IP based firewalls could help with this, blocking access to the target server except from the PSM. But in a complex network it can be very hard to reliably configure the firewalls.

 

What other controls can be used to prevent someone logging in to a target Windows server and bypassing PSM? For instance is there something that can be done with mutual certificate validation?

9 REPLIES 9

L1 Bithead

Hi Jon, I believe you can achieve this through

Configure Windows Firewall Rules on the target servers to allow RDP access only from the PSM server.

Use Local Security Policy (secpol.msc) or Group Policy (GPO) to enforce "Deny Logon Locally" and "Deny Logon Through RDP" for all admin accounts except the PSM service account.

Hi Jon, I believe you can achieve this through

Configure Windows Firewall Rules on the target servers to allow RDP access only from the PSM server.

Use Local Security Policy (secpol.msc) or Group Policy (GPO) to enforce "Deny Logon Locally" and "Deny Logon Through RDP" for all admin accounts except the PSM service account.

Hi Jon, I believe you can achieve this through

Configure Windows Firewall Rules on the target servers to allow RDP access only from the PSM server.

Use Local Security Policy (secpol.msc) or Group Policy (GPO) to enforce "Deny Logon Locally" and "Deny Logon Through RDP" for all admin accounts except the PSM service account.

thanks for your answer @Suresh Vishwakarma​  I am not relying on firewalls as a control in this scenario, as I mention in the question.

 

The Deny Logon settings will block that particular user from logging in to be sure, but it doesn't discriminate whether the login attempt was via PSM or not, so this doesn't fully answer me. A partial solution is indeed to block logon for any account that isn't managed by CyberArk, however there is no way for the OS to validate whether or not an account is managed by CyberArk. Disabling the account has a similar effect.

you're right, Windows Deny Logon policies don’t differentiate between logins through CyberArk PSM and direct logins, and the OS itself isn’t aware of whether access is coming from PSM.

I think better approach is to use controls that enforce PSM-only access by integrating CyberArk with Windows security mechanisms.

 

Here's how it can be done:

  • Restrict Logins to CyberArk-Managed Accounts – Configure Windows policies so that only accounts managed by CyberArk can log in.
  • Enforce Kerberos Authentication – Block NTLM and ensure that privileged access happens only through PSM via Kerberos.

you're right, Windows Deny Logon policies don’t differentiate between logins through CyberArk PSM and direct logins, and the OS itself isn’t aware of whether access is coming from PSM.

I think better approach is to use controls that enforce PSM-only access by integrating CyberArk with Windows security mechanisms.

 

Here's how it can be done:

  • Restrict Logins to CyberArk-Managed Accounts – Configure Windows policies so that only accounts managed by CyberArk can log in.
  • Enforce Kerberos Authentication – Block NTLM and ensure that privileged access happens only through PSM via Kerberos.

you're right, Windows Deny Logon policies don’t differentiate between logins through CyberArk PSM and direct logins, and the OS itself isn’t aware of whether access is coming from PSM.

I think better approach is to use controls that enforce PSM-only access by integrating CyberArk with Windows security mechanisms.

 

Here's how it can be done:

  • Restrict Logins to CyberArk-Managed Accounts – Configure Windows policies so that only accounts managed by CyberArk can log in.
  • Enforce Kerberos Authentication – Block NTLM and ensure that privileged access happens only through PSM via Kerberos.

L4 Transporter

Hi @Jon Musker​ 

 

It seems that @Suresh Vishwakarma​ 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

hm, I appreciate the responses @Suresh Vishwakarma​ .

 

Restricting the login accounts is useful, but it doesn't lock me to access from PSM. A malicious user who gained knowledge of a CyberArk-managed account password could login from any machine.

 

Regards your second suggestion, I haven't figured out how I would use Kerberos to restict RDP access to only come from PSM servers.

  • 180 Views
  • 9 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!