Skyhigh Private Access 6.0.1 Release Notes

Last updated
Save as PDF

The Skyhigh Private Access 6.0.1 release includes feature enhancements and fixes for known issues.

Enhancements

Connector deployment

You can use Red Hat Enterprise Linux versions 8 as a virtual machine for deploying connectors. For more information, see Deploy Connectors.

Access Policy Rules

Supports creating nested policy rules (up to four levels) within a parent rule. For more information, see Configure Private Access Policy Rules.

New Points of Presence (POP)

Expanded the POP availability to Brazil as well.

Device Posture Profiles

Supports entering OS version (greater than, lesser than or the exact version number) for Windows-based devices. For more information, see Configure Device Posture Profiles.

Resolved issues

Reference	Description
PAC-1545	Instead of FQDN, the hostname of the VM (RHEL/ Ubuntu) is now used to update the POP name in the Skyhigh CASB.

Known issue

Reference Description

PAC-1363

Reference	Description
PAC-1363	When you see cwpp-pop-manager pod is in a CrashLoopBackOff state, then it is due to the DNS resolution errors. Workaround: Add the private DNS server to the cwpp-connector pod. Run `kubectl get pods -n` `cwpp`to get the name of the cwpp-connector pod. Copy the name of the cwpp-connector pod. Run `kubectl exec -it <cwpp-connector-podname> -n cwpp` `bash`to login to the cwpp-connector pod. Add the private DNS server to the pod. Edit `/etc/resolv.conf.` Add private DNS IP to the list of nameservers as `nameserver <DNS server IP>.` Exit the pod. List pods and verify `kubectl get pods -n cwpp` The pop-manager pod will be in the completed state in the next few minutes – within 5 minutes. Verify that the pop is displayed in the healthy status in the Skyhigh Security UI.

When you see cwpp-pop-manager pod is in a CrashLoopBackOff state, then it is due to the DNS resolution errors.
Workaround: Add the private DNS server to the cwpp-connector pod.

Run kubectl get pods -n cwppto get the name of the cwpp-connector pod.
Copy the name of the cwpp-connector pod.
Run kubectl exec -it <cwpp-connector-podname> -n cwpp bashto login to the cwpp-connector pod.
Add the private DNS server to the pod.
1. Edit /etc/resolv.conf.
2. Add private DNS IP to the list of nameservers as nameserver <DNS server IP>.
3. Exit the pod.
List pods and verify kubectl get pods -n cwpp
The pop-manager pod will be in the completed state in the next few minutes – within 5 minutes.
Verify that the pop is displayed in the healthy status in the Skyhigh Security UI.