Features of identity and access management platforms (Okta, Microsoft Entra ID, SailPoint, Duo), mapped to HERM capabilities. The service gives each person one identity and controls what it can reach: provisioning, single sign-on, MFA, roles, access reviews and threat detection. The SIS, HR and ERP keep person attributes; applications keep their own access rules.
Shows which parts of the institution the identity service supports, where it overlaps other systems, and where it stops.
A function's main HERM home vs others it touches. Features narrow to one capability.
17 HERM capabilities touched, centred on identity and access management, information security and integration. Almost every feature sits in Enabling capabilities.
Wheel to explore, tree to scan every mapping, CSV or JSON to reuse it.
How this was compiled: three AI assistants (Claude, Perplexity and Grok) drafted lists, reconciled into one set; source letters show which drafts named each feature. A starting point, not a vendor-verified specification.
{{ xwIntro }}
The full hierarchy: areas, functional areas, functions and features, each with its HERM mapping and definition. Select any HERM capability or feature to see its full definition.
Identity is rarely one system. Here the features are mapped to the applications fictional Example State University runs, from vendor core to spreadsheets. Each link records coverage and role; HERM coverage is calculated from the links.
Also see this ecosystem as a capability × application matrix or a HERM-to-application flow.
Inner rings: area and functional area. Outer ring: one slice per feature, split into bands when more than one application provides it. Marks outside the ring flag gaps (red) and competing systems of record (violet).
{{ fd.desc }}
The executive view. Each bar is the capability’s features, coloured by the best coverage any application gives them. Select a capability for its HERM definition, or an application to see its footprint.
{{ pop.body }}