IAM Maintainability
IAM maintainability is the ability to fix, upgrade and evolve an identity platform without disproportionate risk or cost.
- Synonym
- ease of maintenanceevolvability
Definition
IAM maintainability is distinct from operability: operability is about running and watching the system, maintainability is about changing it. It depends on overall architectural complexity, accumulated debt, the amount and nature of customisation, extensions and bespoke code, the number and age of connectors, dependencies between components, documentation quality, release cadence and vendor support, available skills and the existence of regression tests. A maintainable platform lets a team apply a security fix, move to a major version or onboard an application without launching a project each time.
Why it matters
A platform that is hard to evolve eventually freezes an organisation's security posture at the level it had on go-live day.
The Ariovis perspective
Bespoke work is not bad by nature: a specific development is sometimes exactly the right answer to a business need. The danger appears when customisation loses its owner, its tests and its documentation, or when it blocks any platform upgrade. The useful question is not "do we have customisation?" but "do we know why it exists, and can we still maintain it?"
Common pitfalls
- A common mistake is accumulating customisations with no owner and no tests, until upgrading becomes riskier than standing still.
Resources
Explore this category
These concepts matter most inside a real project.
The first conversation helps establish your context, the systems involved and the next useful decision.