Nov 17 / Briefings

Access Should Not Live Forever: Fixing the Identity Crisis

Executive Summary

Most organizations are good at granting access and poor at taking it away. Over time, entitlements pile up, service accounts outlive their purpose, and access reviews become spreadsheet exercises that nobody can audit. The fix the session laid out is a single principle applied through three disciplines: access should exist only for as long as the business needs it, enforced through lifecycle automation, attestation, and delegation to business owners.

For executives and the board, this is a matter of control and proof. The classic audit question, "who had access to system X on date Y, and who approved it?", should be answerable in minutes, not days. Standing access that no one owns is a security exposure, a compliance gap, and often a licensing cost. A governance model that cannot show who decided, why, and for how long leaves leadership accountable for decisions it cannot see.

These findings were taken from the webinar IGA in Action: A Practitioner's Guide to Modern Identity Governance, which featured Chris Martin, Identity Solutions Architect at Netwrix, and Maurice Lethbridge, Senior Solutions Engineer at Netwrix. The session explained why identity programs drift, how lifecycle automation, access reviews, and delegated approvals close the gaps, and included live demonstrations of each process in Netwrix Identity Manager.

Critical Takeaways:
  • Access Needs an Expiry Date: Every entitlement, role, and account should exist only while it serves a business purpose. Project and elevated access should be time-bound by default, with renewal as a deliberate action.
  • Removal Is the Weak Link: Organizations are good at creating access and poor at removing it, so entitlements only grow. Lifecycle management makes the end of access as automatic as the beginning.
  • Automate the Obvious, Escalate the Exceptions: Rules built on trusted data (HR, directories, applications) should handle routine access, leaving human decisions for genuine exceptions. The help desk should not be the gatekeeper.
  • Delegate With Guardrails: Business owners make better access decisions than a central team, but only within clear limits on scope, time, and proof. Reviews and approvals must leave evidence of who decided, why, and until when.

1. The Identity Crisis Hides in Plain Sight

Martin listed the familiar signs of an identity problem: a leaver who still has a working login a month after announcing a new job, new starters given "the same permissions as Sarah" (who has accumulated everything over 12 years), access reviews run from color-coded spreadsheets that cannot be audited, and a service account with administrative privileges that nobody dares disable. He described that last case as the non-human identity equivalent of the leaver who never left, and argued that human and non-human identities need the same governance.

None of these problems causes a visible incident on its own, which is why they persist.

"Now, none of these will feel like a crisis on any given Tuesday. Day-to-day, you can live with these, and that's exactly why they're dangerous." — Chris Martin, Identity Solutions Architect at Netwrix


Attendees were asked to rate their own identity maturity:

POLL: How would you describe your organization's current identity maturity?
We have some lifecycle automation, but governance is inconsistent 32%

We have a mature identity governance program with automated policy-driven controls 28%

We are primarily using manual processes and tickets 26%

We only focus on access reviews, but do not have any lifecycle controls 14%

Fewer than three in ten respondents described a mature, policy-driven program. Seven in ten reported partial automation, manual ticket-driven processes, or reviews with no lifecycle controls behind them. Martin called the spread typical, and noted that many leaders who claim privately to run a mature program do not believe they have a problem, so he welcomed the audience's more candid self-assessment.

2. Access Should Not Live Forever

The principle Martin said he follows in every implementation is that access should exist only while it is useful to the business. Every entitlement has a lifespan: it begins when there is a genuine business reason and should end when that reason is gone. Companies handle the "create" stage well and the "delete" stage badly, so access only grows. Lifecycle management means making removal as automatic and reliable as provisioning: baseline access on day one, old access switched off when someone changes role, and immediate deprovisioning when they leave.

"Access should not live forever. It is such a simple principle that turned out to be quietly radical." — Chris Martin, Identity Solutions Architect at Netwrix


He argued that every access should come with a clock. Users get basic entitlements on day one. Everything else should be requestable, approved by a business owner, and time-bound, so that it lapses unless renewed. Martin also pointed to measurable side benefits: real-time visibility of who has what, both now and in the past; faster large-scale changes (in his example, onboarding 150 interns dropped from a week of copy-and-paste work to about 10 minutes); and license savings when dormant accounts and expired access are cleaned up.

Attendees were then asked where their greatest identity risk lies:

POLL: Which identity governance challenge creates the most risk in your organization today?
Excessive or outdated access (entitlement creep) 38%

Lack of visibility into who has access to what 30%

Manual joiner/mover/leaver processes 23%

Difficulty proving compliance during audits 9%

Entitlement creep was the top concern, followed by lack of visibility. Martin said he was surprised that difficulty proving compliance ranked so low, since in his experience it is usually much higher and tends to stem from the same lack of visibility. He also cautioned that the four options are interlinked: an organization with one of these problems usually has all of them.

