Answer
Pull the actual Helm chart and read the underlying template directly, since that's the real source of truth for what a Helm-driven parameter does: from a machine with the IFS Cloud JFrog repo already configured, run helm repo update, then helm pull ifscloud/ifs-cloud --untar, and look in the untarred chart's charts/ifscore/templates/network.yaml — that file contains the conditional block controlled by networkpolicy.enabled, defining the actual Kubernetes NetworkPolicy resources (which restrict ingress/egress traffic, ports, protocols, etc. per Kubernetes' own NetworkPolicy semantics) it creates when enabled. Once you know what's defined, kubectl get networkpolicy -A lists the live NetworkPolicy resources in your cluster, and kubectl get networkpolicy/<name> -n <namespace> -o yaml shows the exact rules applied, letting you confirm precisely what's being restricted rather than relying on the parameter's one-line documentation.