Atlassian
This guide walks through how to set up Atlassian audit logs as a source in Scanner Collect, using direct API integration with the Atlassian admin org events API.
We'll assume that you want Scanner to both store the logs in S3 and index them for search and detection.
Create a Collect Rule
Authenticate with Atlassian
If you've previously created an Atlassian connection, select it from the list and skip to the next step.
Otherwise, select New Atlassian Connection and fill in:
Connection Name: A recognizable name for this connection.
Organization ID: The UUID of your Atlassian organization (see below).
API Key: The API key value (see below).
If you already have an Organization ID and API key, paste them into the Scanner connection form. Otherwise, create them in Atlassian:
Sign in at
admin.atlassian.comas an organization admin.Open the organization, then go to Organization settings → API keys.
Click Create API key, give it a name (e.g.
scanner-audit-logs), and grant it access to read audit log events.On the Copy API key screen, copy both the Organization ID and the API key. The API key cannot be recovered after you leave this screen, so save it somewhere safe (e.g. a password manager) before continuing.
Paste both values into the Scanner connection form.
Create an Index Rule
With the Collect Rule created, Scanner will poll the Atlassian admin org events API every 5 minutes. New events will be written to your S3 bucket, under the specified prefix.
Create an Index Rule to have Scanner index the logs for fast search and detections.
Atlassian Defaults
When you create the Index Rule from the Collect Rule, the following defaults are pre-populated:
Transformations: Add Metadata, Parse JSON Columns
Timestamp Field:
.attributes.time
Last updated
Was this helpful?