The CyberArk PAM self-hosted Vault is not typically installed on virtualized hardware but some cases make the scenario justified -- one of them being when standing up a lab environment. When using Hyper-V (and potentially other hypervisors), after ha...
PA AG
IT Engineer
Article says "The fix is straightforward. You simply need to change the two following Windows Defender Firewall-related registry keys from 0 to 1"
and it also says "Even CyberArk is uncertain about why this occurs, as when the Vault hardening process identifies that the Vaults are in AWS, CyberArk explicitly sets both keys to 1."
Can you please double check this once and confirm. Thanks