Skip to main content
  1. posts/

Closing the Loop

 Author
Author
Christian Mohn
IT veteran, podcaster, author, and blogger from Bergen, Norway.
Table of Contents
VCF Security Reality Check: ESX, vCenter & Identity - This article is part of a series.
Part 5: This Article

Across this series, three layers have been described.

ESX as the execution layer.
vCenter as the control layer.
Identity as the reachability layer.

Each layer has a distinct role in design. In operation, they form a single chain.

The model in context
#

flowchart TD
A[Identity - Active Directory / Entra ID] --> B[vCenter Control Plane]
B --> C[ESX Execution Layer]
C --> D[Workloads / Virtual Machines]

This model reflects how virtual infrastructure behaves when it is actively used. It is not a theoretical construct. It describes how control flows in practice.

How the chain operates
#

Identity determines whether access exists.

If identity is valid, vCenter becomes reachable through normal administrative interfaces. If vCenter is reachable, ESX becomes controllable through the operations it is designed to execute.

Each layer operates independently in implementation. The combined effect is a single control path.

Where separation stops behaving as isolation
#

In design, ESX, vCenter, and identity are treated as separate domains. In operation, those domains describe responsibility, not isolation. Identity defines reachability. It does not stop at authentication.

vCenter defines control. It does not evaluate intent. ESX defines execution. It does not evaluate origin.

Each layer performs its function exactly as designed.

What the model shows in practice
#

The important point is not that the layers exist. It is that once identity is valid, the distinction between layers no longer limits control flow in any meaningful way.

At that point, the system behaves as a single operational chain rather than independent components.

Where risk concentrates
#

Risk does not concentrate in ESX alone. It does not concentrate in vCenter alone. It concentrates at the point where identity becomes sufficient to traverse the control plane.

From that point onward, ESX and vCenter operate within expected parameters. They do not fail. They execute.

Closing statement
#

ESX executes state. vCenter defines control. Identity defines reachability.

Across this series, these layers have been examined separately. In practice, they operate as one chain.

And once identity is valid within that chain, the system behaves exactly as designed, consistently across all layers, without requiring any break in individual components.

VCF Security Reality Check: ESX, vCenter & Identity - This article is part of a series.
Part 5: This Article

Related