Connectors

Connectors are how Joopler reads the state of your environment and turns it into control evidence. Each connector runs read-only checks on a schedule and records signed results against the controls it covers.

Available connectors

Joopler ships 33 first-party connectors across cloud, identity, devices, work tools, and AI. Select one for its exact setup steps.

Cloud

• Amazon Web Services: Cloud infrastructure: encryption, logging, and account hardening.
• Microsoft Azure: Cloud infrastructure: subscription posture via a service principal.
• Google Cloud: Cloud infrastructure: project posture via a service account.
• VMware vSphere: On-prem virtualization posture: ESXi host hardening, VM encryption, least-privilege roles, and segmentation. For private or air-gapped vCenter, deploy the collector so evidence flows out signed.

Identity

• Okta: Identity governance: MFA enrollment, stale-account review, and system-log access.
• Microsoft Entra ID: Identity governance: member MFA registration, stale guests, and sign-in log access.
• Ping (PingOne): Identity governance: MFA configuration, per-user MFA, and activity-log access.

Devices (MDM)

• Jamf Pro: Apple device posture: FileVault encryption and management state.
• Microsoft Intune: Device posture: managed-device compliance and disk encryption.

Work and code

• GitHub: Org 2FA, branch protection, and Dependabot alerts.
• Slack: Member 2FA + admin count (monitor); failure alerts (webhook).
• Google Workspace: 2-Step Verification enforcement and super-admin count.
• Jira: Open security tickets have an assigned owner; create remediation tickets from findings.

AI providers

• OpenAI: AI governance: org owner hygiene and audit-log access via the Admin API.
• Anthropic: AI governance: org admin hygiene and workspace-scoped API keys via the Admin API.
• Microsoft 365 Copilot: AI governance: Global Admin hygiene, MFA Conditional Access, and audit logging via Microsoft Graph.

HR and ITSM

• Workday: HRIS: onboarding completion, background checks, and timely offboarding.
• ServiceNow: ITSM: change approvals and incident tracking via the Table API.

How a connector works

1. You provide read-only access (a role, an app registration, or an API token).
2. Joopler runs the connector's checks on a daily schedule.
3. Each check writes a signed evidence record and updates the control status: passing, failing, due soon, or needs attention.

Connectors are graded only for the platforms you actually run, so you never see failing controls for a cloud you do not use.

Deploy your baseline as code

For AWS, Azure, GCP, and vSphere you can also deploy the security baseline Joopler verifies using the published Joopler Terraform modules, so getting to green is a terraform apply and staying green is drift-detected like the rest of your infrastructure. See Compliance as code.