SPOG.AI integrates with Cortex XDR to centralize endpoint inventory, alerts, incidents, activity, and user access data. The integration enriches the SPOG.AI CMDB and supports endpoint monitoring, analytics, and approved remediation workflows.
Key Features
| Capability | Description |
|---|---|
| Endpoint Inventory | Collects endpoint identity, operating-system, agent, and activity data. |
| Alerts and Incidents | Retrieves Cortex XDR alerts and incident context for centralized analysis. |
| User Access | Optionally imports tenant users and assigned roles. |
| Remediation | Supports administrator-authorized response actions when the API key has sufficient access. |
| CMDB Enrichment | Maps Cortex endpoint and security data to SPOG.AI records. |
How the Integration Works
SPOG.AI calls the Cortex XDR API over HTTPS using an API key in the Authorization header and the API key ID in x-xdr-auth-id. Scheduled jobs collect endpoint and alert data; optional user ingestion and remediation depend on configured fields and API permissions.
Prerequisites
Before configuring the integration, ensure the following prerequisites are met:
- Tenant Admin authorization in SPOG.AI.
- API access and administrative access in Cortex XDR.
- Cortex XDR API URL, API key, and API key ID.
- HTTPS access from the SPOG Appliance to the Cortex XDR API on port 443.
Configuration
Configure the Cortex XDR integration in SPOG.AI by creating a dedicated API key, entering the connection details, and linking the integration to an appliance.
1. Create a Cortex XDR API Key
Create a dedicated key in Settings > Configurations > Integrations > API Keys.
- Select New Key and use a descriptive name such as SPOG Integration.
- Use a Standard key with Viewer access for monitoring or Instance Administrator only for approved remediation.
- Copy the API key and record its ID.
2. Configure Cortex XDR in SPOG.AI
Add Cortex Integration under Settings > Integrations.
- Enter the API URL, Authorization key, and x-xdr-auth-id.
- Save the integration and link it to the required appliance under Administration > Appliance > Integrations.
Configuration Fields
Use the fields below when creating the integration in SPOG.AI.
| Field | Requirement | Description |
|---|---|---|
| host | Mandatory | Cortex XDR API base URL. |
| Authorization | Mandatory | Cortex XDR API key sent in the Authorization header. |
| x-xdr-auth-id | Mandatory | Cortex XDR API key ID. |
| days | Optional | Lookback or filtering window used by the connector. |
| skip_endpoint_status | Optional | Skips endpoint-status collection when enabled. |
| fetch_users | Optional | Imports Cortex tenant users and direct roles. Default: true. |
| user_batch_size | Optional | Users sent to SPOG.AI per batch. Default: 25. |
| user_progress_every | Optional | Records processed between progress updates. Default: 100. |
| user_timeout | Optional | User API timeout in seconds. Default: 60. |
Security and Connectivity
- Use Viewer access for monitoring and reserve Instance Administrator for remediation.
- Rotate API keys at least every 90 days and store them in a vault.
- Allow HTTPS port 443 and allowlist the appliance egress IP where Cortex ACLs apply.
- Require TLS 1.2 or later.
Validation and Data Coverage
Run Test Connection, confirm endpoint and alert data in SPOG.AI, and use a Cortex API request to verify the API URL, key ID, and key. Common failures are 401 for invalid credentials, 403 for insufficient permissions, and timeouts for blocked network access.
| Data | Coverage |
|---|---|
| Endpoints | Inventory, status, agent, and activity metadata. |
| Alerts and Incidents | Severity, category, detection source, and related context. |
| Users | Tenant users and assigned roles when fetch_users is enabled. |
| Remediation | Response actions when administrator-level access is configured. |
Uninstalling the Integration
- Delete the Cortex XDR integration in SPOG.AI.
- Revoke the Cortex XDR API key.
- Remove appliance linking and any related IP allowlist entries.