SaaS Security
Onboard an Aha.io App to SSPM
Table of Contents
Onboard an Aha.io App to SSPM
Connect an Aha.io 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:
|
To run scans of your Aha.io instance, SSPM connects to the Aha.io instance by using
information that you provide. Once SSPM connects, it scans the Aha.io instance and
will continue to run scans at regular intervals.
Onboard an Aha.io App to SSPM Using Login Credentials
Connect an Aha.io instance to SSPM to detect posture risks.
For SSPM to detect posture risks in your Aha.io instance, you must onboard your
Aha.io instance to SSPM. Through the onboarding process, SSPM logs in to Aha.io
using administrator account credentials. SSPM uses this account to scan your Aha.io
instance for misconfigured settings. If there are misconfigured settings, SSPM
suggests a remediation action based on best practices.
SSPM gets access to your Aha.io 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 Aha.io instance, you complete the following actions:
- Collect information for accessing your Aha.io instance.To access your Aha.io 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 Aha.io instance. Required Permissions: The user account must be assigned to both the Account and Billing administrator roles in Aha.io.Password The password for the login account. Instance Host The custom domain for accessing your organization's Aha.io account. You specify this domain when you sign up for an Aha.io account, and it is included as part of the URL that you use to access the account. If you're 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're 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 Aha.io instance from SSPM.- Identify the Okta user account that SSPM will use to access your Aha.io instance.(Required Permissions) The user account must be assigned to both the Account and Billing administrator roles in Aha.io.Get a secret key for MFA.The steps you follow to get the MFA secret key differ depending on the identity provider you're using to access the account.
- (For Okta log in) To access the account through Okta:
- (For Microsoft Azure log in) To access the account through Microsoft Azure:
Make note of your organization's Aha.io instance host name.After you log in to Aha.io, the instance host name is a unique subdomain included in the Aha.io URL. The URL format is <instance_host>.aha.io.Connect SSPM to your Aha.io instance.By adding an Aha.io app in SSPM, you enable SSPM to connect to your Aha.io instance.- Log in to Strata Cloud Manager.Select and click the Aha.io tile.On the Posture Security tab, Add New instance.Specify how you want SSPM to connect to your Aha.io 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.
