Skip to main content
Applies to BloodHound Enterprise only Some important systems do not fit cleanly into a traditional Tier Zero, Tier One, or Tier Two model. Many applications and environments matter because of the data they process, the business function they support, or the regulatory exposure they create. Examples include:
  • Clinical systems
  • Payment systems
  • Customer data platforms
  • Production control planes
  • Trading or settlement systems
  • Identity infrastructure for a specific business unit
  • Systems in scope for PCI, HIPAA, SOX, or other regulatory programs
Privilege Zones can draw a fence around those assets and analyze attack paths into them.

​
Scenario

A healthcare organization wants to understand attack paths into a set of critical clinical application servers. These systems may not be Tier Zero in the traditional sense, but compromise would create patient care, regulatory, financial, and reputational impact. The team creates a Privilege Zone containing the application servers and supporting infrastructure. The first version may use known server lists, application owner input, OUs, or naming conventions. Once the zone is analyzed, BloodHound Enterprise identifies the users, groups, systems, and relationships that can create paths into that environment.

​
What this can reveal

  • Broad server groups with access to application servers
  • Administrative users outside the expected support model
  • Legacy permissions inherited from prior domain or application structures
  • Misaligned ownership between application teams and infrastructure teams
  • Paths from ordinary users or lower-tier systems into regulated environments

​
Why this works

Critical application zones make Attack Path Management easier to connect to business priorities. The team can ask a specific question: who can reach this application and should they be able to? This approach is useful in complex environments where full tiering may take time. A critical application zone gives the team a practical starting point with clear business relevance.

​
Suggested workflow

  1. Select one critical application or regulated environment.
  2. Identify the systems, groups, service accounts, and administrative roles that support it.
  3. Create a zone using known objects, OUs, naming conventions, or Cypher.
  4. Review attack paths into the zone.
  5. Validate findings with the application owner and infrastructure owner.
  6. Remediate unexpected paths.
  7. Keep the zone for ongoing monitoring or use the process to define the next critical application zone.

​
Starter Cypher queries

These example Cypher queries help you identify candidate objects for zones and labels during discovery, trials, and early implementation.
Review and tune these queries before using them as production Privilege Zone rules.

​
Healthcare or clinical system discovery

​
PCI or payment system discovery

​
Production system discovery

​
Paths into a critical application zone

​
Guidance

Start with a system that has a clear business owner and clear consequences if compromised. Broad keyword searches are useful for discovery, but production rules should be reviewed with application owners so the zone remains credible.

​
Key takeaway

Privilege Zones help organizations apply Attack Path Management to the applications and regulated environments that carry the highest business impact.