Identity lifecycle
| Alternative names | Identity lifecycle management |
|---|---|
| Status | supported |
| Since | 3.5 |
Description
Identities are not static, they evolve in time. There may be a record about the identity before its activation, then the identity becomes active, temporarily suspended, archived and finally deleted. In midPoint, every object in midPoint is in certain lifecycle state, specifying its state or maturity for use. This principle also applies to all objects that represent identities.
Documentation
| Version | Introduction | Guides | Configuration | Examples | Plans |
|---|---|---|---|---|---|
| 4.9 | Object Lifecycle |
||||
| Development | Object Lifecycle |
||||
| 4.8 | Object Lifecycle |
Related Features
Compliance
This feature is related to the following compliance frameworks:
-
ISO/IEC 27001 5.19: Information security in supplier relationships
-
ISO/IEC 27001 5.20: Addressing information security within supplier agreements
-
ISO/IEC 27001 5.23: Information security for use of cloud services
-
ISO/IEC 27001 5.24: Information security incident management planning and preparation
-
ISO/IEC 27001 5.25: Assessment and decision on information security events
-
ISO/IEC 27001 5.26: Response to information security incidents
-
ISO/IEC 27001 6.5: Responsibilities after termination or change of employment
-
ISO/IEC 27001 8.27: Secure system architecture and engineering principles