public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-24 20:18:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove 2.8 specific content and fix typo

Browse Source
This commit is contained in:
Billy Tat
2023-10-24 13:06:13 -07:00
parent 2651168190
commit 410ae2701a
2 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages-for-subheaders/rancher-security.md
-4
View File
@@ -91,7 +91,3 @@ For recommendations on securing your Kubernetes cluster, refer to the [Kubernete
### Rancher Security Best Practices
For recommendations on securing your Rancher Manager deployments, refer to the [Rancher Security Best Practices](../reference-guides/rancher-security/rancher-security-best-practices.md) guide.
### Rancher Webhook Hardening
The Rancher webhook deploys on both the upstream (local) Rancher cluster and all provisioned clusters. See the [Hardening the Rancher Webhook](../reference-guides/rancher-security/rancher-webhook-hardening.md) guide for recommendations on protecting your clusters.
docs/reference-guides/rancher-security/rancher-security-best-practices.md
+1 -1
View File
@@ -8,7 +8,7 @@ title: Rancher Security Best Practices
### Restrict Public Access to /version and /rancherversion Path
The upstream (local) Rancher instance provides information about the Rancher version it is running and the Go version that was used to built it. That information is accessible via the `/version` path, which is used for tasks such as automating version bumps, or confirming that a deployment was successful. The upstream instance also provides Rancher version information accessible via the `/rancherversion` path.
The upstream (local) Rancher instance provides information about the Rancher version it is running and the Go version that was used to build it. That information is accessible via the `/version` path, which is used for tasks such as automating version bumps, or confirming that a deployment was successful. The upstream instance also provides Rancher version information accessible via the `/rancherversion` path.
Adversaries can misuse this information to identify the running Rancher version and cross-relate it with potential bugs to exploit. If your upstream Rancher instance is publicly available on the web, use a Layer 7 firewall to block `/version` and `/rancherversion`.