> 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/data-security-documentation/cortex-data-security-data-sources-and-connectors/connectors.md). # Connectors Connectors represent the new, strategic approach for integrating third-party services and data sources into Cortex Data Security. A connector consolidates all of a vendor's security capabilities, such as log collection, automation and remediation, and posture management, into a single, uniquely named entry with a guided configuration wizard. ### Benefits of the unified connector experience This unified approach provides several key benefits: * **Selective capability onboarding**: For vendors with multiple services, you can choose to enable the full suite at once or select individual **sub-capabilities** (integrations) as needed. Additional capabilities can be enabled later without disrupting your existing configuration. * **Wizard-driven setup**: The configuration wizard dynamically adjusts its steps based on the specific capabilities you choose to enable for that vendor. * **Centralized vault credentials**: Authenticate your connectors directly with stored vault credentials instead of manually entering credentials, extending standard platform security across all capabilities.\ You can configure vault credentials under **Settings** → **Configurations** → **Integrations** → **Credentials**. ### The connector configuration experience The configuration workflow depends on the specific connector you are enabling. The transition to the unified experience is designed to support both existing and new customers within a single guide. Each connector topic specifies the license supported. When using a unified connector, you follow a guided wizard within Cortex Data Security. ### Connectivity and capabilities Unified connectors group vendor functionality into specific security capabilities. Depending on the connector selected, the wizard will present options based on the following possible capabilities: * **Automation and Remediation**: Run automated actions and remediation commands against the connected service. * **Fetch Issues**: Fetch issues and incidents from the connected service for investigation and response. * **Log Collection**: Collect and ingest logs and events from the connected service. * **Threat Intelligence and Enrichment**: Ingest threat intelligence and enrich indicators using data from the connected service. * **Fetch Assets and Vulnerabilities**: Fetch assets and vulnerabilities from the connected service into the Unified Asset Inventory. * **Fetch Secrets**: Retrieve secrets and credentials from the connected service. * **Security Posture**: Detect, monitor, and alert on the security settings and configurations of your SaaS applications. * **Data Security**: Scan and protect sensitive data, including files, attachments, and records within the service. * **Identity Posture**: Maintain visibility and control over SaaS-based identities, including users, groups, roles, and granular permissions. * **Agent Security Scanning**: Monitor and assess the security posture and activity of agents within the service environment. For connectors that support multiple services or complex configurations, these capabilities may be further divided into **sub-capabilities**. For example, a single connector might allow you to independently enable "Users" and "Groups" under the Identity Posture capability. Access to specific connectors and their individual sub-capabilities is determined by your tenant license. Connectors are configured by navigating to **Settings → Data Sources & Integrations → + Add New**. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/data-security-documentation/cortex-data-security-data-sources-and-connectors/connectors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.