Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Glossary. Stale access.

What is stale access, and how long is too long?

Stale access is a grant nobody has used in a period you set. Where the source keeps no record of use, the right entry is “not measured”.

By Dipal Panchal, co-founder and CEO · Updated November 7, 2026

A grant, a period and a last-used date

Stale access is a permission that is still granted but hasn’t been used for longer than a period you have written down. Unlike excessive access, which is broader than the job needs, stale access may be exactly the right size for a job that ended. Calling a grant stale takes a record of its use, and where the source keeps none, the entry is “not measured”.

The account can still read or change the data after the need has gone: people change teams, projects end and service accounts outlive the jobs they ran.

Six grants against a ninety-day period

Reviewed by the data owner on November 7, 2026. Rows 1 to 4 and 6 come from a warehouse whose access record covers the past year; row 5 comes from a PostgreSQL database.

Records
IdentityRole or groupObjectPrivilegeLast usedDecision
m.osei@example.comanalysts_ukfinance.invoicesSELECTOctober 30, 2026Keep: used within the ninety-day period
r.iyer@example.commarketing_incrm.contactSELECTJune 12, 2026Remove: unused since June, when the analyst moved to the product team
svc_month_end (service account)finance_batchledger.close_entriesSELECT, INSERTOctober 31, 2026Keep: a monthly job, held to its own period of six weeks
breakglass_dbaemergency_adminEvery schemaAll privilegesNo use in the past yearKept disabled until needed, since the warehouse is in PCI DSS scope; every use raises an alert and is reviewed
app_reporting (shared login)reportinghr.salarySELECTNot measuredOwner review: PostgreSQL statistics don’t say which login read the table, and a shared login hides the person
k.lee@example.compos_supportpayments.cardholderSELECTJuly 1, 2026, also the last sign-inDisable the account: in PCI DSS scope and past 8.2.6’s ninety days since September 29; raised as an exception

Why row 5 says not measured

PostgreSQL’s cumulative statistics count scans per table, and they don’t record which login ran them. A shared reporting login could be read daily by one analyst or never by anyone, and the statistics can’t tell those apart. Reads by database account need audit logging turned on, and even then a shared login hides the person behind it. From PostgreSQL 16 the statistics also keep the time of each table’s last scan; before that they are counters only.

“Not measured” sends the grant to its owner, who knows whether the report still runs. “Unused” or “used” in that row would both be guesses.

Set the period by type of access

NIST SP 800-53 control AC-2(3) leaves the inactivity period to you; PCI DSS doesn’t, for accounts in its scope. The other periods are Sylox’s recommendation.

Set the period by type of access
Type of accessPeriodWhy
User accounts in PCI DSS scopeRemoved or disabled within ninety days of inactivityPCI DSS v4.0.1 requirement 8.2.6 sets it
People with access to other sensitive dataNinety days without useCovers monthly work; quarterly roles need a quarter plus a margin, and the person can ask again
Service accounts for scheduled jobsOne run cycle plus a margin: six weeks for a monthly jobA shorter period flags a healthy job as stale
Emergency (break-glass) accountsOutside PCI DSS scope, excluded by written exception; in scope, kept disabled until neededThey are meant to sit unused; alert on every use
Contractors and project accessThe contract or project end date, or the ninety-day period if that comes firstThe need ends on a known day; unused access can still go stale earlier

The rule of thumb behind ninety days

Dipal Panchal, Sylox’s co-founder and CEO, gives the rule of thumb behind the ninety-day periods above. On an advisory call in 2026 he said, “If that person has not logged in for ninety days, chances are they are never going to log back again. If they want it again, go ahead and make an access request.”

He also looks outside the data source for signs: people HR lists as gone, and people who changed teams but kept their old application’s access. Row 2 is the second case, and it surfaced only because the warehouse records each user’s reads.

Stale access and dormant accounts

A dormant account hasn’t signed in at all, and identity tools see it in sign-in logs. Stale access is finer: it asks about one grant, so it also catches an account that is busy elsewhere and never touches this table.

The check needs activity data from the data source itself, not from the identity provider. Row 6 is both at once, since its last read was also its last sign-in, and the decision lands on the account rather than the grant.

When the activity record goes blank

Activity counters can start again from empty. PostgreSQL resets its statistics after a crash and when a server starts from a base backup or point-in-time recovery, so a restored host can make busy grants look unused. Reads served by a standby are counted on the standby, not the primary, so record when the counters last reset before you trust a quiet table.

Retention ends the record too: Snowflake keeps ACCESS_HISTORY for one year, and only on Enterprise Edition or higher. And a read made through an application’s service account shows as the service account, whichever of the application’s users asked for the data.

With IRIS

IRIS flags access left unused past the 90-day default, or a period you set, where the source provides activity data. Capabilities vary by edition.

Grants with last use against the 90-day default or your period: IRIS produces part of this, for PostgreSQL, Snowflake and BigQuery; on PostgreSQL, per database account unless audit logging is on.

A reviewer’s decision on an identity’s access to a source, with a reason: IRIS produces this.

The removal in the source system: Not produced by IRIS.

A dated re-scan after the removal, run on demand or on a schedule: IRIS produces this.

Explore access mapping

Write the periods down before the review

Before the next review, agree a period for each type of access in the table above, name who approved it and keep that record with the review. Then check every grant against its own period, and mark the ones with no activity record as not measured before anyone decides.

For the queries on PostgreSQL and SQL Server, see how to find stale access.

Official sources

  1. NIST SP 800-53 Rev. 5, control AC-2(3) Disable accounts, NIST. Opened November 7, 2026.
  2. PCI DSS v4.0.1, requirement 8.2.6 (inactive user accounts), PCI Security Standards Council. Opened November 7, 2026.
  3. PostgreSQL documentation: the cumulative statistics system, PostgreSQL Global Development Group. Opened November 7, 2026.
  4. Snowflake documentation: ACCESS_HISTORY view, Snowflake. Opened November 7, 2026.
FAQ

What reviewers ask about stale access

Protect your brand. Start with your data.

Pick a database with many users. We’ll show what IRIS flags as excessive, or unused past your period with activity data.