Integration · Devices & endpoint

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

CATAAM connects to Jamf Pro with read-only access and runs 1 automated check against your real configuration. The results map to 2 controls across 7 frameworks, including SOC 2, ISO 27001, PCI DSS, NIST CSF, SOC 1, Australian Privacy Principles.

automated checks: 1
controls mapped: 2
frameworks: 7

What happens when you connect Jamf Pro

Connect with read-only access
Add a read-only role, OAuth scope or API token for Jamf Pro. The credential is encrypted at rest.
Discover assets
CATAAM pulls the accounts, users, repositories or devices it finds into one asset inventory.
Run 1 automated check
Every check runs against your real configuration, then keeps running on a schedule.
Map results to 2 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 1 check CATAAM runs on Jamf Pro

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

Jamf computers have disk encryption enabled

Controls these checks support (2)

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

Control	Requirement	Frameworks
CRY-3	Portable media encrypted	SOC 2, ISO 27001
CRY-4	Data encryption utilized	SOC 2, PCI DSS, NIST CSF, SOC 1, Australian Privacy Principles +1

Jamf Pro integration: frequently asked questions

What does CATAAM check in Jamf Pro?

CATAAM runs 1 automated check on Jamf Pro: Jamf computers have disk encryption enabled.

Which compliance frameworks does the Jamf Pro integration support?

The Jamf Pro checks map to 2 control and count toward SOC 2, ISO 27001, PCI DSS, NIST CSF, SOC 1, Australian Privacy Principles.

Does CATAAM need write access to Jamf Pro?

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 Jamf Pro to CATAAM?

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