"When it comes to delete, we are terrible. Every company is terrible. No one is rewarded for handing access back." — Chris Martin, Identity Solutions Architect at Netwrix


3. Automate the Obvious and Take the Help Desk Out of the Gate

Martin argued that people are inconsistent access decision makers. They want to be helpful and are unlikely to say no when unsure. A help desk acting as gatekeeper will approve requests to clear the queue without knowing why the access is needed, and those permissions tend to stay. Decisions that genuinely need a human belong with the business owner, who has the relevant context. Most access should never reach a human at all.

The model he described is a funnel. Trusted facts flow in from HR, directories such as Active Directory, project databases, and the applications themselves. Readable rules turn those facts into the right memberships and entitlements. The steps are: link each person's accounts into one identity; write policies in plain language that the business can own; simulate rules before enforcing them; attach an owner and an expiry to every non-baseline grant; and log every change. Linking also has to cover non-human identities (service accounts, bots, and break-glass admin accounts), correlated on immutable identifiers rather than names or email addresses, which change. Martin noted that non-human identities are typically the biggest blind spot.

In the joiner, mover, and leaver demonstration, Lethbridge showed a new hire provisioned from an HR record, a role change that moved access, and a departure that removed it. Each step ran through tracked workflows rather than service desk tickets.

"And this is what automation looks like at an enterprise scale, not just faster, but accountable." — Maurice Lethbridge, Senior Solutions Engineer at Netwrix


4. Attestation: Proving Access Still Has a Job to Do

If lifecycle management grants access correctly, attestation checks that it stays correct and catches the drift that builds up over time. Martin described access reviews as a continuous loop rather than an annual chore. Owners review a short, meaningful list of current members and permissions and answer one question: is this still needed? Over-scoped roles are tightened and made time-bound. Every decision is recorded with who approved it, why, and when.

Review cadence should match risk: quarterly for high-risk applications and privileged roles, about twice a year for moderate applications, annually for low-risk baseline entitlements, and ad hoc after incidents or audit failures. Every item must be reviewed individually rather than bulk-approved. The right reviewer should be assigned, reminders sent, and stubborn items escalated. In the certification demonstration, Lethbridge showed reviewers confirming or revoking access in a portal, decisions becoming part of the permanent record, and administrators pushing revocations through the provisioning process.

"Access reviews, just consider them a spring cleaning with receipts." — Chris Martin, Identity Solutions Architect at Netwrix


5. Delegation With Scope, Time, and Proof

The third discipline is delegation. Automation should handle the routine majority of access decisions, and the exceptions should go to the people who understand the work, within three guardrails. Scope defines who the owner is, what they can approve, and for whom. Time means every approval has a default duration. Proof means a record of who approved, for what reason, and when the access expires. Martin called delegation a force multiplier: a security team of a handful of people cannot match the knowledge of many business managers, and the central team becomes the group that sets the rules and watches for risk instead of acting as a gate.

He stressed that delegation only works with time-based policies behind it: a contractor might get finance access for 90 days, and it lapses automatically unless someone deliberately renews it. Attendees were asked who makes access decisions today:

POLL: Who makes most access decisions in your organization today?
Business managers/resource owners 38%

Shared responsibility across multiple teams 27%

IT administrators 15%

Application owners 14%

Help desk/service desk 6%

Business managers and resource owners were the most common answer, and only about one in five respondents said IT administrators or the help desk make most decisions. Martin said this surprised him in a good way, since IT normally ranks high on this question. He added that in many organizations a line manager approves the initial request but the decision still passes to IT. The final demonstration showed a user requesting access from a catalog with a start and end date, and the request routed to the user's manager as the delegated approver.

"Delegation without the safety net just spreads the rubber stamping around." — Chris Martin, Identity Solutions Architect at Netwrix


Strategic Roadmap

  • Make Time-Bound Access the Default: Keep baseline access durable. Make project, elevated, and contractor access requestable, owner-approved, and set to expire unless renewed, so that the default outcome is removal.
  • Build Lifecycle Automation on Linked, Trusted Identity Data: Bring every identity store and non-human identity into scope, correlate accounts on immutable identifiers, express access policies in plain language, and simulate rules before enforcing them.
  • Run Risk-Based Attestation and Delegated Approvals With Evidence: Set review cadence by risk, assign the right reviewer for each item, prohibit bulk approvals, and give business owners scoped, time-limited approval rights that record who decided, why, and until when.

To dive deeper into the topics discussed today, access the recorded webinar: IGA in Action: A Practitioner's Guide to Modern Identity Governance.