Skip to content

Blog

Access certification: proving who should have access

Access certification is the signed proof that each person's access is still right. How it differs from a review, who signs off, and a lightweight process.

· 9 min read

Access certification is the formal, recorded sign-off that each person's access to a system is still right: a named reviewer looks at a list of accounts and roles, approves or changes each one, and puts their name and a date on the result. The review is the checking. The certification is the signature that says the checking happened and who answers for it.

If an auditor, a customer's security questionnaire or a regulator asks "how do you know only the right people have access?", a certification is the answer you hand over. Below: what it is, how it differs from an access review, when you need one, and a version a small company can run without buying anything.

What access certification is

Access certification (also called access recertification or attestation) is a control with three parts. First, a list: every account in a system, with its role or permissions, as of a stated date. Second, a decision per line: keep, change or remove, made by someone who knows whether the access is justified. Third, a signed statement: the reviewer declares that they checked the list and that what remains is appropriate. That statement, with the list and the changes, is the evidence.

The word "certify" is doing real work. A manager who certifies their team's access in the CRM is taking responsibility for it. If an ex-contractor is found in there next month, the question is not only "why wasn't it removed?" but "why was it certified?"

That accountability is the whole point. Without a name on the result, a review is something that happened to the access. With one, it is a decision someone made, and someone can be asked about it.

Certification vs review

People use the two terms interchangeably, and our user access review guide, the hub for this topic, treats them as the same job. The distinction is still worth knowing, because it tells you what to keep:

Access reviewAccess certification
What it isThe process of comparing who has access with who shouldThe reviewer's recorded approval of the outcome
OutputFindings and changesA signed, dated statement per system and reviewer
Who does itWhoever collects and matches the listsThe person accountable for the access: manager or tool owner
What it provesThat someone lookedThat a named person stands behind the result

In practice, a review without certification is a cleanup. Useful, but an auditor cannot tell whether the right person made the decisions. A certification without a real review is worse: a signature on a list nobody read. The industry name for that is rubber-stamping, and auditors look for it.

When it is required

No law says "do access certification" in those words for a small private company. It shows up indirectly, through four routes.

SOC 2. The auditor tests your access controls against the AICPA's criteria and against your own policy. If your policy says access is reviewed quarterly and approved by system owners, they will ask for the approvals. Do you need SSO for SOC 2? covers the access side of that audit.

ISO 27001. The 2022 version's Annex A includes a control titled "Access rights" (5.18). Periodic, documented reviews of access rights are the usual way to show it working; your certification body decides what is enough. Access control under HIPAA and ISO 27001 goes through the access controls.

HIPAA. The Security Rule's information access management standard includes an implementation specification for establishing, documenting, reviewing and modifying a user's right of access (45 CFR 164.308(a)(4)). The same section, as we read it on 27 October 2026, also lists a "Workforce clearance procedure", to "determine that the access of a workforce member to electronic protected health information is appropriate". Both are labeled addressable. Under 45 CFR 164.306(d)(3), that means you assess whether each one is reasonable and appropriate for you, implement it if it is, and if it is not, document why and implement an equivalent alternative where reasonable. It does not mean optional.

Customer contracts and questionnaires. Larger customers ask "Do you perform periodic access reviews, and who approves them?" A yes with dates and names is much stronger than a yes.

In every case, the framework sets the goal and your own policy sets the details: how often, which systems, who signs. Your auditor or assessor decides whether what you did meets it. If you have no policy yet, the access control policy template has a clause for this.

Who signs off

The person who signs should be the one who can answer "does this person still need this?" without guessing.

Managers certify their direct reports across tools. They know who moved teams and who is about to leave.

Tool owners certify each tool's member list. The head of engineering for GitHub, the finance lead for the accounting tool. They know which roles are dangerous.

Nobody certifies their own access. If the CTO is a GitHub owner, someone else signs for that line. ISO 27001's Annex A has a separate control for segregation of duties (5.3) for exactly this kind of conflict.

Admins get a second pair of eyes. Owner and admin roles are the lines that matter most; have them certified by someone other than the admins themselves.

In a 15-person company the same three people will sign most certifications. That is fine. What matters is that each signature covers a list the signer actually read.

Manager-led or owner-led

There are two ways to cut the work, and they find different problems. A manager-led certification sends each manager everything their people have, across tools; it is good at catching movers who kept old access, because the manager knows what the person does now. An owner-led certification sends each tool owner the full member list of their tool; it is good at catching unknown accounts, dangerous roles and seats nobody uses, because the owner knows the tool.

