Overview
SaaS Posture integrations provide visibility into the configuration and security posture of your connected SaaS applications. Cato continuously reviews the application settings and compares them to the recommended posture defined by Cato’s research team. This helps identify misconfigurations that can increase risk, such as authentication settings, third-party integrations, and data-sharing controls.
Posture data appears in the Applications dashboard, where you can view posture scores and the highest-severity findings across connected applications. You can review each posture check from the Posture page, including the issue details, status, and remediation action required to pass the check.
For more information, see Reviewing the Security Posture of Your SaaS Applications.
To configure the SaaS Posture integration, you need to:
Configure the required settings in the SaaS application
Create the API connector in the CMA
A CASB license is required for SaaS Posture integrations.
Configuring the Docusign Integration
To configure the Docusign integration, create an application in the DocuSign admin portal.
Prerequisites
Your DocuSign account must have an Organization configured (DocuSign Admin / Organization Management)
The authenticating user must have the Organization Administrator role
Standard eSignature account access is used, for account-level security settings, password rules, users, and Connect webhook configuration
Step 1: Configure the Integration in the Docusign Admin Portal
In the Docusign admin portal, configure a user and application.
Creating a User
The first step in configuring the integration is to create a user with the required roles.
To create a user:
In the Docusign Admin Portal create a user. For more information, see the Docusign documentation.
Assign the user the Organization Administrator or Security Reports Administrator role.
On the User's page, copy and save the User ID so that it can be entered into the CMA.
Configure an Application
The next step is to create an Integration key and Private key.
To configure an application:
In the Docusign Admin Portal, navigate Settings > Integrations > Apps and Keys.
Click Add App and Integration Key.
Add the following:
App Name: Choose a name for the app
Integration Type: Third-party integration key
Redirect URIs: Click Add URI and enter:
https://cc.catonetworks.com/redirect/cas/appconnector/callbackAllowed HTTP Methods: Check GET and POST
Copy and save the Integration Key so it can be entered into the CMA.
In the Service Integration section, click Generate RSA. Copy and save the Private Key so it can be entered into the CMA.
Note: This is only displayed once.
Click Save.
Step 2: Create the API Connector in the CMA
After you have set up an integration with the required application, add the details in the CMA.
To create the API connector in the CMA:
From the navigation menu, click Resources > Integrations.
Click the Configured Integrations tab.
Click New.
The New Integration panel opens.
Select the SaaS Application you want to add.
In the Capability drop down select SaaS Posture.
Add the details created during step one.
If you are integrating with a development environment, check the Is Dev Environment box, if you are integrating with a production environment, leave this box unchecked.
In the Consent Endpoint field:
For production environments, add: https://account.docusign.com/
For developer environments, add: https://account-d.docusign.com/
Click Save.
The Docusign consent flow opens.
Grant consent for these scopes:
signature
impersonation
user_read
organization_read
account_read
group_read
permission_read
identity_provider_read
domain_read
The app is visible on the Integrated Apps table with a Connected status.