SaaS Security
Onboard an Expiration Reminder App to SSPM
Table of Contents
Expand All
|
Collapse All
SaaS Security Docs
Onboard an Expiration Reminder App to SSPM
Connect an Expiration Reminder 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 Expiration Reminder instance, you must onboard your Expiration Reminder
instance to SSPM. Through the onboarding process, SSPM logs in to Expiration Reminder using
administrator account credentials. SSPM uses this account to scan your Expiration Reminder
instance for misconfigured settings. If there are misconfigured settings, SSPM
suggests a remediation action based on best practices.
SSPM gets access to your Expiration Reminder instance by using Okta SSO credentials that you provide during the
onboarding process. For this reason, your organization must be using Okta as an
identity provider. The Okta account must be configured for multi-factor
authentication (MFA) using one-time passcodes.
To onboard your Expiration Reminder instance, you complete the following actions:
Collect Information for Accessing Your Expiration Reminder Instance
To access your Expiration Reminder instance, SSPM requires the following information, which you
will specify during the onboarding process.
Item | Description |
---|---|
User email | An email address of an Okta user account.
Required Permissions: The user must be an
Expiration Reminder administrator. |
Password | The password for the Okta user account. |
Okta Domain | The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization. |
MFA Secret Key | A key that is used to generate one-time passcodes for multi-factor authentication. |
As you complete the following steps, make note of the values of the items
described in the preceding table. You will need to enter these values during
onboarding to access your Expiration Reminder instance from SSPM.
- Identify the Okta user account that SSPM will use to access your Expiration Reminder instance. The user account must have administrator privileges in Expiration Reminder. SSPM needs this administrator access to monitor your Expiration Reminder instance.Remember which account you will use to access your Expiration Reminder instance through Okta SSO authentication from SSPM. You will provide the login credentials to SSPM during the onboarding process.
Connect SSPM to Your Expiration Reminder Instance
By adding an Expiration Reminder app in SSPM, you enable SSPM to connect to your Expiration Reminder instance.- Log in to Strata Cloud Manager.Select ManageConfigurationSaaS SecurityPosture SecurityApplicationsAdd Application and click the Expiration Reminder tile.Under posture security instances, Add Instance or, if there is already an instance configured, Add New instance.Enter the user credentials, Okta domain, and MFA secret key for accessing your Expiration Reminder instance and Connect.