Upwind Catalog Loader (Ingestion API)

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index


Attribute Value
Connector ID UpwindCatalogLoader
Publisher Upwind
Used in Solutions Upwind
Collection Method Azure Function
Connector Definition Files UpwindCatalogLoader_API_FunctionApp.json
Ingestion API Log Ingestion API — Sibling ARM template declares DCR / Log Ingestion API resources
Microsoft Learn View on Learn

The Upwind Catalog Loader data connector ingests compute platform assets from the Upwind cloud security platform into a Microsoft Sentinel custom table using an Azure Function and the Azure Monitor Ingestion API (DCE/DCR).

Upwind provides runtime-powered cloud security, correlating cloud posture with live workload context. This connector surfaces your Upwind inventory catalog — compute platform assets across AWS, GCP, and Azure — directly into Microsoft Sentinel for correlation, hunting, and incident enrichment.

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
UpwindCatalogAssets_CL ✓ ✓ ✓

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This connector uses Azure Functions and the Azure Monitor Ingestion API (DCE/DCR) to push Upwind catalog assets into Microsoft Sentinel. The ARM template automatically creates the Data Collection Endpoint, custom log table (UpwindCatalogAssets_CL), Data Collection Rule, and role assignment. This might result in additional data ingestion costs. Check the Azure Functions pricing page and Azure Monitor pricing page for details.

(Optional) Securely store your Upwind client secret in Azure Key Vault. Set KEY_VAULT_URI and UPWIND_SECRET_NAME app settings to enable Key Vault retrieval. The function will fall back to the UPWIND_CLIENT_SECRET app setting if Key Vault is not configured.

1. STEP 1 – Obtain Upwind API credentials

  1. Log in to the Upwind platform.
  2. Navigate to Settings → API Keys.
  3. Create a new API key and note the Client ID and Client Secret.
  4. Navigate to Settings → Organization and note your Organization ID.

2. STEP 2 – Deploy the Azure Function App

Click Deploy to Azure and fill in the parameters. The template automatically creates the DCE, UpwindCatalogAssets_CL table, DCR, role assignment, and Function App.

Deploy To Azure

Parameters to fill in:

Parameter Description
WorkspaceName Name of your Log Analytics / Microsoft Sentinel workspace
WorkspaceResourceGroup (optional) Resource group containing that workspace, if different from the one you deploy into
UpwindOrgId Upwind Organization ID from Step 1
UpwindClientId Upwind API Client ID from Step 1
UpwindClientSecret Upwind API Client Secret from Step 1
AppInsightsWorkspaceResourceID Full Resource ID of the Log Analytics workspace (from Log Analytics workspace → Properties)
UpwindCatalogSchedule (optional, default hourly) When the function runs. Each run fetches what changed since the previous scheduled run

3. Updating an existing deployment

Updating or reinstalling this solution from Content Hub doesn't change the code your Function App runs. To get the latest connector code, click Deploy to Azure in Step 2 again and deploy into the same resource group with the same FunctionName. The deployment updates the existing Function App, tables and Data Collection Rule in place.

The deployment resets the Function App's app settings to the template's values. Note any settings you added or changed yourself (for example KEY_VAULT_URI, UPWIND_SECRET_NAME or UPWIND_FULL_SYNC_INTERVAL_HOURS) and set them again afterwards.

To confirm the update, check the Function App's logs after the next run: the latest version logs Fetching catalog assets updated since instead of fetching the whole catalog on every run.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index