Clerk.io

Access Control Policy

1. Purpose

Define requirements for granting, reviewing and revoking access to Clerk.io information assets.

2. Principles

  1. Least Privilege – users receive the minimum access necessary.
  2. Need-to-Know – data access aligns with job role.
  3. Segregation of Duties – no single person can deploy unreviewed code to prod.
  4. Timely Revocation – accounts disabled within 24 h of termination.

3. Account Types

Type Examples Approval
Workforce (SSO) Google Workspace, Slack Line Manager + ISM
Workforce (Custom MFA) HQ (Internal Tool Portal) Line Manager + ISM
Developer GitHub (MFA required), Sentry, IPA, Datadog Line Manager + ISM
Privileged AWS IAM console user (hardware MFA) Head of Product + ISM
Compute Roles AWS IAM instance profiles SRE + ISM

4. Authentication Requirements

5. Access Request & Approval

  1. Request privilege escalation through Head of Product.
  2. Head of Product verifies legitimate need.
  3. Head of Product handles or delegates the access grant.
  4. Access granted by appropriate team (typically SRE).

6. Reviews

7. Revocation

HR off-boarding triggers removal workflow: * Remove access to: - Github - Sentry - IPA (Engineering Identify Management) - HQ (Internal Tool Portal) - Slack - Google Workspace - Datadog * Collect hardware.

8. Exceptions

Temporary elevated access managed via FreeIPA/Kerberos: login sessions valid for 8 hours, sudo escalation ~30 minutes; tickets auto-expire and cannot be transferred between systems.

9. Compliance

Non-compliance reported to ISM; disciplinary action possible.

Version 1.2 — effective 2025-09-01