---
title: "Claude Enterprise: Configuring the SaaS Posture Integration"
slug: "claude-enterprise-configuring-the-saas-posture-integration"
updated: 2026-11-01T13:58:02Z
published: 2026-11-01T13:58:02Z
canonical: "knowledge.catonetworks.com/claude-enterprise-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.

# Claude Enterprise: 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 Claude Enterprise Integration

To configure the Claude Enterprise integration, enable the Compliance API and create a Compliance Access Key.

### Prerequisites

- Compliance API enabled for your organization
- Access as the primary owner of your Claude Enterprise organization to enable the Compliance API and create the key

### Step 1: Configure the Integration in Claude Enterprise

Enable the Compliance API in the parent organization, then create a key with the required SaaS Posture scopes. Compliance API enablement cascades to every linked organization. Compliance Access Key scopes cannot be changed after creation.

**To configure the integration in Claude Enterprise:**

1. Log in to [claude.ai](https://claude.ai) as the **primary owner** of your Claude Enterprise organization.
2. Open your profile menu and select **Organization settings**. Navigate to **Organization settings > API**.

You can also open the [API settings page](https://claude.ai/admin-settings/api-access) directly.
3. Under **APIs**, enable on the **Compliance API** toggle.
4. In the same **API** section, in the **Keys** area, click **Create key**.
5. Name the key and select the required scopes:

If you plan to use both Activity and SaaS Posture, select all three scopes when creating the key.
  - `read:compliance_org_data`
  - `read:compliance_user_data`
  - `read:compliance_activities`
6. Click **Create**.
7. Copy and save the **Compliance Access Key** so it can be entered into the CMA.

The key starts with `sk-ant-api01-` and is shown only once. Store it securely before continuing.

### 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.

For this integration, select **Claude Enterprise**.
5. In the **Capability** drop-down, select **SaaS Posture**.
6. Add the details created during step one.
  - **Auth**: Select **Compliance API key authentication for Claude Enterprise**.
  - **Name**: Enter a name for the connector.
  - **(Optional) Description**: Enter a description.
  - **Compliance API Key**: Paste the Compliance Access Key saved in step 1.
7. Click **Save**.

The app is visible on the **Integrated Apps** table with a **Connected** status.