India · DPDP Act
—days to go
Core duties become binding on 13 May 2027.
Penalties of up to ₹250 crore. Knowing who and what can reach personal data is where the evidence starts.
Source: SCC Online, 2025
Anoryx Research
Every company keeps a list of its employees. Almost none keep a list of everything else that can log in, spend money or read data on their behalf.
Actors that can log in
6 shown · 4 with no owner
Priya N.
Employee · Finance
svc-billing-sync
Service account · Created 2023 · never reviewed
invoice-agent
AI agent · Can draft and send email
gh_pat_…7f2
API token · Admin on 41 repos · unused 214 days
notes-ai
Shadow AI app · Reads mailbox · not approved
K. Iyer
Left in August · Supplier portal still works
Definition
Identity debt is what builds up when a company does not know every actor that can act inside it, what each can reach, and who is accountable for it.
Like technical debt, it accumulates silently and is paid with interest during an incident. The credentials rarely do anything unusual. They simply still work.
The access model
An actor presents a credential to obtain a permission. Behind each actor there should be an owner who answers for it, and a lifecycle: created for a reason, used, reviewed, retired.
Actor
Who or what is acting?
Priya, accounts payable
Credential
What does it present?
SSO login with MFA
Permission
What can it do?
Approve invoices up to a limit
Owner
Which human answers for it?
Her line manager, via HR
Lifecycle
Created, reviewed, retired?
Joiner → mover → leaver
Security programmes have perfected all five parts — for people.
One root cause, three symptoms
Each looks like a separate problem with a separate budget. Underneath, it is one question nobody can answer: what exactly do we have, and who owns it?
API keys, OAuth tokens, service accounts and AI agents acting on a manager’s authority — created for a reason nobody wrote down.
A factory that hands spare keys to every contractor, delivery robot and cleaning crew, never writes down who has which key, and never changes the locks.
Shadow IT and shadow AI: tools adopted because the approved path is slow, now holding company data no one has mapped.
Workers who bring their own power tools and extension cords onto the shop floor because the approved ones take three weeks to order. Productive, until one sparks.
Offboarding closes the obvious doors. The supplier portal, the shared admin login and the tokens they created stay open.
An employee hands in their ID card on the last day but keeps the master key, the garage remote and the password to the supplier portal.
By the numbers
82–0
machine identities for every human identity
CyberArk, 2025 · Palo Alto Networks, 2026
0%
of former employees still had an account that worked
Sagiss 2026 via HRD Australia · indicative
0%
of secrets leaked on public GitHub in 2022 were still valid four years later
GitGuardian, 2026
+$0K
added to the average breach where shadow AI use is high
IBM, 2025
Figures are drawn from the sources named; several are vendor-sponsored surveys. Ranges are shown as ranges.
Why it is ignored
If the evidence is this strong, why does nearly every organisation carry identity debt? Because the incentives point the other way.
An orphaned token costs nothing until it is used. Budgets fund visible costs; identity debt is invisible by construction.
DevOps creates service accounts, business units buy SaaS, HR owns the leaver event. A problem owned by everyone is managed by no one.
When ‘privileged user’ means a person, the largest population of privileged actors falls outside the programme.
Shadow tools and quick integrations deliver real speed today. The risk is probabilistic and deferred.
Every organisation has credentials it assumes are dead. Attackers only need one that is not.
What good looks like
The controls are well understood. The hard part is building and maintaining a truthful inventory with owners — and keeping it true as people, tools and agents change every week.
A continuously updated inventory of every actor: human, machine, agent and shadow app.
Every actor linked to a named human who answers for it — and re-assigned when that person moves.
Permissions trimmed to what is actually used, not what was granted on day one.
Tokens that expire by default, so a forgotten key stops working on its own.
Keys rotated on schedule and actors retired when their purpose ends — including the leaver’s machine footprint.
Every AI agent registered with its delegating human, its scope and an expiry date.
The regulation clock
Neither law says ‘identity debt’. Both expect you to show who and what can reach the data and systems you are responsible for.
India · DPDP Act
—days to go
Penalties of up to ₹250 crore. Knowing who and what can reach personal data is where the evidence starts.
Source: SCC Online, 2025
Germany · NIS2
—days in force
More than 30,000 entities are in scope. The directive lists access control among the risk-management measures it requires.
Source: Scheja & Partners, 2026
How Anoryx helps
Start with a fixed-scope assessment that tells you where you stand. Keep the map current, inside your own infrastructure, with Sentinel.
Read-only discovery, an ownership map, a risk register, a DPDP / NIS2 / ISO 27001 evidence gap list and a remediation roadmap. Nothing in your environment changes while we look.
How the assessment worksFind every key, bot, AI agent and shadow AI app. Give each one an accountable owner. Prove it to your auditor. An ownership control plane for non-human identities that runs inside your infrastructure.
Explore SentinelFigures on this page are drawn from the sources named; several are vendor-sponsored surveys. Anoryx produces audit-ready evidence that maps to these regulations; it does not certify compliance.
Start with a read-only Identity Debt Assessment. You keep the map, the register and the roadmap, whatever you decide next.