> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/basecamp.md).

# Basecamp

Use Basecamp data with Cortex XSIAM.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* **SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.
  * **saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Basecamp connector

Cortex XSIAM supports Basecamp accounts with Admin or Owner privileges.

To access Basecamp, Cortex XSIAM requires the following information, which you will specify during the connection process.

* **Client ID:** A unique identifier for your application, generated when you register an app in the 37signals Launchpad. Cortex XSIAM uses this value to identify your integration.
* **Client Secret:** A secret key generated within your registered Basecamp application. Cortex XSIAM uses the Client ID and Client Secret to authenticate to the Basecamp API.

Perform the following procedures in the order that they appear below.

#### Task 1: Create a Basecamp App

1. Navigate to the [37signals Launchpad](https://launchpad.37signals.com/) and log in using your credentials.
2. Click **Register another application**.
3. Enter your **App Name** (for example, `Cortex_Integration_YourOrg`).
4. Enter your **Company Name** and **Website URL**.
5. Under **Redirect URIs**, enter the specific URLs provided by the Cortex onboarding team for your environment.
6. Click **Save**.

#### Task 2: Retrieve Your Client ID and Client Secret

1. In the Launchpad, click on your registered application.
2. Locate the **Client ID** and **Client Secret**.
3. Copy both values and store them securely.

   > Do not continue to the next step unless you have copied the Client ID and Client Secret. You must provide these values to Cortex XSIAM during the onboarding process.

#### Task 3: Connect Basecamp to Cortex XSIAM

1. In Cortex XSIAM, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Basecamp.
4. Under **Recommended**, hover over the new Basecamp integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Client ID** and **Client Secret** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. Click **Connect**. Cortex XSIAM redirects you to the Basecamp login screen.
10. Log in with your Basecamp Admin or Owner credentials if prompted.
11. Review the permission request from your custom app and click **Allow** to grant Cortex XSIAM access to the requested data.
12. A confirmation message shows that Basecamp is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/basecamp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
