Integration · Identity & access

Clerk integration for continuous SOC 2, ISO 27001 & PCI DSS compliance

CATAAM connects to Clerk with read-only access and runs 3 automated checks against your real configuration. The results map to 7 controls across 8 frameworks, including SOC 2, ISO 27001, PCI DSS, GDPR, NIST CSF, SOC 1.

automated checks: 3
controls mapped: 7
frameworks: 8

What happens when you connect Clerk

Connect with read-only access
Add a read-only role, OAuth scope or API token for Clerk. The credential is encrypted at rest.
Discover assets
CATAAM pulls the accounts, users, repositories or devices it finds into one asset inventory.
Run 3 automated checks
Every check runs against your real configuration, then keeps running on a schedule.
Map results to 7 controls
Each result lands on the controls it proves — and counts for every framework that shares them.
Store evidence and raise issues
Passing checks become audit evidence. Failures show up for the control owner and can open a Jira issue.

The 3 checks CATAAM runs on Clerk

Each check runs against your real Clerk configuration and keeps running on a schedule. Check names are shown as they appear in the CATAAM platform.

Clerk inactive users disabled or removed
Clerk instance is a production instance (not development)
Clerk users have two-factor authentication enabled

Controls these checks support (7)

A passing check becomes evidence for each control below, and counts for every framework that shares the control.

Control	Requirement	Frameworks
CRY-1	Unique production database authentication enforced	SOC 2, ISO 27001
IAC-1	Production application access restricted	SOC 2, ISO 27001, SOC 1
IAC-6	Production network access restricted	SOC 2, ISO 27001, SOC 1
IAC-8	Access revoked upon termination	SOC 2, ISO 27001, SOC 1
IAC-12	Remote access MFA enforced	SOC 2, ISO 27001, PCI DSS, NIST CSF, SOC 1 +1
IAC-85	Remote access MFA enforced	GDPR, DPDP Act
TECH-03	Information Access Restriction	ISO 27001

Clerk integration: frequently asked questions

What does CATAAM check in Clerk?

CATAAM runs 3 automated checks on Clerk, for example: Clerk inactive users disabled or removed; Clerk instance is a production instance (not development); Clerk users have two-factor authentication enabled. The full list is on this page.

Which compliance frameworks does the Clerk integration support?

The Clerk checks map to 7 controls and count toward SOC 2, ISO 27001, PCI DSS, GDPR, NIST CSF, SOC 1.

Does CATAAM need write access to Clerk?

No. Connectors use read-only roles, scopes or API tokens, and credentials are encrypted at rest. The only optional write anywhere in CATAAM is opening Jira issues for failed checks.

How do I connect Clerk to CATAAM?

Add a read-only role, OAuth scope or API token for Clerk in CATAAM. CATAAM then discovers your assets, runs the checks and keeps running them on a schedule, storing each result as audit evidence.