Learn how you can manually provide SSPM with the configuration values for a
Perplexity instance.
| Where Can I Use This? | What Do I Need? |
|---|
|
|
- SaaS Security Posture Management license
Or any of the following licenses that include the Data Security license:
|
The onboarding process for Perplexity is different from most applications,
because SSPM does not support scans for Perplexity. During the onboarding process
for most applications, SSPM establishes a connection to your application instance by
using credentials that you provide, such as a login password or an access token.
After SSPM has established this connection, SSPM can scan your application
instance's settings by using an API provided by the application or by using data
extraction techniques.
Although SSPM does not support scans for Perplexity, you can still onboard a
Perplexity application to SSPM. However, when you onboard a Perplexity application
to SSPM, you don’t supply SSPM with any authentication credentials. SSPM does not
establish a connection to your Perplexity instance and does not run scans to
determine the Perplexity settings. Instead, you will manually enter your Perplexity
instance's settings, which SSPM will compare against its recommended settings. You
can think of this process as a virtual onboarding. SSPM creates a tile on the
Applications page to represent your Perplexity instance, but this tile is isolated
to SSPM. SSPM will show rule violations for the Perplexity instance, but SSPM
determines the violations based entirely on the information that you manually enter.
If you change the value of a setting in your application instance, you must also
manually update the setting value in SSPM. If you don’t keep the setting values
synchronized, the rule violations that SSPM displays will be unreliable.
To onboard a Perplexity instance, you complete the following steps:
