Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hardening check for PSM - Error messages #86

Closed
tovd600 opened this issue Dec 1, 2021 · 1 comment · Fixed by #87
Closed

Hardening check for PSM - Error messages #86

tovd600 opened this issue Dec 1, 2021 · 1 comment · Fixed by #87

Comments

@tovd600
Copy link

tovd600 commented Dec 1, 2021

Hello team. We are facing some messages when running the health chech on PSMs. Can you please advise on below items?

  1. Why do we need to grant FullControl rights as described here? Is it really necessary?

image

  1. Errors during the execution, should we do something when it happens?

image
image
image

Many thanks

@AssafMiron AssafMiron mentioned this issue Dec 2, 2021
2 tasks
@AssafMiron
Copy link
Contributor

Hello @tovd600 ,

Thanks for approaching with this issue :)

Regarding the first item, we have improved the logging and messages in the report to include also the access type
In this specific case the hardening requirement is to Deny FullControl
You can see the requirement here:
https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/Security/PSM-hardening-configuration.htm?TocPath=Security%7C_____3#:~:text=Adds%20an%20access%20rule%20for%20PSMConnect%2C%20PSMAdminConnect%20and%20PSMShadowUsers%20to%20Deny%20FullControl%20for%20the%20specified%20path

This is now solved and updated in #87

Regarding the second item, for issues like these the best is to review the logs to see more details on the error
or run the script with verbose logging (just run the script with "-Debug -Verbose" switches at the Powershell command
That would add more insights into the log files so you could better understand what happened

Hope this helps,
Regards,
Assaf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants