Skip to main content

Upwind

Visualize Upwind cloud security posture including vulnerability findings, threat detections, configuration findings, and inventory assets. Monitor changes through queries and alerts.

Installation​

Prerequisites in Upwind​

Before configuring the integration in JupiterOne, you must generate API credentials in Upwind.

info

You will need the following parameters:

  • Client ID and Client Secret — OAuth 2.0 credentials for API authentication
  • Organization ID — Your Upwind organization identifier (e.g., org_123456789)
  • Region — The regional API endpoint your Upwind account uses: us, eu, or me

Step 1: Generate API Credentials in Upwind​

  1. Log in to the Upwind console.
  2. Navigate to Settings > Credentials.
  3. Click Generate Credential.
  4. Select API (Call the Upwind API service).
  5. Click Generate New Credentials.
  6. Copy and securely store the Client ID and Client Secret. The client secret is shown only once.
warning

Treat your client credentials like a password. Store them securely and never share them in plain text.

Step 2: Find Your Organization ID​

Your Organization ID is available in the Upwind console URL or in your account settings. It follows the format org_ followed by alphanumeric characters (e.g., org_123456789).

Step 3: Determine Your Region​

Upwind operates in three regional environments. Select the region that matches your Upwind deployment:

RegionAPI Endpoint
US (default)https://api.upwind.io
EUhttps://api.eu.upwind.io
MEhttps://api.me.upwind.io

Step 4: Configure the Integration in JupiterOne​

Navigate to the Integrations tab in JupiterOne and select Upwind. Click New Instance to begin.

Creating an Upwind instance requires the following:

  • The Account Name used to identify this Upwind account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to help identify the integration instance (optional).

  • Polling Interval that suits your monitoring needs. You may leave this as DISABLED and invoke the integration manually.

  • Your Upwind Client ID and Client Secret from Step 1.

  • Your Upwind Organization ID from Step 2.

  • Your Upwind Region (us, eu, or me). Defaults to us if not specified.

Data Volume Configuration​

The following settings control which findings and detections are ingested. Narrowing these filters reduces ingestion volume and keeps your graph focused on the most relevant security data.

Vulnerability Findings​

FieldDescriptionDefaultOptions
Vulnerability SeveritySeverity levels of vulnerability findings to include. Leave all unselected to ingest all severities.Critical, HighCritical, High, Medium, Low, Unclassified, Other
Exploitable OnlyWhen enabled, only ingests vulnerabilities marked as exploitable.Disabled—
Fix Available OnlyWhen enabled, only ingests vulnerabilities that have a fix available.Disabled—

Configuration Findings​

FieldDescriptionDefaultOptions
Configuration Finding SeveritySeverity levels of configuration findings to include. Leave all unselected to ingest all severities.Critical, HighCritical, High, Medium, Low
Failed Findings OnlyWhen enabled, only ingests configuration findings with a FAIL status, excluding findings that pass.Disabled—
Configuration Findings Ingestion WindowHow far back to look for configuration findings. Reducing this window limits the volume of findings ingested on each run.30 days7, 15, 30, 60, 90, 180, 365

Threat Detections​

FieldDescriptionDefaultOptions
Threat Detection SeveritySeverity levels of threat detections to include. Leave all unselected to ingest all severities.Critical, HighCritical, High, Medium, Low
Threat Detections Ingestion WindowHow far back to look for threat detections. Reducing this window limits the volume of detections ingested on each run.30 days7, 15, 30, 60, 90, 180, 365

Click Create once all values are provided to finish setting up the integration.

Next steps​

Once configured, the integration will run on the polling interval you selected, populating data in JupiterOne. See the Instance management guide to learn more about managing integration instances.