Lab: Apply Security Compliance Benchmark and Configure Chargeback
Objectives
- Enable and apply CIS ESXi security benchmark in VCF Operations
- Analyze compliance findings and execute remediation workflows
- Create custom compliance benchmarks for VCF-specific requirements
- Configure costing rate cards for chargeback/showback reporting
- Generate cost allocation reports per workload domain and business unit
- Design a unified compliance + cost governance strategy for VCDX defense
Prerequisites
VCF Operations deployed with vCenter adapter collecting data (Lab 11 prerequisite)
Prior labs: vcp-admin-11
Required skills:
- VCF Operations UI navigation
- ESXi security hardening concepts
- CIS benchmark framework understanding
- Basic cost management principles
Lab Environment
Holodeck VCF pod with VCF Operations monitoring management domain. ESXi hosts in default (non-hardened) state for compliance testing.
Credentials
| System | Username | Password |
|---|---|---|
| VCF Operations | admin | |
| vCenter | administrator@vsphere.local |
Tasks
Task 1 Enable CIS Compliance Benchmark and Analyze Findings
securitySecurity compliance is a key exam topic (Obj 4.3). CIS benchmarks provide industry-standard hardening checks for ESXi hosts. Understanding how VCF Operations automates compliance scanning is critical for both admin operations and VCDX defense.
Navigate to VCF Operations > Security > Compliance. Observe the current state: data sources (vCenter, VMware Cloud Foundation) on top, and the benchmark sections (VMware SDDC Benchmarks, VCF Benchmarks, Custom Benchmarks, Regulatory Benchmarks). With nothing enabled there are no score cards.
Install the CIS pack: download the CIS compliance pack (.pak) from the VMware Marketplace, add it under Administration > Integrations (Repository), then in Security > Compliance click Activate From Repository on the CIS pack and Activate.
Enable the benchmark policies: on the Security > Compliance page click Enable on the installed CIS pack card; in the Enable Policies dialog select the policy that applies to the management cluster objects (a child policy can be selected instead of the parent) and click Enable. VCF Operations activates the compliance alert definitions in that policy.
Wait for the next collection cycles. Return to Security > Compliance and open the CIS score card: per-object compliance scores (percentage), with non-compliant objects and their violations listed.
Click a host with a low compliance score. Expand the violations list. For each alert, review: CIS control ID, description, current value, expected value, recommendation (esxcli or PowerCLI), criticality.
Export a compliance report: Visualize > Reports, generate a report on the compliance alerts for the management cluster (or use the score card's report option where offered), format PDF. Review the structure: summary, per-host details, recommendations.
Validation Gate
Check: Compliance dashboard shows per-host compliance percentage with detailed findings
Expected: CIS ESXi 8 benchmark results visible for all management cluster hosts with specific control findings
Task 2 Execute Compliance Remediation Workflows
securityKnowing what's non-compliant is only half the story — remediation demonstrates operational competence. This task covers both manual and automated remediation approaches.
Select a non-compliant finding with clear remediation: 'SSH service enabled' (CIS 1.2). Review the remediation: stop the SSH service and set it not to start with the host (VMware Host Client → Manage → Services → TSM-SSH → Stop, VCF 9.0.1 docs p.1271; or the host's Services settings in the vSphere Client). Note the risk: in Holodeck this removes your shell access to the host, so review it but do not apply it here.
Remediate a safe finding: Set shell timeout. SSH to an ESXi host → run: esxcli system settings advanced set -o /UserVars/ESXiShellInteractiveTimeOut -i 900. This sets 15-minute shell timeout without breaking lab functionality.
Wait for the next collection cycles (compliance is evaluated continuously against collected data; there is no manual rescan button). Return to Security > Compliance, open the CIS score card and the host, and verify the remediated alert has cancelled.
Document remediation exceptions. For a finding that cannot be remediated in this environment, record an exception: justification, risk owner, review date. In VCF Operations, use the compliance alert's recommendation and the alert definition's state in the policy to track accepted deviations (for example deactivate the alert definition in a lab-only child policy). A legitimate lab example: 'ESX Shell/SSH left enabled on Holodeck nested hosts for lab console access; not permitted in production.'
Review the configuration-enforcement layer. Host Profiles are deprecated in vCenter 9.0 (VCF 9.0.1 docs p.226). Use vSphere Configuration Profiles at cluster level (vSphere Client > cluster > Configure > Desired State > Configuration; vSphere 9.0 docs: Create a Draft Configuration in vSphere Client) to define the hardened settings as desired state, and VCF Operations configuration drift (Configuration Drift dashboard: vCenter instances with configuration templates and vSphere clusters with Configuration Profiles enabled, pp.2954) to detect deviation.
Validation Gate
Check: At least one finding remediated and re-scan shows improved compliance score
Expected: Compliance percentage increased after remediation. Exception documented for unremediated findings.
Task 3 Create Custom Compliance Benchmark for VCF
securityCIS benchmarks are generic ESXi hardening. VCF environments have specific requirements (SDDC Manager connectivity, NSX VTEP MTU, vSAN network settings) that need custom compliance checks.
Navigate to Security > Compliance. In the Custom Benchmarks section click Add Custom Compliance, select Create a New Custom Benchmark, and enter Name='VCF 9.0 Operational Baseline' and a description. Click Next.
Add custom compliance checks (symptoms and alert definitions that map to compliance controls):
- vSAN Network MTU Check: Verify VMkernel adapter MTU >= 9000 for vSAN traffic
- SDDC Manager Connectivity: Verify ESXi host can reach SDDC Manager on port 443
- NTP Synchronization: Verify time drift < 5 seconds across all hosts
- vSAN Disk Health: Verify no disks in 'Degraded' or 'Absent' state
Enable the custom benchmark alongside CIS: finish the Add Custom Compliance wizard by selecting the policy that covers the management cluster, then click Enable.
Compare compliance views on Security > Compliance: open the CIS score card and the custom score card separately. Note which areas each benchmark catches that the other misses.
Validation Gate
Check: Custom VCF compliance benchmark created, enabled, and producing compliance data alongside CIS
Expected: Two benchmarks active with separate compliance scores per host
Task 4 Configure Costing Rate Cards and Generate Business Unit Reports
manageabilityChargeback/showback is exam-relevant under Obj 4.3. Rate cards translate infrastructure consumption into business costs, enabling IT-as-a-service financial transparency.
Navigate to VCF Operations → Infrastructure Operations → Configuration → Policy Definitions. Select the policy that applies to your management cluster → horizontal ellipsis → Edit → VC Pricing → New Pricing Card. Review the two pricing card types: cost-based (cost factors for CPU, memory, storage and additional cost, multiplied by a factor) and rate-based (CPU rate, memory rate per GB and storage rate per GB), each with a charging period (hourly, daily, weekly or monthly) and a charge-on-power-state option (VCF 9.0.1 docs pp.5207-5208).
Create three rate-based pricing cards for different service levels (illustrative rates; enter them in the units the pricing card prompts for):
- 'Standard Tier': CPU=$0.03/GHz/day, Memory=$0.008/GB/day, Storage=$0.003/GB/day
- 'Performance Tier': CPU=$0.06/GHz/day, Memory=$0.015/GB/day, Storage=$0.008/GB/day (vSAN all-flash)
- 'Mission Critical': CPU=$0.10/GHz/day, Memory=$0.025/GB/day, Storage=$0.015/GB/day (stretched cluster + HA)
Assign pricing cards to clusters: pricing cards are assigned to vCenter instances or clusters, and a cluster assignment takes precedence over the vCenter-level card for everything under that cluster (VCF 9.0.1 docs pp.5207-5208). Assign 'Standard Tier' to the management cluster. In production, 'Performance Tier' would map to VI workload domain compute clusters, 'Mission Critical' to stretched clusters.
Generate cost reports: Cost → Overview → review per-VM cost breakdown. Drill into a VM to see: daily compute cost, daily storage cost, total monthly projection. Navigate to Cost → Reports → Create → 'Monthly Cost by VM' → PDF.
Configure cost allocation by business unit: Create custom groups in VCF Operations (Environment → Custom Groups) → group VMs by business unit using naming convention or tags. Generate cost report filtered by custom group to show per-department costs.
Compare showback vs chargeback modes: Review the difference — showback displays costs for transparency without billing action; chargeback integrates with finance/ERP systems (ServiceNow, SAP) for actual cross-charging. No 'Mode = Showback' setting surfaced in the VCF 9.0.1 cost documentation: in VCF Operations, showback is delivered through the Showback VM Cost and Showback (Business Application Cost) dashboards, and price-based chargeback through the Chargeback VM Price dashboard (VCF 9.0.1 docs pp.4090-4091). Open the Showback VM Cost dashboard and compare it with the Chargeback VM Price dashboard.
Validation Gate
Check: Tiered rate cards created, assigned to clusters, per-VM cost reports generated with business unit allocation
Expected: Cost dashboard shows per-VM costs with rate card pricing. Business unit cost allocation visible via custom groups.
Task 5 Unified Compliance + Cost Governance Strategy and VCDX Defense
manageabilityCompliance and costing are two sides of governance. This task ties them together into a holistic operational model that demonstrates architect-level thinking for VCDX defense.
Build a governance dashboard in VCF Operations: Create a custom dashboard (Dashboards → New) with widgets showing:
- Compliance Score by Cluster (scoreboard widget)
- Non-Compliant Findings Trend (line chart, 30 days)
- Monthly Cost by Workload Domain (bar chart)
- Cost per VM Trend (line chart, 90 days)
- Top 10 Most Expensive VMs (top-N widget)
Create compliance-cost correlation: Using Super Metrics (from Lab 11), create a metric that calculates 'Cost of Non-Compliance' = (number of non-compliant findings) x (estimated remediation hours) x (engineer hourly rate). This quantifies the business impact of security debt.
Configure automated alerts for governance thresholds:
- Alert if compliance score drops below 80% on any cluster
- Alert if monthly cost exceeds budget threshold per business unit
- Alert if a VM runs without compliance scan for > 48 hours
Set notification channel to email (configured in Lab 11).
VCDX Defense Preparation — document and rehearse responses to these panelist questions:
- 'How do you balance security hardening (CIS) with operational needs (SSH access for troubleshooting)?'
Answer: Exception-based model. SSH disabled by default, enabled via change request during maintenance windows with audited access. SDDC Manager uses its own management path that doesn't require persistent SSH.
- 'What costing model justifies VCF investment to leadership?'
Answer: TCO comparison. VCF per-core licensing vs traditional vSphere + separate NSX + separate vSAN licensing. Show how consolidated management reduces operating cost using the customer's own TCO figures (no generic percentage). Tiered rate cards demonstrate value-based pricing.
- 'CIS says disable the ESX Shell and SSH; your operations team needs emergency CLI access. How do you handle it?'
Answer: Services disabled by default (SSH and ESX Shell are deactivated by default on ESX, VCF 9.0.1 docs p.1123); time-boxed enablement through change control, enforced with the shell timeouts (UserVars.ESXiShellTimeOut / ESXiShellInteractiveTimeOut) and an alert on the service's Running property so a forgotten enablement is caught (p.4481); lockdown mode Exception Users documented and reviewed (p.2988); every exception recorded with risk owner and review date.
- 'How do you handle shared infrastructure costs (management domain, NSX edges) in chargeback?'
Answer: Shared infrastructure costs allocated proportionally based on workload domain resource consumption. Management domain cost treated as platform overhead — either absorbed centrally or distributed evenly across business units.
Validation Gate
Check: Governance dashboard created, compliance-cost correlation configured, alerts set, VCDX defense responses prepared
Expected: Unified governance view operational with proactive monitoring and documented defense strategy
Final Validation
CIS compliance benchmark applied and remediated, custom VCF benchmark created, tiered costing configured with business unit allocation, unified governance dashboard operational.
✓ CIS ESXi 8 benchmark enabled and producing compliance data → Per-host compliance status visible with detailed findings
✓ At least one finding remediated with improved compliance score → Post-remediation re-scan shows improvement
✓ Custom VCF operational benchmark active → VCF-specific compliance checks producing results
✓ Tiered rate cards assigned to clusters → Per-VM cost calculations with tiered pricing
✓ Cost allocation by business unit configured → Custom groups showing per-department costs
✓ Governance dashboard with compliance + cost widgets → Unified view of security posture and cost efficiency
Cleanup / Restore
• Take snapshot 'post-compliance-costing'
• Note: Leave compliance benchmarks enabled for ongoing monitoring
Design Reflection (VCDX)
Panelist: How do you balance security hardening (CIS) with operational needs (SSH access for troubleshooting)? What costing model justifies VCF investment to leadership? How do you quantify security debt in business terms?
Requirements
- Regulatory compliance reporting (CIS, DISA STIG, industry-specific)
- Cost transparency per business unit with tiered service levels
- Automated compliance monitoring with drift detection
- Exception management with audit trail
Constraints
- CIS benchmarks may flag VCF-required configurations as violations
- Rate card accuracy depends on current hardware and licensing costs
- Compliance remediation may require maintenance windows
- Custom benchmarks need ongoing maintenance as VCF versions change
Assumptions
- Compliance benchmarks updated with each VCF upgrade
- Rate cards reviewed quarterly to reflect actual infrastructure costs
- Business units accept showback model before chargeback transition
- vSphere Configuration Profiles (cluster-level desired state) used to enforce consistent hardening across clusters; Host Profiles deprecated in vCenter 9.0
Risks
- Over-hardening can break VCF operational workflows (SSH, NTP, firewall rules)
- Inaccurate rate cards lead to billing disputes and loss of IT credibility
- Compliance exceptions without proper documentation create audit exposure
- Cost allocation model disputes between shared infrastructure consumers
Self-Assessment Discussion Prompts
- How would you handle a CIS finding that directly conflicts with VCF operational requirements?
- What's the difference between chargeback and showback, and when should each be used?
- How do you quantify the business impact of compliance debt to executive stakeholders?
- What's your approach to shared infrastructure cost allocation in a multi-tenant VCF environment?
- How would you design a compliance remediation workflow that minimizes operational disruption?
Extensions
Integrate VCF Operations compliance data with ServiceNow GRC module for enterprise-wide compliance reporting
Create automated remediation playbooks using VCF Operations + Automation integration
Build a compliance trend dashboard showing improvement over time for board-level reporting
⚠ Known Pitfalls
References
- CIS ESXi BenchmarkTier 1 — Official
- VCF 9.0 documentation (landing page) — VCF Operations compliance: Security > Compliance, CIS Compliance Pack for VCF (VCF 9.0.1 docs pp.5504-5516)Tier 1 — Official
- VCF 9.0 documentation (landing page) — VCF Operations pricing cards and showback/chargeback dashboards (VCF 9.0.1 docs pp.5207-5208, pp.4090-4091)Tier 1 — Official
- VMware Security Hardening GuideTier 2 — Supporting source