Glossary. Access certification.
What is access certification, and how are reviews recorded?
Access certification is a periodic review of who keeps each grant. It is finished when every revoked grant is gone and nobody has certified their own access.
By Dipal Panchal, co-founder and CEO · Updated November 8, 2026
A decision on every grant, with a date
Access certification is a periodic review in which the person who knows the need confirms each existing grant or marks it for removal, with a recorded decision and date. Unlike approval at grant time, which happens once, certification asks again whether the reason for each grant still holds. A cycle is finished when every revoke has a removal date and a later check shows the grant gone.
It is also called access recertification or access review. IDPro, the association for identity professionals, describes it as “the periodic process of reviewing and validating user access rights.”
One review cycle, six decisions
A quarterly cycle on grants: decisions recorded on November 7, 2026, removals due two weeks later. Last used comes from each source’s activity record; not measured means the source keeps none.
| Identity | Role or group | Object | Privilege | Last used | Decision |
|---|---|---|---|---|---|
| a.ndlovu@example.com | finance_analysts_uk | finance.gl_entries | SELECT | October 28, 2026 | Keep; reviewer: the finance data owner |
| j.ortiz@example.com | finance_analysts_uk | finance.payroll | SELECT | April 2, 2026 | Revoke: remove j.ortiz from finance_analysts_uk; reviewer: the payroll owner; due November 21, 2026 |
| svc_billing_sync (service account) | billing_writer | billing.invoice | INSERT, UPDATE | November 6, 2026 | Downgrade to INSERT; reviewer: the billing system owner; due November 21, 2026 |
| p.shah@example.com (DBA) | dba_admin | Every schema | All privileges | November 5, 2026 | Rejected: the DBA certified their own access; reviewer reassigned: the head of platform |
| l.berg@example.org (contractor) | project_x_ro | crm.contact | SELECT | September 30, 2026 | Revoke by November 8, 2026; reviewer: the sponsor; access should have ended September 30, so a leaver finding is raised |
| support_in (group) | support_tier2 | crm.v_ticket_customer | SELECT | Not measured | Keep until March 31, 2027, members reviewed; reviewer: the support lead, who knows the need |
Nobody certifies their own access
p.shah’s row is the decision a reviewer can’t make, because the DBA approved the DBA’s own administrator rights, so the decision is rejected and goes to someone with authority over the role. The same applies to anyone whose grant lands on their own list.
Match every other row to the person who knows the need. A manager can say whether a person still needs access for the job, and a data owner can say whether access to that dataset is appropriate at all. Service accounts have no manager to ask, so their system owner reviews them.
What the frameworks set
Use the row for the framework you are audited against. PCI DSS fixes six months for user accounts; the others leave the frequency to you, and ISO and SOC 2 also point to segregation of duties.
| Framework | Provision | What it asks |
|---|---|---|
| PCI DSS v4.0.1 | Requirement 7.2.4 | Review user and third-party accounts at least every six months; fix inappropriate access; management acknowledges |
| PCI DSS v4.0.1 | Requirement 7.2.5.1 | Review application and system accounts at the frequency your targeted risk analysis sets |
| ISO/IEC 27001:2022 | Annex A 5.18 and 5.3 | Review access rights as your access policy provides (5.18; no interval named); segregate conflicting duties (5.3) |
| NIST SP 800-53 Rev. 5 | AC-2, item j; AC-6(7)) | Review accounts at a frequency you define; review user privileges and remove those no longer needed |
| SOC 2 (2017 Trust Services Criteria) | CC6.3 | Authorize, modify or remove access by role, weighing least privilege and segregation; point of focus: periodic review |
How reviews turn into rubber stamps
Reviewers face a high volume of requests, “leading to fatigue and a tendency to approve access without proper validation,” in the words of its body of knowledge article Optimizing Access Recertifications. A list of entitlement names with no link to the data asks the reviewer to guess.
Dipal Panchal, Sylox’s co-founder and CEO, ran reviews from the other side. “At CBRE, I managed three to five applications with a team of over 200 people,” he says. Every review meant a manual spreadsheet, and approvals were split across Okta, Azure, ServiceNow and custom steps, so people did not know where to ask.
What was missing, Panchal said in an April 2026 interview, was business context. Ask who had access to a dataset and when they last used it, and “IT handles that” was the answer. A reviewer who sees the data each grant reaches and its last use has something to decide on.
The gaps between review cycles
A certification judges the grants on the list on the day of the review, so access granted the week after waits for the next cycle. Joiners, movers and leavers need their own trigger in the identity process.
It is also a judgment, which makes it different from a stale access check that reads activity data. The support_in row shows the two together: with no activity record, the support lead’s knowledge is all the evidence there is, so the decision is time-limited.
Close the cycle, then call it done
Sylox’s close-out rules, beside whatever your framework asks: nobody certifies their own access. Every revoke or downgrade gets a removal date two weeks after the decision, and an unanswered item goes to the data owner’s manager. Leavers are removed at once, not at the next review.
The cycle closes only when a later check shows each revoked grant gone. Without that check, nothing in the record shows the review changed anything.
IRIS records a reviewer’s decision on each identity’s access to a source, beside the sensitive data it reaches, where the source exposes permission data. Capabilities vary by edition.
A reviewer’s decision on an identity’s access to a source: certified, or marked for downgrade or revocation, with a reason: IRIS produces this.
Each decision kept in the audit history: IRIS produces this.
Scheduled cycles, reviewer assignment and reminders: Not produced by IRIS.
Removing the grant in the source system: Not produced by IRIS.
A later complete scan of the same scope, showing whether the access is still there: IRIS produces this.
IRIS for access reviewsCheck last cycle’s revokes today
Open the record of your last review and list every revoke and downgrade. For each one, check the source system today: is the grant gone, reduced, or still there? Record any grant still there as an open finding from that review.
Before the next cycle, trace every path to your most sensitive tables with data access governance, then run it with how to run a database access review.
Official sources
- PCI DSS v4.0.1, requirements 7.2.4 and 7.2.5.1, PCI Security Standards Council. Opened November 7, 2026.
- ISO/IEC 27001:2022, Annex A controls 5.3 and 5.18, ISO. Opened November 7, 2026.
- NIST SP 800-53 Rev. 5 (release 5.2.0), AC-2 and AC-6(7), NIST. Opened November 8, 2026.
- 2017 Trust Services Criteria (revised points of focus, 2022), CC6.3, AICPA. Opened November 7, 2026.
Around a review cycle
What is data access governance?
The step before a review: every path from an account to a sensitive table, so the list is complete.
What is stale access?
A check on activity data against a written period, which supports a review but can’t replace the reviewer’s judgment.
What is audit evidence for data security?
The next step: the review record as an evidence item, with its producer, date and completeness check.
What reviewers ask about certification
A manager can confirm the person still needs access for the job. Whether access to that dataset is appropriate at all is the data owner’s call, so ask both where the data is sensitive.
Yes, if each row carries the decision date, the reviewer and the decision, and the file names the system and report that produced it, the export date and a row count you can check. Without those, an auditor has nothing to test.
No. A review when someone changes role catches movers early, but grants drift between events too. Run both, and record each the same way.
Protect your brand. Start with your data.
Bring your last access review spreadsheet. We’ll show how IRIS records each decision and reason on the same accounts.