Atlassian (Jira & Confluence)¶
Identity & SaaS audit logs. Jira and Confluence audit events, plus Atlassian organization and admin activity.
Status: available on request - self-serve connect is not live yet
The collector and detections for this source are built and run in our lab, but switching it on from the console is not live yet, so connecting it there will not start collection. Ask for it through Integrate -> Request an integration, or email support@sheersafe.com, and we enable it on your dedicated instance. The steps below are accurate, so a credential you create now is the one it will use.
Three feeds, one source
Jira, Confluence, and Atlassian organization/admin activity arrive as one Atlassian source. You can set up a subset of the three; tell us which when you ask for it.
What SheerSight reads¶
SheerSight reads three Atlassian audit feeds:
- Jira audit records (admin permission grants, permission-scheme changes, a project made public, app installs, admin-group membership changes, bulk exports),
- Confluence audit records (space-permission and space-admin changes, anonymous access enabled, page restrictions removed, external sharing enabled, app installs, bulk exports), and
- Atlassian organization / admin events (admin role granted, product access granted, SSO and authentication-policy changes, org API tokens created, IP allowlist changes, domain claimed, users provisioned or deactivated, mass user provisioning).
Together those feeds power the matching detections above. Everything is read-only.
What you'll need¶
- An Atlassian organization admin (admin.atlassian.com) and a site admin for Jira and Confluence.
- For the organization / admin feed: an Atlassian Guard (formerly Atlassian Access) subscription. Jira and Confluence audit do not require Guard, but the organization events API does.
- Your dedicated instance enrolled.
Create the read-only credentials¶
Atlassian splits this into two credentials: an OAuth app for the Jira and Confluence audit logs, and an organization API key for the org and admin events. You can connect one or both.
- Go to the Atlassian developer console (developer.atlassian.com/console/myapps) and create an OAuth 2.0 (3LO) app.
- Under Permissions, add read-only scopes for audit and the minimum content reads:
read:audit-log:jiraread:audit-log:confluenceread:jira-user,read:jira-workread:confluence-content.alloffline_access(required so the connection can refresh itself)
- Set the app's callback URL and run the consent once to authorize it against your site, which produces a refresh token.
- Note your site URL (or its cloud ID).
Scope names
Atlassian occasionally revises granular audit-log scope names. If the console offers a differently named audit-log read scope, choose that one and tell us. The requirement is read-only audit access, nothing more.
- Go to admin.atlassian.com -> Settings -> API keys and create a key. This requires an Atlassian Guard subscription.
- Scope it read-only (audit / events read).
- Note your Organization ID (visible in the admin.atlassian.com URL and settings).
Connect it in SheerSight¶
Self-serve connect is not live for Atlassian yet. Open Integrate -> Request an integration, choose Atlassian, and note which feeds you set up. We enable the source on your dedicated instance and arrange the handover of the credentials through the same browser-side encryption used for every live source, so nothing is sent in the clear:
- Jira & Confluence: the OAuth app's client ID, client secret, and refresh token, plus your site URL or cloud ID.
- Organization & admin: your Organization ID and org API key.
Verify¶
- The source is enabled on your dedicated instance.
- Jira, Confluence, and organization events begin appearing, and matching detections start firing.
Troubleshooting¶
- No organization / admin events. The org events API requires an Atlassian Guard subscription. Jira and Confluence audit will still work without it.
- Jira/Confluence stopped after a while. The OAuth connection refreshes itself using
offline_access; if it was set up without that scope, re-create the app with it included. - No data. Confirm the OAuth consent was completed against the correct site and the scopes above were granted.
What SheerSight can and cannot do¶
The credentials are read-only audit and events access. SheerSight cannot change Jira or Confluence content, permissions, or settings, and it cannot manage users, policies, or the organization. It only reads audit events.