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 eighteen first-party connectors across cloud, identity, devices, work tools, and AI:

• Cloud: AWS, Azure, GCP, VMware vSphere
• Identity: Okta, Microsoft Entra ID, Ping
• Devices (MDM): Jamf Pro, Microsoft Intune
• Work + code: GitHub, Slack, Google Workspace, Jira
• AI providers: OpenAI, Anthropic, Microsoft 365 Copilot
• HR + ITSM: Workday, ServiceNow

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.