Find an owner before you accept the access.
An account without an accountable owner needs investigation. Service accounts and other non-human identities need that ownership even when they do not follow an employee’s HR record.
Start with a defined population
Service accounts keep integrations, scheduled jobs and applications running. Their access needs a named owner and a clear purpose, just as employee access does. Comparing accounts in connected systems with your identity records helps identify ownership gaps.
A missing match is a reason to investigate. It is not enough evidence to delete the account: a business service may depend on it.
Know who is responsible
Ownership information gives a reviewer someone to contact about the account’s purpose and continued need. The available view depends on the account type, connected source and supported workflow; our team will establish that scope with you.
When an owner leaves, responsibility needs to pass to another accountable person. An account created outside easyIGA keeps the origin details available from midPoint; missing historical information is marked rather than guessed.
Agree how to resolve the finding
Identify the application owner who can confirm the account’s purpose. Decide whether to assign an accountable owner, restrict the access or retire the account through a tested process.
The access review records the decision, while the evidence trail distinguishes it from the confirmed outcome of an access change.
Bring your own access question
See how easyIGA simplifies everyday access management for your organisation in a 30-minute live walkthrough. Our team will discuss your systems and the tasks you want to improve.