diff --git a/docs/advanced/cluster-pod-security-standard.md b/docs/advanced/cluster-pod-security-standard.md
index 530710c4f0..f932969112 100644
--- a/docs/advanced/cluster-pod-security-standard.md
+++ b/docs/advanced/cluster-pod-security-standard.md
@@ -9,17 +9,13 @@ title: "Harvester Cluster Pod Security Standard Setting"
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.8/advanced/cluster-pod-security-standard"/>
 </head>
 
- Starting from v1.8.0, Harvester provides a more flexible way for cluster admins to apply [Kubernetes Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) by changing a setting.
+Starting from v1.8.0, Harvester provides a more flexible way for cluster admins to apply [Kubernetes Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) by changing a setting.
 
 This is useful for users leveraging Harvester for bare metal workloads.
 
-
-
 ## Background
 
-Harvester users running baremetal workloads in large multi-tenant environments may need to avoid privileged escalation. 
-
-Users could manually apply pod security standards using the following knowledge base [document](https://harvesterhci.io/kb/2025/05/08/using-pod-security-standard).
+Harvester users running baremetal workloads in large multi-tenant environments may need to avoid privileged escalation.
 
 The new setting simplifies setup of cluster-wide pod security standards.
 
@@ -28,7 +24,7 @@ The setting is disabled by default.
 ```json
 {
   "enabled":false,
-  "whitelistedNamespacesList":"", 
+  "whitelistedNamespacesList":"",
   "privilegedNamespacesList":"",
   "restrictedNamespacesList":""
 }
@@ -36,7 +32,7 @@ The setting is disabled by default.
 
 The various fields are as follows
 
-**enabled**: when `true` ensures a [baseline](https://kubernetes.io/docs/concepts/security/pod-security-standards/#baseline) standard is applied to all non harvester system specific namespaces. Core Harvester features are verified to work at the `baseline` level. Once enabled, direct changes to the namespace PSS configuration are forbidden. All modifications must be done via the Harvester settings UI or API.
+**enabled**: when `true` ensures a [baseline](https://kubernetes.io/docs/concepts/security/pod-security-standards/#baseline) standard is applied to all non-Harvester system specific namespaces. Core Harvester features are verified to work at the `baseline` level. Once enabled, direct changes to the namespace PSS configuration are forbidden. All modifications must be done via the Harvester settings UI or API.
 
 **whitelistedNamespacesList**: cluster admins can specify a list of namespaces to be skipped from pod security standard application.
 
@@ -44,11 +40,34 @@ The various fields are as follows
 
 **restrictedNamespacesList**: cluster admins can specify a list of namespaces which will have [restricted](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted) pod security standard applied.
 
-
 ## Configuring pod security standards
+
 Cluster-wide pod security standards can be applied using the `cluster-pod-security-standard` setting.
 
- To enable this setting, check its current value:
+<Tabs>
+<TabItem value="ui" label="UI" default>
+
+#### Enable the Pod Security Standard Setting
+
+1. Go to **Advanced > Settings > cluster-pod-security-standard**.
+1. Select **Edit Setting**.
+1. Select **Enabled**.
+1. Use the **Whitelisted Namespaces**, **Privileged Namespaces**, **Restricted Namespaces** settings to designate pod security standards to specific namespaces.
+    * For each setting, multiple namespaces can be specified by separating them with a comma.
+1. Click **Save**.
+
+#### Disable the Pod Security Standard Setting
+
+1. Go to **Advanced > Settings > cluster-pod-security-standard**.
+1. Select **Disabled**.
+1. Click **Save**.
+
+</TabItem>
+
+<TabItem value="cli" label="CLI">
+
+To enable this setting, check its current value:
+
 ```shell
 kubectl get settings.harvesterhci.io cluster-pod-security-standard
 NAME                            VALUE
@@ -56,13 +75,69 @@ cluster-pod-security-standard
 ```
 
 Update the setting as follows:
+
 ```shell
 kubectl patch settings.harvesterhci.io cluster-pod-security-standard --type='json' -p='[{"op": "replace", "path": "/value", "value": "{\"enabled\":true,\"whitelistedNamespacesList\":\"default\",\"restrictedNamespacesList\":\"demo,restricted-ns\",\"privilegedNamespacesList\":\"demo2,privileged-ns\"}"}]'
 ```
 
 Verify that the setting was applied:
+
 ```shell
 kubectl get settings.harvesterhci.io cluster-pod-security-standard
 NAME                            VALUE
 cluster-pod-security-standard   {"enabled":true,"whitelistedNamespacesList":"default","restrictedNamespacesList":"demo,restricted-ns","privilegedNamespacesList":"demo2,privileged-ns"}
-```
\ No newline at end of file
+```
+
+</TabItem>
+</Tabs>
+
+:::note
+
+The following list of system namespaces are always whitelisted to ensure the proper functioning of Harvester. Their PSS settings cannot be modified:
+
+* `calico-apiserver`
+* `calico-system`
+* `cattle-alerting`
+* `cattle-csp-adapter-system`
+* `cattle-elemental-system`
+* `cattle-epinio-system`
+* `cattle-externalip-system`
+* `cattle-fleet-local-system`
+* `cattle-fleet-system`
+* `cattle-gatekeeper-system`
+* `cattle-global-data`
+* `cattle-global-nt`
+* `cattle-impersonation-system`
+* `cattle-istio`
+* `cattle-istio-system`
+* `cattle-logging`
+* `cattle-logging-system`
+* `cattle-monitoring-system`
+* `cattle-neuvector-system`
+* `cattle-prometheus`
+* `cattle-provisioning-capi-system`
+* `cattle-resources-system`
+* `cattle-sriov-system`
+* `cattle-system`
+* `cattle-ui-plugin-system`
+* `cattle-windows-gmsa-system`
+* `cert-manager`
+* `cis-operator-system`
+* `fleet-default`
+* `ingress-nginx`
+* `istio-system`
+* `kube-node-lease`
+* `kube-public`
+* `kube-system`
+* `longhorn-system`
+* `rancher-alerting-drivers`
+* `security-scan`
+* `tigera-operator`
+* `harvester-system`
+* `rancher-vcluster`
+* `cattle-dashboards`
+* `fleet-local`
+* `local`
+* `forklift`
+
+:::