Collecting manager initials on an annual spreadsheet feels orderly right up until an external auditor asks to see the raw account lists behind it. During SOC 2 Type II (Criteria CC6.1 through CC6.3), PCI DSS v4.0.1 (Requirements 7.2.4, 7.2.5, and 8.2.6), and ISO/IEC 27001:2022 (Annex A.5.18 and A.8.2) examinations, assessors do not stop at your central SSO directory. They pull account rosters straight from cloud consoles, source repositories, and production databases, lay them beside HR termination logs, and sample individual revocations to confirm the access actually came off.
Why do teams that faithfully run quarterly reviews still run into exceptions during fieldwork? Usually one of three things happened. Someone exported Entra ID or Google Workspace and overlooked the systems where engineers sign in without corporate SSO. Or an IT administrator reviewed and approved the row containing their own privileged role. Or a manager marked an account for removal on October 5, everyone closed the spreadsheet, and nobody attached a timestamped ticket proving the login was disabled in the target system.
For smaller system rosters, you can enter accounts directly into our browser-based User Access Review Worksheet to record discrete keep, downscope, and revoke decisions, note justifications, and export a formula-safe CSV or PDF review sheet.
Pull Read-Only Snapshots Everywhere People Authenticate Directly
Start by pulling timestamped exports on the same snapshot date across every environment capable of authenticating independently of corporate SSO. Your identity provider and groupware tenant (Entra ID, Google Workspace, or Okta) covers active, disabled, and guest users along with privileged directory roles and MFA status, though stopping there leaves major blind spots.
In cloud control planes such as AWS IAM and IAM Identity Center, Azure RBAC, and GCP IAM, export console users, federated permission sets, cross-account AssumeRole trusts, and programmatic access keys. In GitHub or GitLab, pull organization owners, deploy keys, personal access tokens, and especially outside collaborators—where agency contractors often linger long after a statement of work finishes. Round out the snapshot with direct PostgreSQL, MySQL, or Redis database roles reached over VPN or bastion hosts, plus standalone consoles that frequently sit outside SSO: banking portals, payment processors, domain registrars, and MDM break-glass logins.
# 1. AWS IAM: Generate and download a full account credential report (users, MFA, access key age)
aws iam generate-credential-report
aws iam get-credential-report --query 'Content' --output text | base64 -d > ./uar-aws-credentials.csv
# 2. GitHub CLI: Export outside collaborators and organization owners
gh api orgs/EXAMPLE-ORG/outside_collaborators --paginate --jq '.[] | [.login, .id, .site_admin] | @csv' > ./uar-github-outside.csv
gh api orgs/EXAMPLE-ORG/members?role=admin --paginate --jq '.[] | [.login, .id] | @csv' > ./uar-github-owners.csv
# 3. PostgreSQL: Export login-capable roles, superuser/bypassrls flags, and group memberships
psql "$PROD_READONLY_DSN" -c "\copy (
SELECT r.rolname, r.rolsuper, r.rolcreaterole, r.rolcreatedb, r.rolbypassrls, r.rolvaliduntil,
ARRAY(SELECT b.rolname FROM pg_catalog.pg_auth_members m JOIN pg_catalog.pg_roles b ON m.roleid = b.oid WHERE m.member = r.oid) AS member_of
FROM pg_catalog.pg_roles r
WHERE r.rolcanlogin = true
ORDER BY r.rolname
) TO './uar-postgres-roles.csv' WITH CSV HEADER"
Reconcile Against HR Terminations and Transfers First
Before asking engineering leads or department managers to review active staff, compare every exported identity list against HR's authoritative log of employees and contractors terminated or transferred since the previous cycle. Handing managers a cluttered sheet full of people who left earlier in the quarter wastes their attention and invites rubber-stamp replies. Flag any account tied to a departed person for immediate revocation—and inspect post-termination login timestamps if an active credential turns up during a quarterly sweep, since finding one signals a gap in your offboarding webhook or runbook.
Require Explicit Dispositions and Separation of Duties
Vague "Approved" checkboxes and bulk "Approve All" email replies give auditors very little reason to trust that anyone read every row. Require each system owner or team manager to assign one of four explicit states per row, and route every IT, security, or cloud administrator's own row to the CTO, CFO, or another independent executive reviewer so nobody self-approves privileged access:
KEEPwhen current job duties require that exact privilege level, with a short functional justification recorded on any admin or write role.DOWNSCOPEwhen the person remains active on staff but changed roles or only needs read-only visibility (for example, changingAdministratorAccesstoViewOnlyAccess).REVOKEfor a departed employee, a completed contractor SOW, or an unused tool seat (reclaiming paid licenses alongside your SaaS spend audit).INVESTIGATEfor an unrecognized service principal or a human account dormant for 90+ days, suspending it within 48 hours if no owner claims it.
| Compliance Framework | Typical Cadence & Thresholds | What Auditors Sample |
|---|---|---|
| SOC 2 (CC6.1 - CC6.3) | Quarterly or semi-annual per policy; prompt offboarding SLA (commonly 24 hours) | Samples terminations, role transfers, and admin rosters across SSO, cloud, Git, and databases; checks independent sign-off |
| PCI DSS v4.0.1 (Req 7.2.4, 7.2.5, 8.2.6) | User accounts at least every 6 months; system/app accounts reviewed periodically; inactive accounts disabled within 90 days | Requires documented management acknowledgment that CDE access stays least-privilege and vendor accounts remain disabled when not in use |
| ISO/IEC 27001:2022 (A.5.18, A.8.2) | Planned intervals defined in Access Control Policy plus role changes | Checks stricter scrutiny on privileged access rights (A.8.2) and verifies revocations feed tracked tickets |
Separate Decision Timestamps From Proof of Removal
Auditors draw a clear distinction between deciding to remove access on October 5 and proving the account was disabled on October 6. A date in a review spreadsheet only proves someone made a call. Open a tracked ticket for every REVOKE and DOWNSCOPE row and attach concrete closure evidence before marking the quarterly review complete:
Ticket Summary: [UAR-Q4] Revoke / Downscope - [Principal Identifier] in [System Name]
Reviewer Decision Date: [YYYY-MM-DD HH:MM UTC] by [Reviewer Name / Title]
Execution Target SLA: 24 hours (Revoke) / 5 business days (Downscope)
Required Closure Evidence:
[ ] Account disabled or role downgraded in [System Name] at [YYYY-MM-DD HH:MM UTC]
[ ] Active SSO/OAuth sessions, personal access tokens, and SSH/API keys revoked
[ ] Post-change CLI output or console screenshot attached showing updated role state
[ ] Independent peer check completed by: [Verifier Role / Name]
You can pair quarterly access reviews with our SOC 2 compliance checklist, or take a look at our managed IT and identity operations and PCI DSS consulting services if you want engineers to tighten Entra ID, AWS, and SaaS governance.