Compliance Drift Detection & Auto-Remediation in VCF Operations (formerly Aria Operations)
Objectives
- Build a custom HIPAA compliance benchmark in VCF Operations, detect drift, and wire an approval-gated remediation workflow in VCF Operations orchestrator.
Prerequisites
VCF lab environment deployed and operational
Lab Environment
VCF 9.0 lab environment with VCF Operations 9.0; UI paths in this lab follow VCF Operations 9.0. The 2V0-32.24 Cloud Operations 8.x exam itself targets vRealize Operations 8.6, vRealize Log Insight 8.8 and vRealize Suite Lifecycle Manager 8.8, so map any 8.x exam detail accordingly.
Tasks
Task 1 Compliance Drift Detection & Auto-Remediation
Configure HIPAA compliance baseline, detect drift, and set up automated remediation via vRO workflow.
Define the HIPAA baseline. All prod VMs (tag environment:prod) must have:
- VM encryption: enabled, AES-256
- Secure Boot: enabled
- vTPM: present
In VCF Operations go to Infrastructure Operations > Configurations > Alert Definitions tile and create one alert definition per rule (alert subtype Compliance, base object type Virtual Machine) built on property symptoms for the encryption, Secure Boot and vTPM configuration properties. Then go to Security > Compliance > Custom Benchmarks > Add Custom Compliance > Create a New Custom Benchmark, name it "HIPAA-Encryption-Baseline", add the three alert definitions, and activate it in the policy that applies to the prod custom group.
Manually introduce drift.
- In vCenter select two prod VMs
- Disable encryption on one; on the other change the storage policy so encryption no longer applies (simulate an accidental change)
- Save the changes
Detect the drift.
- Compliance is evaluated from collected data through the Compliance-subtype alert definitions (VCF 9.0.1 docs p.5504), and a standard collection cycle begins every five minutes (p.3102), so allow at least one collection cycle after the change and record how long the alert took to appear
- Open Security > Compliance, select the HIPAA-Encryption-Baseline score card: expect two VMs in violation
- Open a violated object's Alerts tab > Symptoms: the triggered symptom shows the actual value against the expected one (e.g. encryption OFF, expected ON)
Create the remediation workflow in VCF Operations orchestrator.
- In the orchestrator client (https://<orchestrator-fqdn>) go to Library > Workflows and create "Remediate-HIPAA-Encryption" with one VC:VirtualMachine input
- Steps: a User interaction schema element for the approval, with its security.group variable set to the ops-lead LDAP group and its timeout.date variable set (VCF 9.0.1 docs p.6744-6745; the workflow suspends until a group member responds or the timeout passes, then fails), then power off the VM, apply the encryption storage policy (reconfigure the VM's home and disks), power on, and send a completion email
- Register the vCenter instance by running the Add a vCenter Server instance workflow if it is not already registered (VCF 9.0.1 docs p.6567)
- Run the workflow once by hand on a test VM and check it under Activity > Workflow Runs (VCF 9.0.1 docs p.6632)
Wire the alert to the workflow.
- Install and configure the Management Pack for Orchestrator in VCF Operations (Administration > Integrations), pointing at the orchestrator instance
- Map the "Remediate-HIPAA-Encryption" workflow as the action of a recommendation on the encryption compliance alert definition
- Notifications: Infrastructure Operations > Configurations > Notifications tile, create a rule for the HIPAA alerts with the Standard Email Plugin (Outbound Settings) to ops-lead@company.com
- Keep the workflow approval-gated: the alert surfaces a Run Action, nothing executes unattended
Test the automation (approval-required mode).
- In VCF Operations go to Troubleshoot > Alerts, select the HIPAA alert on the drifted VM, show the Action column and click Run
- The workflow suspends at the User interaction element; the waiting request shows in the Recent Workflow Runs panel of the orchestrator dashboard and the top-right notification menu (VCF 9.0.1 docs p.6617), where an ops-lead group member approves it
- The workflow powers off the VM, re-applies encryption, powers it on and sends the completion email
- After the next collection cycle the compliance score card shows the VM compliant again
Generate the compliance report.
- Infrastructure Operations > Dashboards & Reports > Reports: create a report on the prod custom group over the last 30 days
- Columns: VM Name, Compliance Status, Violations, Remediation Actions, Time to Remediate (from the orchestrator run history)
- Export as CSV
Validation Gate
Check: Verify lab completion
Expected: Lab exercise completed successfully
Common Errors
Final Validation
Lab completed successfully
✓ All steps completed → No errors observed
Cleanup / Restore
• Revert to snapshot if needed
Design Reflection (VCDX)
Compliance automation demonstrates operational maturity and regulatory awareness. VCDX panelists test how you maintain compliance at scale without manual auditing.