Big Data Workload Managementīackup Cassandra workloads while a cluster is active and granularly restore from table or keyspace level. Kubernetes Data MovementĪpplication-consistent Kubernetes cluster backup, deduplication, and image duplication for the tiering of backup storage (service lifecycle policies, “SLP”) and Auto Image Replication in containerized environments. Scale and protect cloud workloads with efficient and secure object storage support. PaaS workloads will be automatically discovered across all major cloud providers, and create protection plans autonomously, providing fast and agile support for new workloads. The actual hardening guides can be found here => Īgain, each document has a comments form, the authors are actively seeking constructive comments on these documents before going to a final version.Isolated Recovery Environment EnhancementsĮliminate the need for additional infrastructure when isolating and protecting data and use the pull method to move data without the risk of introducing malicious activity from production to an environment. While reviewing the draft, you'll see that most guidelines are worded to be 'script friendly', which is very nice to see. The Hardening Guide can certainly be used as-is for production environments today, but we can expect changes over the next while in response to comments to the posted draft.

A worthy successor to the current VMware Hardening Guide, it contains over 100 guidelines, split into the following sections:Īside from the versioning difference, this newer version of the guide uses a standardized format, and has severity levels for each security recommendation. VMware announces the first draft of the vSphere Hardening Guide, posted for public comment.

Vsphere 6 keygen malware