Most identity governance programmes name an application owner for every system, yet few write down what that person must actually do, so reviews go to IT by default, service accounts outlive their projects and nobody signs off when an application is switched off. The application owner is the accountable business person for an application across its whole life: whether it is onboarded to governance, who may hold which access, which combinations are forbidden, whether access reviews are meaningful and whether every account and credential is removed when it retires. This guide sets out those duties as a RACI across the lifecycle, separates them from the entitlement owner, system owner and IT administrator roles, and shows how to roll the role out and measure it. It is written for IGA leads, identity architects, internal audit and the business owners themselves.
Key takeaways
- Accountable, not hands-on. The application owner decides and signs off; administrators, IGA teams and entitlement owners carry out the work. One accountable person per application, with a named deputy.
- Policy before tooling. Who may request each role, who approves, how long access lasts, which roles conflict and how often access is reviewed are business decisions the owner records before any connector is built.
- Non-human accounts are in scope. Service accounts, API keys, integration users and signing keys belonging to the application need the same owner attestation as human access.
- Remediation is part of the review. A certification is complete when revoked access is actually removed and evidenced, not when the owner clicks submit.
- Decommission is a governed event. Retiring an application requires the owner to confirm removal of accounts, entitlements, credentials and integrations, and to hand over records for retention.
Who the application owner is, and who they are not
NIST defines an information owner as the official with statutory or operational authority for specified information and responsibility for establishing the controls for its generation, collection, processing, dissemination and disposal. In access governance the application owner is that person for one application: usually the business head of the function the application serves, senior enough to accept risk and to say no. Four roles are routinely confused:
| Role | Question they answer | Typical holder | Must not be |
|---|---|---|---|
| Application owner | Should this application exist, who should use it and on what terms, and is the residual access risk acceptable? | Business head of the served function | A team mailbox, the vendor, or an IT administrator of the same system |
| Entitlement owner | Is this specific role or permission correctly described, rated and held by the right people? | Process or data owner, often reporting to the application owner | Someone who cannot judge the business effect of the access |
| System or technical owner | Is the application running, patched, connected and configured as decided? | IT service owner or platform lead | The final approver of their own administrative access |
| IGA or identity team | Are the processes, connectors and evidence working across all applications? | Central identity governance function | The default reviewer when an owner is missing |
The entitlement-level role, descriptions and risk ratings are covered in the Entitlement Catalogue Guide. This page covers the application-level role across the lifecycle.
RACI across the access lifecycle
R = responsible (does the work), A = accountable (signs off), C = consulted, I = informed. Adapt the column names to your organisation, but keep exactly one A per row.
| Activity | Application owner | Entitlement owner | System owner | IGA team | Security and audit |
|---|---|---|---|---|---|
| Decide to onboard the application to governance and set its risk tier | A | C | C | R | C |
| Define access policy: who may request, approval stages, duration | A | R | C | C | C |
| Describe and risk-rate entitlements | A | R | C | C | I |
| Define SoD conflicts and mitigating controls | A | R | C | C | C |
| Approve high-risk or privileged access requests | A | R | I | I | I |
| Provision and deprovision accounts | I | I | R | A | I |
| Certify user and privileged access | A | R | C | C | I |
| Remediate revoked access and evidence it | A | I | R | R | I |
| Own and attest service accounts, API keys and integrations | A | C | R | C | C |
| Approve SoD and policy exceptions | A | C | I | R | C |
| Decommission the application and confirm removal | A | C | R | R | C |
For non-human accounts on their own, the NHI Ownership RACI gives a ready template.
Onboarding: decisions the owner makes before the connector
- Risk tier: the owner confirms data sensitivity, regulatory scope (financial reporting, payment card, health data) and business criticality. The tier sets review frequency, approval stages and whether privileged access goes through PAM.
- Access populations: for each role, who is eligible (department, employee type, contractor or guest), who approves and for how long. A common pattern is manager approval for the core team, an additional owner approval for people outside it, and a 30 or 90 day limit for contractors and temporary access.
- Authoritative account source: the owner and system owner agree which accounts are expected, including local administrators and service accounts, so that the first aggregation can be reconciled and orphans flagged.
- Baseline review: before the application enters routine governance, the owner certifies every existing account once, so later reviews start from a known-good state.
- Deputy and succession: a named deputy, and an automatic reassignment rule when the owner leaves or moves.
The connector, aggregation and catalogue mechanics are in the Entitlement Catalogue and Application Onboarding Guide.
Requests, approvals and separation of duties
- Approval design: the owner decides where their own approval adds judgement (high-risk, privileged, out-of-population requests) and where a manager approval is enough. Owners who approve everything become a bottleneck and start approving without reading. See the Access Request and Approval Workflow Design Guide.
- Conflicting roles: the owner lists pairs of roles within the application that one person must not hold (for example create supplier and approve payment), and cross-application conflicts with the owners of the other systems. These become preventive checks at request time and detective checks in reviews. See the Segregation of Duties Guide.
- Exceptions: where a conflict must be allowed, the owner approves it with a named mitigating control (for example a monthly review of transactions by the conflicting user) and an expiry date. Exceptions without expiry become permanent policy.
- Emergency access: the owner approves who can use break-glass or firefighter accounts in the application and reviews every use afterwards. See the Break-Glass Account Guide.
Access reviews: what the owner owns
The mechanics of campaigns, reviewer interfaces and evidence are covered in the Access Reviews Guide. The owner's part is narrower and more important:
- Reviewer model: decide whether managers, entitlement owners or the owner review each population. IDPro's guidance suggests managers for their teams, entitlement owners for sensitive privileges, and system or application owners where roles are few or unstructured.
- Frequency by risk: IDPro suggests quarterly reviews for high-risk or privileged access, semi-annual for moderate and annual for low risk, with event-driven reviews after role changes, terminations, mergers or incidents. The owner confirms the tier and any regulatory minimum.
- Reviewer context: insist that reviewers see when and why access was granted, last use, peer comparison and risk rating; without that context reviewers rubber-stamp.
- Sign-off and remediation: the owner attests completion only when revocations are executed and evidenced in the target system. Auditors check timeliness of remediation and the records that prove it.
- Non-response: agree in advance what happens if a reviewer does not respond (escalation to the owner, then removal for high-risk access), so silence never means approval.
Where identity fits: non-human accounts and credentials
Every application has identities that no manager will ever review: service accounts, database logins, integration users, API keys, OAuth clients and signing keys. The application owner is the natural accountable party for them, with the system owner responsible for day-to-day custody. The owner should attest at least annually that each one is still needed, has the minimum privileges, has a named technical custodian and has a rotation date. When an engineer with access to those credentials leaves, the owner's leaver checklist must trigger rotation, not only the disabling of the person's login. In the Coupang breach, investigators found that a token signing key obtained by a developer was never revoked or rotated after he left, and he used it to forge customer access tokens months later. See the NHI Ownership Guide and How to Run an Access Review for Service Accounts.
Movers, leavers and decommission
- Movers: the owner defines which roles are tied to a job or department so a move triggers removal or review, rather than accumulation. NIST SP 800-53 AC-2 requires notifying account managers when users are transferred or when need-to-know changes, and PS-5 requires reviewing access on transfer.
- Leavers: account removal is automated by the IGA team, but the owner confirms that application-local accounts, shared accounts and credentials known to the leaver are covered. AC-2 also requires changing shared or group account authenticators when individuals are removed from the group. See the Joiner-Mover-Leaver Guide.
- Owner departure: ownership transfers to the deputy automatically on the owner's leaver event, and the new owner re-attests the application within a set period.
- Decommission: the owner signs a retirement record confirming that user accounts, entitlements, service accounts, API keys, OAuth grants, SSO and SCIM integrations and firewall or network rules for the application are removed; that the catalogue entries are retired; and that access logs and review evidence are retained for the required period.
Rolling out the role
- Write the role description. One page: accountability, decisions, time commitment and the RACI above, approved by the risk or governance committee so owners cannot decline it informally.
- Assign owners to the top tier first. Start with applications in financial reporting, payment card, health data or privileged infrastructure scope, then work down. Record owner and deputy in the CMDB or IGA application record.
- Brief owners on their decisions. A short working session per application to capture access populations, approvals, SoD pairs and review tier is more effective than an emailed questionnaire.
- Pilot with three to five applications. Run one baseline review and one approval cycle, measure time spent and revocation rates, and adjust the reviewer model before scaling.
- Automate ownership hygiene. Detect owners who have left, moved or hold no management role, and route reassignment to the deputy and the IGA team.
- Report and escalate. Publish owner coverage and overdue actions to the governance committee each quarter; persistent non-performance goes to the owner's executive.
Decision guidance
| Situation | Approach |
|---|---|
| Small organisation, few applications | One owner may hold application and entitlement owner roles; keep the system owner separate from approval of their own admin access |
| Large estate with hundreds of applications | Tier applications; full owner duties for high-risk tiers, lighter manager-led reviews and annual owner attestation for low-risk tiers |
| SaaS application managed by a business team | The business team lead is owner; the vendor is never owner. Add OAuth grants and API tokens to the owner's attestation |
| Shared platform (ERP, data warehouse) | One application owner for the platform, entitlement owners per module or data domain, cross-module SoD agreed jointly |
| Application with no willing owner | Escalate to the business executive; if nobody accepts accountability, treat it as a candidate for retirement |
Detection and measurement
- Ownership gaps: applications whose owner is disabled, has left, has moved department or is a non-person account.
- Review quality: approval rates near 100% with very short decision times per item indicate rubber-stamping.
- Remediation lag: revoked items still present in the target system after the agreed deadline.
- Unowned non-human accounts: service accounts and keys mapped to the application with no custodian or rotation date.
| Metric | What good looks like |
|---|---|
| In-scope applications with a named owner and deputy who are both active | 100% of high-risk tier, rising across others |
| Reviews completed on time by owner-assigned reviewers | Above 95% |
| Revoked access removed within the remediation deadline | Above 95%, with evidence |
| SoD exceptions with a mitigating control and expiry date | 100% |
| Non-human accounts per application attested in the last 12 months | 100% of high-risk tier |
| Decommissioned applications with a signed retirement record | 100% |
Common failure patterns
- IT as default owner: administrators certify their own users and their own admin rights, which defeats separation of duties and gives auditors a finding.
- Owner by job title that no longer exists: ownership recorded against a person who left, so reviews route to an empty mailbox or to the IGA team.
- Approving everything personally: owners who insist on approving every request create backlogs and then approve in bulk without reading.
- Human-only reviews: certifications cover employee accounts but skip service accounts, API keys and integration users the application depends on.
- Submit without remediation: campaigns marked complete while revoked access remains in the target system.
- Silent retirement: an application switched off without removing its service accounts, OAuth grants and firewall rules, which then remain usable against shared infrastructure. See Orphaned and Dormant Accounts.
Framework mapping
| Framework | Reference | Owner duty it supports |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 Account Management | Approvals for account creation, assigned account managers, periodic account review, alignment with termination and transfer |
| NIST SP 800-53 Rev 5 | AC-5 Separation of Duties | Documented conflicting duties and access authorisations that support them |
| NIST SP 800-53 Rev 5 | AC-6(7) Review of User Privileges | Periodic validation of privileges and removal where not needed |
| NIST SP 800-53 Rev 5 | PS-4 Personnel Termination; PS-5 Personnel Transfer | Leaver and mover access actions |
| NIST CSF 2.0 | GV.RR-02 | Cybersecurity roles and responsibilities established and enforced |
| NIST CSF 2.0 | PR.AA-05 | Access permissions defined in policy, reviewed, least privilege and separation of duties |
Practitioner checklist
- Publish a one-page application owner role description with the lifecycle RACI, approved by the governance committee.
- Record an active owner and deputy for every in-scope application, starting with the highest risk tier.
- Capture access populations, approvers, durations and SoD pairs with each owner before onboarding the connector.
- Run a baseline certification of all existing accounts when an application enters governance.
- Set review frequency by risk tier and define non-response escalation in advance.
- Require evidence of remediation before a review can be signed off.
- Add service accounts, API keys, OAuth clients and signing keys to the owner's annual attestation, with rotation triggered by relevant leavers.
- Reassign ownership automatically on owner leaver and mover events.
- Require a signed retirement record for every decommissioned application.
Standards and references
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
- NIST: Cybersecurity Framework 2.0
- NIST CSRC Glossary: Information owner
- IDPro Body of Knowledge: Optimizing Access Recertifications
- Microsoft Learn: Define organisational policies for governing access to applications
- Microsoft Learn: Access reviews overview
Related NHI Mgmt Group resources: Entitlement Catalogue Guide · Access Reviews Guide · Access Request and Approval Workflow Design Guide · Segregation of Duties Guide