--- title: "Salesforce: Configuring the Remediation Actions Integration" slug: "salesforce-configuring-the-remediation-actions-integration" updated: 2026-11-15T13:57:08Z published: 2026-11-15T13:57:08Z canonical: "knowledge.catonetworks.com/salesforce-configuring-the-remediation-actions-integration" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.catonetworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Salesforce: Configuring the Remediation Actions Integration ## Overview XOps integrations let you take response actions in connected third-party applications as part of an investigation. You can revoke a user’s sessions or disable their account in your single sign-on (SSO) provider or a specific application. These actions help you contain threats by restricting access to affected accounts. To enable these actions, configure a connector for the relevant third-party application. For more information, see [Mitigating Threats in XOps Stories](/v1/docs/mitigating-threats-in-xops-stories). To configure the Remediation Actions integration, you need to: 1. Configure the required settings in the SaaS application 2. Create the API connector in the CMA A XOps license is required for Remediation Actions integrations. ### Benefits of Connecting Salesforce The Salesforce Remediation Actions connector lets Cato take response actions on Salesforce user accounts during an investigation. It uses a separate External Client App and write access, without affecting other Salesforce connectors, such as App Activities. - **Disable User:** Finds the user whose Salesforce username or email matches the requested email and deactivates the account by clearing **Active**. If the account is already inactive, the action reports that condition and succeeds. - **Revoke Sign-In Sessions:** Finds the user in the same way, ends all active Salesforce sessions, and revokes OAuth authorizations (connected-app grants). The user must sign in again and reauthorize connected apps. The account stays active. The result shows the number of sessions ended and OAuth authorizations revoked, including app names. If the user has no sessions or authorizations, the action succeeds and reports zero for both. ## Configuring the Salesforce Integration To configure the integration, create a dedicated Salesforce integration user, permission set, and External Client App, then create the connector in the Cato Management Application (CMA). ### Prerequisites - A Salesforce organization with API access enabled - A Salesforce administrator who can create users, permission sets, and External Client Apps **Manage Users** is a broad permission. Salesforce enables related permissions with it, such as Reset Passwords and Assign Permission Sets. **Customize Application** is also broad. Assign both only to a dedicated integration user. Do not reuse the integration user of your other Salesforce connectors. ### Step 1: Configure the Integration in Salesforce Create a dedicated integration user and assign the permissions required for both remediation actions. **To create the integration user:** 1. Sign in to Salesforce at `<your_tenant>.lightning.force.com`. 2. Click the gear icon and select **Setup**. 3. Search for **Users** in Setup and click **New User**. 4. Fill in the required details: - **User License:** Salesforce - **Profile:** Standard User 5. Click **Save**. 6. In Setup, search for **Permission Sets**, click **New**, and enter a label such as `Cato Remediation Actions`. 7. Click **Save**. 8. Open **System Permissions**, click **Edit**, and enable: - **API Enabled** - **Manage Users** - **Customize Application** 9. Click **Save**. 10. Select **Manage Assignments > Add Assignments** and select the integration user. 11. In Setup, search for **External Client App Manager** and click **New External Client App**. 12. Fill in **Basic Information** and set **Distribution State** to **Local**. 13. Under **API (Enable OAuth Settings)**, enable OAuth and configure: - **Callback URL:** `https://cc.catonetworks.com/redirect/cas/salesforce/callback` - **OAuth Scopes:** Manage user data via APIs (`api`) - **Flow Enablement:** Enable the Client Credentials Flow 14. Click **Create**, then open **Policies > Edit** and configure: - **Plugin Policies > Permitted Users:** Admin approved users are pre-authorized - **App Policies > Select Permission Sets:** Select the permission set created above - **Client Credentials Flow > Run As (Username):** Enter the integration user's username 15. Click **Save**. 16. Open **Settings > OAuth Settings > App Settings > Consumer Key and Secret** and authenticate. 17. Copy and save the **Consumer Key** and **Consumer Secret** so they can be entered into the CMA. 18. Copy and save the **Base URL** so it can be entered into the CMA. Use your organization's My Domain URL, including `https://`, as the **Base URL**. For example, use `https://yourcompany.my.salesforce.com`. For a sandbox, use its domain, such as `https://yourcompany--sandboxname.sandbox.my.salesforce.com`. ### 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:** 1. From the navigation menu, click **Resources > Integrations.** 2. Click the **Configured Integrations** tab. 3. Click **New**. The **New Integration** panel opens. 4. Select the **SaaS Application** you want to add. 5. In the **Capability** drop-down, select **Remediation Actions**. 6. Add the details created during step one. - **SaaS Application:** Salesforce - **Authentication:** Select **OAuth2 authentication for Salesforce** - **Name:** Enter a name for the integration - **Description:** Optionally, enter a description - **Consumer Key:** Enter the value saved in Step 1 - **Consumer Secret:** Enter the value saved in Step 1 - **Base URL:** Enter the My Domain URL saved in Step 1 7. Click **Save**. The app is visible on the **Integrated Apps** table with a **Connected** status. ## Known Limitations - **Email is not unique:** If multiple Salesforce users have the requested email, the action reports **Failed** and lists all matching usernames. The email match ignores letter case. - **Integration user:** The user the connector runs as cannot be disabled or have its sign-ins revoked by the connector. - **Subsequent sign-ins:** **Revoke Sign-In Sessions** leaves the account active and its password unchanged. The user, or anyone with their credentials, can sign in again. Use **Disable User** to block access. - **OAuth authorization permissions:** **Customize Application** is required to view other users' OAuth tokens and revoke their OAuth authorizations. Without it, the connector cannot list or revoke the target user's OAuth authorizations. The action can still end the user's sessions and report success. - **Partial failures:** Each session and authorization is processed independently. If some operations are unsuccessful, the others are still processed. The result is **Failed**, with counts of successful and unsuccessful operations and the first five errors. - **Connection status:** **Connected** confirms only that Cato can sign in and query users. A missing **Manage Users** permission is reported as a **Failed** result when an action runs. - **Authentication:** Only the OAuth 2.0 client credentials flow is supported. - **User records:** Deactivation preserves the user record. To restore access, reactivate the user in Salesforce Setup.