The graph is the same.
The consequence is not.
Reachability math does not change between sectors. What changes is what sits at the end of the path — and which regulator asks you to account for it. These pages describe how identity risk takes a different shape depending on what your organization is accountable for.
Healthcare & Life Sciences
PHI reachable by identities nobody owns
Financial Services
Standing privilege where money moves
Government & Public Sector
Citizen data, contractor identities, long system lifetimes
Technology & SaaS
Machine identities outnumber humans, by a lot
Manufacturing & Industrial
IT identities reaching operational systems
Retail & E-commerce
Seasonal scale, permanent access
Energy & Utilities
Critical infrastructure, regulated access
Professional Services
Client data, matter boundaries, guest sprawl
Your sector is not on the list? The engine does not care — these pages exist because the regulated data and the operating model differ, not because the product does.
No sector-specific product. One platform.
There is no healthcare edition and no financial-services module. Selling the same engine under eight names would be a pricing strategy dressed as a product strategy.
What genuinely differs by sector is the classification of your data, the frameworks you must evidence against, and the identity patterns your operating model produces. Data Trust Zones and control mappings are configuration. Everything underneath is the same graph.
Start with the question you cannot answer today.
A scoped assessment against your own Azure tenant. Read-only, agentless, and nothing is written to your environment — ever.
Free forever on a bounded estate · 30-day trial unlocks everything · No credit card
Read-only access · No agents · No log ingestion · Azure generally available