Architecture
Extends IDM. Replaces nothing.
Mir.IAM components run inside the existing IDM engine as drivers, policies, and workflow extensions. No separate platform. No additional infrastructure. No migration required.
Architecture principles
Configuration-driven
Behavior is controlled through configuration objects in eDirectory, not custom code. Changes deploy without recompilation.
Zero extra infrastructure
All components run on the existing IDM platform. No additional servers, databases, or message queues.
Modular composition
4 products, 46 components. Adopt what you need without coupling to what you do not.
Production-proven
Every capability is tested and hardened across real enterprise deployments before it enters the catalog.
How each product integrates into the IAM architecture
Each Mir.IAM product extends a distinct part of the OpenText / NetIQ IDM operating model. Rather than introducing a separate platform, the products plug into the existing architecture at focused control points: application governance, operational protection, lifecycle automation, and privileged-access enforcement.
MAYA integrates at the application-governance layer. It gives teams a repeatable way to declare applications, structure access rights, and bring those applications into the IDM governance model quickly, so request workflows, self-service, reporting, and role logic can start from a controlled foundation.
PAUL integrates inside the operational supervision and protection layer of IDM. It adds threshold-based safeguards, centralized audit visibility, and alerting around high-risk or abnormal event flows, helping teams detect and contain damaging processing patterns before they spread across the environment.
SARA integrates at the lifecycle-automation layer. It supports joiner, mover, and leaver execution with configuration-driven logic, grace-period handling, and protections against premature removals, so standard access-right transitions can be automated without turning the operating model into a maintenance burden.
ZETI integrates where least-privilege control needs to be enforced more aggressively. It focuses on privileged groups, local-admin rights, and other sensitive authorization paths, adding monitoring, enforcement, and cleanup logic that helps keep privileged access aligned with IAM policy over time.