> 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/vmware/vmware.md).

# VMWare

Configure VMware security posture capabilities for 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):

* Security Posture: 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 VMware connector

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

* **API token**: The API token generated for the organization.
* **Organization ID**: Your VMware Cloud Services Organization ID.
* **MFA secret key**: (If MFA is configured for tokens) The MFA secret key for the account.

#### Task 1: Connect to the VMware API

1. Log in to VMware Cloud Services using an account assigned to the **Organization Owner** role.
2. Generate and copy an **API token** for the organization. Configure the API token to the following specifications:
   * Set **Organization Roles** access to **Organization Owner**.
   * Set **Service Roles** to **Skyline Advisor**.
   * Select the **OpenID** scope.
   * (Optional) Select the email preference option to receive notifications when the token is about to expire.
3. Copy your **Organization ID** from your profile.
4. (Optional) Activate MFA for tokens associated with the account and copy the **MFA secret key**.

#### Task 2: Connect VMware to Cortex XSIAM

1. In Cortex XSIAM, navigate to **Settings** > **Data Sources & Integrations**.
2. Click **+ Add new**.
3. On the **Add Data Sources or Integrations** page, search for **VMware**.
4. Under **Recommended**, hover over the VMware 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 **Connection**, provide the following:
   * API token
   * Organization ID
   * MFA secret key (if MFA is configured for tokens)
8. Click **Next**.
9. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments. Click **Next**.
10. A confirmation message indicates that VMware 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/vmware/vmware.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.