SaaS Security
Onboard a Jira App to SSPM
Table of Contents
Onboard a Jira App to SSPM
Connect a Jira instance to SSPM to detect posture risks.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
Or any of the following licenses that include the Data Security license:
|
For SSPM to detect posture risks in your Jira instance, you must onboard your Jira
instance to SSPM. Through the onboarding process, SSPM logs in to Jira using account
credentials. SSPM uses this account to scan your Jira instance for misconfigured
settings. If there are misconfigured settings, SSPM suggests a remediation action
based on best practices.
SSPM can also scan your Jira instance for connected
third-party plugins. To enable SSPM to scan your Jira instance for connected
third-party plugins, you must onboard an Atlassian app. If you
onboard an Atlassian app, SSPM also scans high-level
Atlassian Administration settings for your organization. Some high-level Atlassian
Administration settings can affect Jira, and will differ depending on whether your
organization has the free, Standard, or Premium version of Jira.
SSPM gets access to your Jira instance by using Okta SSO or Microsoft Azure credentials that you
provide during the onboarding process. For this reason, your organization must be
using Okta or Microsoft Azure as an identity provider. The Okta or Microsoft Azure
account must be configured for multi-factor authentication (MFA) using one-time
passcodes.
To onboard your Jira instance, you complete the following actions:
Collect Information for Accessing Your Jira Instance
To access your Jira instance, SSPM requires the following information, which you
will specify during the onboarding process.
| Item | Description |
|---|---|
| User | The login email address of the account that SSPM
will use to access your Jira instance. (Required
Permissions) The user must be a Jira Organization
Administrator. |
| Password | The password for the Organization Administrator account. |
If you are logging in through Okta, you must provide SSPM with the following
additional information:
| Item | Description |
|---|---|
| Okta subdomain | The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization. |
| Okta 2FA secret | A key that is used to generate one-time passcodes for MFA. |
If you are using Azure Active Directory (AD) as your identity provider, you must
provide SSPM with the following additional information:
| Item | Description |
|---|---|
| Azure 2FA secret | A key that is used to generate one-time passcodes for MFA. |
As you complete the following steps, make note of the values of the items
described in the preceding tables. You will need to enter these values during
onboarding to access your Jira instance from SSPM.
- Identify the account that SSPM will use to access your Jira instance.(Required Permissions) The user must be a Jira Organization Administrator.Get a secret key for MFA.The steps you follow to get the MFA secret key differs depending on the identity provider you are using to access the Organization Administrator account.
- (For Okta log in) To access the account through Okta:
- (For Microsoft Azure log in) To access the account through Microsoft Azure:
Connect SSPM to Your Jira Instance
By adding a Jira app in SSPM, you enable SSPM to connect to your Jira instance.- Log in to Strata Cloud Manager.Select and click the Jira tile.On the Posture Security tab, Add New instance.Specify how you want SSPM to connect to your Jira instance. SSPM can Log in with Okta or Log in with Azure.When prompted, provide SSPM with the login credentials and the information it needs for MFA.Connect.
