Security has industrialized almost everything except the decision
We discover applications automatically. We provision identities automatically. We detect anomalies, correlate signals, and generate evidence at machine speed. What no tool does at machine speed is answer the question that every one of those controls eventually depends on: who is the named human accountable for this application, and did they agree to be?
That sounds like an administrative question. It is a control question. An access review without an accountable reviewer is a signature, not a control. An offboarding process without an application owner is a checklist that stops at the identity provider. An audit finding about stale access is almost never a finding about the scanner. It is a finding about the fact that nobody was assigned.
This paper argues that application ownership is not metadata attached to a security program. It is the precondition for the program working at all, and the largest unmanaged control layer in most security organizations today.
What we mean by owned
A named individual, currently employed, who took an affirmative action accepting accountability for a specific application, timestamped in an audit log that another human can read. An owner inferred from usage data who has not accepted does not count. A distribution list does not count. "IT" does not count. The strictness is what makes the number credible.
Part I. The gap
Discovery is the first twenty percent
Discovery works. Browser telemetry, OAuth grant analysis, expense feeds, and identity provider logs will find applications your inventory does not have. What discovery produces is a list, and a list is not accountability.
After an application appears on the list, someone has to decide whether to keep using it, who can have access, who answers when a review lands or a vendor discloses a breach, and who signs off when it is retired. None of those are discovery problems. All of them are ownership problems. In the absence of an owner, each one defaults to the security team.
Discovery is the easy 20 percent. Someone has to own approval and offboarding, or you're back to 94 apps in six months. (Managed service provider, r/msp, May 2026)
Where identity governance stops
Identity governance reasons from the identity outward: given a user, what do they hold, and is it appropriate? That model is useful, and it has three blind spots here.
- Applications outside the identity fabric. Certifications cover what is connected. Apps without SCIM, apps bought outside procurement, and apps with local logins are out of scope.
- Single sign-on deletion is not deprovisioning. Deleting the directory account breaks the login path. It does not always terminate the account inside the app.
- The manager is the wrong reviewer. The default campaign routes to the user's manager, who knows the person and frequently does not know the resource.
Owner as a field, owner as an object
Most organizations already have an owner field somewhere. A field is populated once, often by someone who is not the owner, and rarely again. It has no acceptance event, no expiry, no health state, no escalation path, and no audit trail. An object has all of them.
| Owner as a field | Owner as an object | |
|---|---|---|
| Origin | Entered or inferred | Proposed, then accepted |
| Proof | A name in a cell | A timestamped acceptance record |
| Freshness | Decays silently | Has a health state and an expiry |
| Non-response | Nothing happens | Escalates on a defined path |
| Departure | Field goes stale | Triggers reassignment |
| Audit | A screenshot | A queryable history |
Part II. How ownership fails
Ownership does not fail randomly. It fails in recognizable ways, each predictable enough to design against.
- Rot on role change. Someone moves teams or leaves, and the record still points at them.
- The rubber stamp. Reviewers approve in bulk because they are reviewing resources they do not own.
- Local and non-federated accounts. Accounts created inside an app are invisible to identity governance by construction.
- Offboarding that stops at the directory. The runbook covers the identity provider and the top ten apps, not the long tail.
- Dormancy. Dormant credentials are live authentication paths nobody is watching.
- Non-human identities and AI agents. Every service account, API key, and agent needs an accountable human. Most do not have one.
- Configuration database decay. Entered once, trusted by nobody.
- Post-audit drift. Enforced during the audit, gone two months later.
- Shadow purchase. Apps on personal cards never appear in sign-in data.
- Shadow governance. Owners who care build their own controls outside the process.
51 percent of organizations report no clear ownership or accountability for non-human and AI identities (CSA and Oasis Security, published January 2026).
Part III. Why the current stack does not fix this
A useful test for any tool: what is the primary object in its data model? Whatever that object is, the product governs it well and treats everything else as an attribute. Attributes do not get lifecycles. They get fields.
- Identity governance governs the identity. The application owner is optional metadata.
- SaaS management governs the application as a cost center. The owner is configured, not guaranteed.
- Compliance automation governs the campaign. Ownership is re-established every cycle and gone between them.
- Configuration databases govern the configuration item. Nothing notices the owner left.
- CASB, DLP, and posture tools govern the finding. A finding without an owner is a queue entry.
- Just-in-Time platforms reduce what needs review, and still need someone to approve the request.
- Spreadsheets and email have no primary object at all.
Validating ownership, getting a named person to accept, is the stage no category requires. It is the one every other stage depends on.
Part IV. What the regulators actually say
The regulatory picture is narrower and sharper than most vendor claims suggest.
| Framework | Requires an owner | Requires periodic access review |
|---|---|---|
| FFIEC IS booklet II.C.7(b), supervisory guidance | Yes, explicitly | Yes, by application owners |
| NYDFS 500.13(a), binding regulation | Yes, as a tracked attribute | Via 500.7(a)(4) |
| ISO/IEC 27001:2022 A.5.9 | Yes, in the inventory | Via other controls |
| SOC 2 CC6.2 and CC6.3 | No | Auditor expectation, not text |
| PCI DSS 4.0.1 Req. 7.2.4 | No | Yes, every six months |
| SOX via COSO and AS 2201 | No | Audit practice, not statute |
| CIS v8.1 Safeguard 6.8 | No | Yes, at minimum annually |
SOX does not name application owners. Auditors do, because someone has to sign the access review.
Part V. The Ownership-Driven Security model
Ownership-Driven Security establishes ownership as a primary security control: every application, integration, service account, API key, and non-human identity has a verified owner accountable for its lifecycle. Ownership is continuously monitored, periodically certified, and updated as the organization changes.
The ownership lifecycle
- Discover. Find applications and identities from more than one signal.
- Classify. By criticality, data sensitivity, department, and risk.
- Identify ownership. Propose the most probable owner. A proposal and nothing more.
- Validate ownership. The owner affirmatively accepts. This is the stage everyone else skips.
- Govern. The owner reviews access and approves changes.
- Monitor. Watch for departures, moves, dormancy, and missing certifications.
- Certify. Re-verify ownership itself, not only access.
- Retire. Keep the history, because audit periods look backward.
Three-way certification
One reviewer cannot hold all three facts a correct access decision needs.
- The application owner knows how the application is used.
- The manager knows why the employee needs it.
- The employee knows whether they actually use it.
Splitting the decision does not cure the rubber stamp. It raises the cost of a careless approval, which is the most any process design can honestly claim.
The owner's charter
Nobody accepts an unbounded obligation. Know the application, control who has access, keep it compliant, manage the lifecycle, and transfer accountability before you move on. A reasonable target is about fifteen minutes per application per quarter.
Part VI. Running the program
What to measure
- Accepted ownership coverage. In-scope apps with a current owner who accepted. The headline number.
- Ownership decay rate. Coverage lost per month without intervention.
- Mean time to reassign. Days from an owner leaving to a new owner accepting.
- Access removals per campaign. A campaign that removes nothing is not a review.
- Non-human identities with an accountable human. As a share of all discovered.
The first ninety days
- Days 1 to 14. Connect the identity provider, pull OAuth grants and expense data, and lock the baseline set.
- Days 15 to 30. Classify and propose owners, starting with the riskiest quartile.
- Days 31 to 60. Collect acceptances, routed from an internal leader, with escalation on a published schedule.
- Days 61 to 90. Run one real review with accepted owners, then wire the triggers: departure, department change, dormancy, and non-response.
A note on AppGovern
AppGovern is building the ownership layer described in this paper: ownership as a first-class object with an acceptance event, a health state, a risk score, an escalation path, and an audit trail, with access reviews routed to accepted owners. We do not have public reference customers yet, and we would rather say that than imply otherwise.
Statistics are attributed to their publishing organization and edition. Regulatory text was checked against primary sources where publicly available. Practitioner quotations come from discovery interviews, identified by role, and from public forum threads quoted as written. The full 44-page paper, with sources, is available on request.