Atlassian (Formerly Atlassian Jira Software)

Atlassian (formerly Atlassian Jira Software) is a work management tool for various use cases, from requirements and test case management to agile software development.

This adapter lets you fetch data and get visibility and security across all Atlassian accounts and products at your company, including the users managed under the following cloud products:

• Jira Software
• Jira Work Management
• Jira Service Management
• Confluence
• Bitbucket
• Trello
• Opsgenie
  
  

Types of Assets Fetched

This adapter fetches the following types of assets:

• Users
• Roles
• Groups
• Application Settings
• Accounts/Tenants
• Application Resources
• Permissions

Enforcements

Axonius has Enforcement Center actions to create and delete Atlassian.

• Jira Software - Create User
• Jira Software - Delete User

Axonius SaaS Applications Adapter Configuration

To Fetch SaaS data, some of the initial configurations in Atlassian need to be performed by a user with administrator level privileges.

If the adapter has already been set up and you want to configure it to fetch application settings from SaaS data, make sure to include the following connection parameters:

• Atlassian Admin API - Organization ID
• Atlassian Admin API - API key
• Password
• 2FA Secret Key

Parameters

The parameters that you need to fill out will differ based on the capabilities in your Axonius platform. 'General' pertains to users with Axonius Cyber Assets and/or Axonius SaaS Applications.

General

• Domain (required) - The hostname or IP address of the Jira Software server.

• User Name (required) - The username for a user account that has the Required Permissions to fetch assets.

• API Token (required) - An API Token associated with a user account that has the Required Permissions to fetch assets. Note: The API Token is not the same as the Admin Key.

• Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

• HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

• Jira API Version (required, default: V3) - Select your Jira API version.

• Atlassian Admin API - Organization ID and Atlassian Admin API - API key - The organization ID and an organization API key generated for fetching SaaS data. Needed for fetching organizational data.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

Axonius SaaS Applications

• Password - The password for the Atlassian user account. Needed for fetching Settings from Atlassian.
• 2FA Secret Key - If you require two-factor authentication to access Atlassian, and you want to fetch Settings from Atlassian, you will need to generate a secret key in a 2FA solution such as Google authenticator and paste it here. See Set Up Google Authenticator in the Okta adapter, for an example.
• Connection Label - A label to help distinguish between multiple connections for the Atlassian adapter.
  
  

Advanced Settings

General

• Do not fetch disabled users (required, default: false) - Select whether to exclude fetching disabled users.
• Distinguish User ID From Different Domains - When selected, the Atlassian domain is appended to the ID of each user, to allow Axonius to fetch the same users from multiple sites without overriding the data.
• Users per page (default: 50) - Enter the number of users per a single request. Atlassian may limit the maximum number of users per page. If the number you enter is higher than the limit, the fetch will fail. Therefore make sure the value you enter is lower than that.

Axonius SaaS Applications

• Fetch projects and project roles - Select this option to fetch projects and project roles.
• Fetch groups - Select whether to fetch users groups details.
• Fetch permissions - Select to fetch permissions configured for the Atlassian accounts in your organization.
• Fetch settings - Select to fetch settings configured for the Atlassian accounts in your organization.
• Filter users without site access - Select to exclude users who cannot access the Atlassian site.
• Number of parallel requests - Specify the maximum parallel request this adapter will create when connecting the Atlassian server.
  • This setting lets you control the performance of this adapter.

API

Axonius uses the Jira Cloud platform REST API.

Required Permissions

The value supplied in User Name must have Jira 'global' permissions to fetch assets. For permissions required for fetching Saas data, see the Create a User Account and Create an Organization API Key sections.

Set Up the Adapter

To successfully connect this adapter, you need to complete the following steps.

Accounts with only Axonius Cyber Assets:

• Create an API token

Accounts with Axonius SaaS Applications:

1. Create a User Account
2. Create an Organization API Key
3. Create an API token

Create a User Account

You must have the Jira Administrator or Jira System Administrator global permission to be able to manage users in Jira applications.

To create a new user, from the Atlassian Administration:

1. Go to Administration > User Management.
2. In the User browser, select Create User.
3. Enter the Username, Password, Full Name, and Email address.
   1. The password length should be at least 32 characters.
   2. The user account needs to have MFA disabled.
4. Select all Jira applications.
5. Select Create.
6. To fetch data from the Atlassian Access, the created account must be an admin:
   1. Go to Settings > Administrators.
   2. Click Add administrators.
   3. Enter the created Atlassian account email address and click Grant access.
7. If the created account has not been set as an admin, to fetch data from Jira, edit that user and add them to groups that provide the following permissions:
   1. Administer Jira global permission.
   2. Browse users and groups global permission.
   3. Administer projects project permission (for all projects).
8. If the created account has not been set as an admin, to fetch data from Confluence, edit that user and add them to groups that provide the following permissions:
   1. Permission to access the Confluence site ('Can use' global permission).
   2. 'View' permission for all spaces.

Create an Organization API Key

1. Login to admin.atlassian.com with the created Atlassian account. Select your organization if you have more than one.
2. Select Settings > API keys.
3. Select Create API key in the top right.
4. Enter a name that you’ll remember to identify the API key.
5. Set the latest date possible for the key expiration date. You will be unable to select a date longer than a year from the date of creation.
6. Select Create to save the API key.
7. Copy the generated Organization ID and API key.
8. Select Done. The key will appear in your list of API keys.
9. In Axonius, paste the copied values in the Atlassian Admin API - API Key and Atlassian Admin API - Organization ID fields.

Create an API token

1. Login to admin.atlassian.com with the created Atlassian account, and generate an API token, using the following URL: https://id.atlassian.com/manage/api-tokens#.
2. To generate an API Token, click on Create API token.
3. Choose a label that is short, memorable, and easy to remember, and click Create.
4. Copy the generated API token.
5. In Axonius, paste the copied token in the API Token field.

Version Matrix

This adapter has only been tested with the versions marked as supported but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.