- 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.
01-26-2021 09:57 AM
Hi everyone, I'm having the following issue. I've enabled the Commands Access Control on both connection components (PSM-SSH and PSMP-SSH). When I connect to a target using the PSM-SSH connection component on the PVWA the commands access control works perfect. However when I connect using the PSMP-SSH (using Putty from my machine) the commands are not being blocked. Has anyone encounter this issue?
I've checked and followed the instructions on how to set up this feature, but for some reason it's not working on PSMP-SSH. Any advice?
02-25-2022 03:29 PM
Hi gnoguez, I ended up opening a support case. It seems the regex expression needs to be exactly as specified in the docs. This is the response from the case I opened.
"Hello Xavier, Can you provide a screenshot of the ACL rule, for the previous test running "passwd root" with PSM-SSH and PSMP-SSH. I believe I found the issue.
In my lab I was able to reproduce this with ACL set up as a "black list" Allow All: .* DENY id .*
PSMP-SSH
id - succeeds
id user - succeeds
id<space> - succeeds
PSM-SSH
id -Succeeds
id user - Fails: "you are not authorized."
It appears that the regex for "id .*" as a Deny Rule, doesn't follow the same as an Allow Rule. If I set the Deny Rule up as per the documentation example: (.*/)?id.* This is successfully able to DENY on both PSMP-SSH and PSM-SSH. https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Configuring-SSH-Comman... "Apply a black-list of SSH Commands" I believe you will need to change your DENY rules to use the syntax as documented. (.*/)?passwd.* Please let me know your results, Regards, Aaron"
It worked for me. Hope it helps you.
Regards.
01-26-2021 08:43 PM
Double check your configuration:
Regards
02-25-2022 12:02 PM
Hello @Xavier Orozco De La Huerta
could you solve it?
Im getting the same behaviour but the Capability is already enabled on the PSMP-SSH component.
Regards
02-25-2022 03:29 PM
Hi gnoguez, I ended up opening a support case. It seems the regex expression needs to be exactly as specified in the docs. This is the response from the case I opened.
"Hello Xavier, Can you provide a screenshot of the ACL rule, for the previous test running "passwd root" with PSM-SSH and PSMP-SSH. I believe I found the issue.
In my lab I was able to reproduce this with ACL set up as a "black list" Allow All: .* DENY id .*
PSMP-SSH
id - succeeds
id user - succeeds
id<space> - succeeds
PSM-SSH
id -Succeeds
id user - Fails: "you are not authorized."
It appears that the regex for "id .*" as a Deny Rule, doesn't follow the same as an Allow Rule. If I set the Deny Rule up as per the documentation example: (.*/)?id.* This is successfully able to DENY on both PSMP-SSH and PSM-SSH. https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Configuring-SSH-Comman... "Apply a black-list of SSH Commands" I believe you will need to change your DENY rules to use the syntax as documented. (.*/)?passwd.* Please let me know your results, Regards, Aaron"
It worked for me. Hope it helps you.
Regards.
02-25-2022 04:33 PM
Yeah, it works.
Thank you so much.
Regards
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!

