vCenter Server security hardening guide
- Maintain supported OS, Database, and hardware for vCenter
- Keep vCenter Windows OS patches up to date
- Provide Windows system protection on vCenter server
- Limit access to vCenter server system
- Install vCenter Server with service account, instead of a build-in Windows account, while it is a local administrator account
- Restrict usage of vSphere administrator privilege.
- vCenter server communication
- SSL certificate from CA
- Service account access to certification directory
- Restrict access to SSL certificate files
- Always verify SSL certificates
- Restrict access to only those essential components required to communicated with vCenter.
- Block unused port on vCenter.
- Disable managed object browers from vpxd.cfg
- Disable vSphere web access (tomcat under infrastructure folder, ui directory)
- Disable datastore browser: vpxd.cfg
- Least privilege for vCenter server database user.
- vSphere client components
- Restrict use of Linux-based clients, jump-box is preferred.
- Verify the integrity of vSphere client: only authorized extensions from trusted source.
- Least privilege for the update Manager database user.
- Keep VUM patched up to date
- Provide Windows OS protection on VUM server
- Avoid user log into VUM server
- VUM won't manage patch for VUM server
- Limit the connectivity between VUM and public patch repository
No comments:
Post a Comment