A small company can alternate: owner-led one quarter, manager-led the next. Or run owner-led for the critical tools every quarter and a manager-led pass across everything once a year.

A lightweight process

You do not need identity governance software for this. A shared folder, a spreadsheet and email are enough, as long as you are consistent.

Fix the scope and the date. List the systems in scope (start with those holding customer data, money or code) and pick a cut-off date. Every export uses that date.

Export and prepare one sheet per system. Account, name, role, last login if the tool shows it, and the person's status in your directory (active, suspended, not found). Flag the lines that need attention: admins, unknown emails, suspended people.

Send each reviewer only their lines, with a deadline. Ask for a decision per line: keep, change role, remove.

Get a written statement back. One short paragraph is enough. For example:

I have reviewed the accounts in [system] as of [date]. The access listed as "keep" is required for each person's current role. The accounts marked "change" or "remove" should be changed as noted. Reviewed by [name, title] on [date].

A reply to the email, a comment on a ticket, or a signed PDF all work. Keep it with the sheet.

Make the changes, then prove them. Remove or downgrade, note the date, and capture a screenshot or log entry from the tool. A certification that asks for removals nobody carried out is a finding against you.

File it. One folder per review cycle: scope, exports, statements, changes, evidence. Note anyone who did not respond and what you did about it.

Watch for rubber-stamping. If a reviewer approves every line, every quarter, in two minutes, ask them about one specific account. The first certification nearly always finds something; if yours do not, look harder at the lists.

Quarterly for important systems and yearly for the rest is a common pattern. The frequency in your policy matters more than the one in this article, because that is what you will be tested against.

When a reviewer does not answer

Someone will miss the deadline. Decide in advance what happens: a reminder after the deadline, then escalation to their manager or the founder, and a note in the file either way. Do not certify on their behalf, and do not quietly drop the system from scope. An unanswered certification recorded honestly is a small finding; a missing one discovered by an auditor is a bigger one.

Some companies set a default: access that is not confirmed by the deadline is removed. That is effective and unpopular. If you adopt it, put it in the policy so nobody is surprised.

Tools

What is on the market, roughly in order of cost.

A spreadsheet and email. Free and accepted by auditors if the records are complete. The slow part is pulling member lists from every tool.

Form tools and tickets. A form per reviewer, or a ticket per system, gives you timestamps and a clean record of who approved what.

Compliance automation platforms. Products sold for SOC 2 and ISO 27001 readiness usually include an access review module that collects sign-offs. They read accounts through integrations, so coverage depends on which of your tools they connect to.

Identity governance and administration (IGA) products. Full certification campaigns, reminders, escalations and reports. Built and priced for large companies, and generally reliant on the tools being connected through SSO and SCIM, which often means paying for the tools' enterprise plans first.

For a company of 5 to 50 people, the signature part is easy. The hard part is producing an accurate list of who has what in thirty tools, on the same date, every quarter. The lines that cause the most trouble are the ones no list explains: shared accounts with no owner, and admin roles that break the principle of least privilege.

Where SmashSSO fits

SmashSSO produces that list. It reads your people from Google Workspace with read-only access, reads each tool's members and roles, and matches them by email into one access grid. Accounts that match nobody in your directory are flagged, and people suspended in Google Workspace show every tool where they still have access. Reviewers decide; then removals and role changes run from the same screen, through a tool's member API where you have added a token or through an agent in your own Chrome otherwise, and every change is recorded in the audit log.

It does not collect sign-offs or run certification campaigns, it has no CSV export, and it has no SOC 2 report of its own (security says so). It is not SSO. It costs a flat fee from $199 a month, billed annually (pricing).

FAQ

What is access certification?
Access certification is the formal, recorded sign-off that each person's access to a system is still appropriate. A named reviewer checks a list of accounts and roles, decides on each line, and signs and dates the result.
Is access certification the same as an access review?
They are closely related and often used interchangeably. The review is the checking of who has access against who should; the certification is the reviewer's signed statement that the checking happened and the result is right.
Who signs off?
Managers sign for their direct reports' access, and tool owners sign for the member list of their tool. Nobody signs for their own access, and admin roles should be certified by someone other than the admins.
How often is it done?
Quarterly for systems holding customer data, money or code and yearly for the rest is a common pattern. The frequency written in your own policy is the one an auditor will test you against.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google