pdellamore
25771e2843
* Add note regarding rancher pentest reports public availability This PR will add a note regarding third-party penetration test reports public disclosure. * Add session management section to rancher security best practices This PR will create a new section inside Rancher Security Best Practices adding security recommendations for RM deployments that might need additional security controls. * Apply suggestions from code review Co-authored-by: Paulo Gomes <paulo.gomes.uk@gmail.com> * Update docs/reference-guides/rancher-security/rancher-security-best-practices.md * Update docs/reference-guides/rancher-security/rancher-security-best-practices.md Co-authored-by: Guilherme Macedo <guilherme@gmacedo.com> * versioned docs --------- Co-authored-by: Pietro Dell'Amore <pdellamore@MacBook-Pro-de-Pietro.local> Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com> Co-authored-by: Paulo Gomes <paulo.gomes.uk@gmail.com> Co-authored-by: Guilherme Macedo <guilherme@gmacedo.com>
1.8 KiB
title
| 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 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.
See OWASP Web Application Security Testing - Enumerate Infrastructure and Application Admin Interfaces for more information on protecting your server.
Session Management
Some environments may require additional security controls for session management. For example, you may want to limit users' concurrent active sessions or restrict which geolocations those sessions can be initiated from. Such features are not supported by Rancher out of the box.
If you require such features, combine Layer 7 firewalls with external authentication providers.