--- title: "Box: Configuring the SaaS Posture Integration" slug: "box-configuring-the-saas-posture-integration" updated: 2026-11-01T13:57:48Z published: 2026-11-01T13:57:48Z canonical: "knowledge.catonetworks.com/box-configuring-the-saas-posture-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. # Box: Configuring the SaaS Posture Integration ## 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 [Cloud Apps Dashboard](/v1/docs/using-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.](https://knowledge.catonetworks.com/v1/docs/understanding-the-security-posture-of-your-saas-applications) To configure the SaaS Posture integration, you need to: 1. Configure the required settings in the SaaS application 2. Create the API connector in the CMA A CASB license is required for SaaS Posture integrations. ## Configuring the Box Integration To configure the Box integration, create an app. ### Prerequisites - A Box Enterprise license - Two-factor authentication enabled on the Box account that creates the app. ### Step 1: Configuring the Integration in your Box Tenant 1. Login to the Box Developer Console `https://<your_tenant>.app.box.com/developers/console` . 2. Click **Create a Platform App**. 3. Select **Custom App** and enter a name. Choose these configurations: - Purpose: Integration - Category: Security & Compliance 4. Choose **Server Authentication (Client Credentials Grant)** and click **Create App**. 5. On the **General Settings** page, copy and save the **Enterprise ID** so it can be entered into the CMA. 6. On the **Configuration** page, copy and save the **Client ID** so it can be entered into the CMA. 7. Click **Fetch Client Secret**, copy and save the secret so it can be entered into the CMA. 8. On the **Configuration** page, select **App + Enterprise Access**. 9. Under **Application Scopes**, select **Manage users** and **Manage enterprise properties**. 10. Under **Advanced Features**, select **Make API calls using the as-user header**, then click **Save Changes**. 11. Navigate to **Authorization** and click **Review and Submit.** 12. The Box admin receives an email and must approve the app. ### 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 **SaaS Posture**. 6. Add the details created during step one. 7. Click **Save**. ## Known Limitations - Box does not expose a last-login field on the managed-user object, the connector does not evaluate login inactivity - The connector evaluates enterprise and managed-user configuration. Per-file sharing exposure, connected application inventory, and activity events are handled by other Cato capabilities - Box-native MFA checks are not evaluated when SSO is required because MFA is then controlled by the identity provider - Settings that Box reports as not in use are not evaluated - External collaboration: The enterprise-wide control is available on supported Box Enterprise tiers and must be enabled by request through Box. If the control is unavailable and Box reports it as not in use, the related posture check is not evaluated. - Box Forms: Requires Box Enterprise Advanced and acceptance of the Box Forms Addendum. If Forms is unavailable and Box reports it as not in use, the related posture check is not evaluated. - Permanent deletion restrictions: The “People who can permanently delete content in Trash” control requires the Box Governance package. If the control is unavailable and Box reports it as not in use, the related posture check is not evaluated. - Changes made in Box are reflected after the next 8-hour posture collection