Securing vSphere Against BRICKSTORM: A Comprehensive Hardening Guide

Overview

The BRICKSTORM campaign, as detailed by Google Threat Intelligence Group, targets the virtualization layer of VMware vSphere environments—specifically the vCenter Server Appliance (VCSA) and ESXi hypervisors. Attackers establish persistence below the guest operating system, bypassing traditional endpoint detection and response (EDR) tools. This is not due to vendor vulnerabilities but rather weak security architecture, identity design, and limited visibility. This guide transforms your virtualization stack from a blind spot into a hardened, observable fortress.

Securing vSphere Against BRICKSTORM: A Comprehensive Hardening Guide — Source: www.mandiant.com

Prerequisites

Before starting, ensure you have:

Administrative access to vCenter Server (vSphere Client or SSH to VCSA)
Root or sudo privileges on the Photon Linux OS of the VCSA
Knowledge of basic vSphere and Linux command-line operations
A backup of VCSA configuration (optional but recommended)

Step-by-Step Hardening Instructions

1. Harden the Photon OS Layer

The VCSA runs on a customized Photon Linux. Secure it like a Tier‑0 asset.

Update the system
tdnf update -y
Disable unneeded services
Stop and mask services like bluetooth, cups, etc. Use systemctl list-units --type=service to review.
Configure the host firewall
Enable and restrict iptables to allow only essential ports (443, 22 from management jump host, etc.).
Set up auditd
Install and configure auditd to monitor critical files and commands:
auditctl -w /etc/shadow -p wa -k shadow_changes

2. Enforce Identity and Access Controls

Attackers often exploit weak authentication. Implement the following:

Disable the default root SSH login. Use a dedicated service account with sudo.
Enforce multi‑factor authentication (MFA) via VMware Identity Manager or an external IdP.
Create custom vSphere roles with least‑privilege and avoid assigning Administrator globally.
Regularly review SSO group memberships and remove orphaned accounts.

3. Configure Comprehensive Logging

Visibility is critical. Centralize all logs to a SIEM or syslog server.

In vSphere Client, navigate to Administration > System Configuration > Services and enable syslog for VCSA and all ESXi hosts.
On Photon OS, forward /var/log/audit/audit.log using audispd or rsyslog.
Enable VMware vCenter events logging for all operations (e.g., VM creation, permission changes).

4. Implement Network Segmentation

Isolate the management network from production traffic.

Place VCSA and ESXi management interfaces on a dedicated VLAN with strict firewall rules.
Use a separate jump box (bastion host) for administrative access; block direct internet access to VCSA.
Apply network access control lists (ACLs) to restrict communication to only required services.

5. Deploy the Mandiant vCenter Hardening Script

Mandiant released a script that automates many of these settings. Run it after reviewing the source:

Download the script from GitHub or Mandiant’s repository onto a secure machine.
Transfer to VCSA via scp to a temporary directory.
Review the script’s configuration file (e.g., hardening.conf) and adjust to your environment.
Execute with root privileges: bash vcenter_harden.sh --apply
Verify changes by checking the audit log and service status.

Common Mistakes to Avoid

Leaving default credentials: Change the root password immediately after deployment.
Skipping patches: Regularly apply VMware security advisories—BRICKSTORM exploits known weaknesses in exposed services.
Insufficient logging: Without centralized logs, spotting lateral movement becomes nearly impossible.
Over‑permissive firewall rules: Allow only absolute minimum ports (443, 22 from management hosts, and vSphere replication ports if needed).
Ignoring Photon OS security: Many admins treat VCSA as a black box; hardening the underlying OS is essential.

Summary

BRICKSTORM demonstrates how threat actors exploit visibility gaps at the virtualization layer. By hardening the Photon OS, enforcing strict access controls, centralizing logging, segmenting networks, and leveraging tools like the Mandiant hardening script, organizations can detect and block adversaries operating below the guest OS. Transform your vSphere environment from an attacker’s paradise into a defensible, monitored Tier‑0 asset. Apply these steps today to protect your critical workloads.

Tags: