It’s been a while since I visited this topic, but a few years back, Xen (and by extension XCP-NG) was better known for security whilst KVM (and thus Proxmox) was considered for better performance (yes, I’ve heard of the rumours of AWS moving to KVM from Xen for some appliances).
I would like to ask the community about the security measures you’ve taken to harden the default PROXMOX and XCP-NG installations. Have you run the CIS benchmarks and performed hardening that way? Did you enable 2FA?
I’m also interested in people who run either of these in production: what steps did you take? Did you patch the Debian base (for PVE)/Fedora base (I think, for XCP)?
Thank you for responding!
I had looked into openstack a while back but left it thinking it was too complex. I was looking at Apache’s Cloudstack then.
I see now that a contributor has got Debian in the official list of supported distributions. Which means my distro-morphing idea should work in theory with OpenStack. This is a great idea, thanks. I will look at OpenStack more seriously now. Does look like it will need some effort though
I also don’t recommend doing a manual install though, as it’s extremely complex compared to automated deployment solutions like kolla-ansible (openstack in docker containers), openstack-ansible (host os/lxc containers), or openstack-helm/genestack/atmosphere (openstack on kubernetes). They make the install much more simpler and less time consuming, while still being intensely configurable.
I see. But does the installation cover hardening steps like hardened_malloc, permission hardener, kernel self-protection etc?
I don’t think so, now. You’ll have to do those yourself.
Ah, sucks