SaaS Security
Onboard a Confluence App to SSPM
Table of Contents
Onboard a Confluence App to SSPM
Connect a Confluence App 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 Confluence instance, you must onboard your
Confluence instance to SSPM. Through the onboarding process, SSPM logs in to
Confluence using account credentials. SSPM uses this account to scan your Confluence
instance for misconfigured settings. If there are misconfigured settings, SSPM
suggests a remediation action based on best practices.
SSPM can also scan your Confluence instance for connected third-party plugins. To
enable SSPM to scan your Confluence instance for connected third-party plugins,
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 Confluence, and will differ depending on whether
your organization has the free, Standard, or Premium version of Confluence.
SSPM gets access to your Confluence 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 Confluence instance, you complete the following actions:
Collect Information for Accessing Your Confluence Instance
To access your Confluence instance, SSPM requires the following information,
which you will specify during the onboarding process.
| Item | Description |
|---|---|
| User email | The login email address of the account that SSPM
will use to access your Confluence instance. (Required
Permissions) The user must be a Confluence
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 Confluence instance from SSPM.
- Identify the account that SSPM will use to access your Confluence instance.(Required Permissions) The user must be a Confluence 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 Confluence Instance
By adding a Confluence app in SSPM, you enable SSPM to connect to your Confluence instance.- Log in to Strata Cloud Manager.Select and click the Confluence tile.On the Posture Security tab, Add New instance.Specify how you want SSPM to connect to your Confluence 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.
