---
title: "Upwind Security"
slug: "upwind"
updated: 2026-03-06T22:49:03Z
published: 2026-03-06T23:00:02Z
canonical: "docs.hunters.ai/upwind"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hunters.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Upwind Security

Self Service Ingestion

          

Connect this data source on your own, using the Hunters platform.

****TL;DR****

| Supported data types | 3rd party detection | Hunters detection | IOC search | Search | Table name | Log format | Collection method |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Upwind Security Logs - Detection Logs | ✅ | ✅ |  | ✅ | upwind_security_logs | NDJSON | S3 and API |
| Upwind Security Logs - Stories Logs | ✅ | ✅ |  | ✅ | upwind_story_logs | NDJSON | API |

---

## Overview

Cloud Security Happens at Runtime is a runtime-powered Cloud-Native Application Protection Platform![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(241).png) (CNAPP) designed to secure cloud environments in real time. It provides deep visibility into workloads, APIs, identities, and containers by analyzing actual runtime behavior. Security teams use Upwind to detect threats, prioritize risks, and respond instantly based on real usage context. The platform reduces alert noise by mapping vulnerabilities to live assets and connections. Upwind also supports shift-left security by connecting runtime insights back into CI/CD workflows.

## Supported data types

### Upwind Security Logs - Detection Logs

**Table name:** `upwind_security_logs`

collects runtime threat detections from the Upwind CNAPP platform. It ingests high-fidelity alerts about suspicious process behavior, reverse shells, privilege escalations, and other MITRE-mapped tactics within containerized workloads. Each log includes severity, resource context, command-line activity, and detection metadata. The data is enriched with MITRE ATT&CK mappings and linked to cloud assets in Kubernetes environments.

Learn more [here](https://www.upwind.io/).

## Send data to Hunters

Hunters supports the ingestion of Upwind logs (Detection) via an intermediary AWS S3 bucket.

**To connect Upwind logs using AWS S3 bucket:**

1. Export your logs from Upwind to an AWS S3 bucket by following [this guide](https://docs.upwind.io/integrations/monitoring-and-logging/s3?_highlight=s3#overview).
2. Once the export is completed and the logs are collected to S3, follow the steps in [this section](/v1/docs/connect-data-through-aws-s3).

Hunters also supports the collection of logs from Upwind using API.

**To connect Upwind logs using API:**

1. Official Upwind’s [Api refs](https://docs.upwind.io/restapi/v1/introduction)
2. Official Upwind’s [User guide](https://docs.upwind.io/)
3. Official [Upwind’s docs center](https://docs.upwind.io/)
4. You can ask Upwind to support you with the full onboarding guide in case of need, but here’s a high level way to do it:
5. Go to settings of your account and click on **“Connect organization or account”**
6. Choose a Cloud provider to sync your assets with the Upwind platform: ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(305).png)Once you’d click on “Connect organization or account” you’ll reach:![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(306).png)

Please choose your cloud-provider, you’d like to integrate with Upwind.
7. Fill in the details of you account-id, org-id, arn etc.. and generate new client credentials, on this next page: ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(307).png)
8. In the Settings menu - generate new credentials for API-method and make sure to use your client-id and secret on our portal SSI integrations page: ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(308).png) Once you’d click on “Generate credentials” you’d see, add would have to pick “API” and “Generate new client credentials”:

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(309).png)
9. Once you’d have the client-id, org-id, client-secret, you can go to the Hunters SSI page, search for upwind and try to connect to the API method: ![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(311).png) And then fill in:

![](https://cdn.document360.io/5f63f0e0-3c70-4d00-b623-82493be0bde5/Images/Documentation/image(310).png)
10. Now you should be connected and well ingesting logs 😀😀😀

## Expected format

Logs are expected in JSON format for the [upwind detection](https://docs.upwind.io/restapi/v1/list-threat-detections):

```json
{
  "category": "PROCESS",
  "description": "Network sniffing involves the interception and analysis of network traffic flowing between devices on a network. Attackers may use network sniffing tools to capture sensitive information, such as passwords or account credentials, as they travel across a network. This can lead to unauthorized access or data exfiltration.",
  "first_seen_time": "2025-07-11T09:34:07Z",
  "id": "uwd-xxxxxxxxxxxxxxxx",
  "last_seen_time": "2025-07-11T09:34:07Z",
  "links": [
    {
      "href": "https://api.upwind.io/v1alpha1/detections/uwd-xxxxxxxxxxxxxxxx",
      "rel": "SELF"
    },
    {
      "href": "https://console.upwind.io/threats?selectedDetectionId=uwd-xxxxxxxxxxxxxxxx",
      "rel": "VIEW"
    }
  ],
  "mitre_attacks": [
    {
      "links": [
        {
          "href": "https://attack.mitre.org/tactics/TA0006",
          "rel": "TACTIC"
        },
        {
          "href": "https://attack.mitre.org/techniques/T1040",
          "rel": "TECHNIQUE"
        }
      ],
      "tactic_id": "TA0006",
      "tactic_name": "Credential Access",
      "technique_id": "T1040",
      "technique_name": "Network Sniffing"
    }
  ],
  "occurrence_count": 2,
  "resource": {
    "cloud_account_id": "byoc-<redacted>",
    "cloud_provider": "BYOC",
    "cluster_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "id": "ep-xxxxxxxxxxxxxxxx",
    "name": "<redacted-node-name>",
    "region": "byoc-<redacted-region>",
    "type": "KUBERNETES_NODE"
  },
  "severity": "CRITICAL",
  "status": "OPEN",
  "title": "A Kubernetes Node is executing a network sniffing tool",
  "triggers": [
    {
      "events": [
        {
          "data": {
            "command": "tcpdump -i <interface> -w <file> port <port>",
            "description": "Tcpdump can be used by hackers to capture network traffic, which can aid in identifying potential vulnerabilities. Additionally, it can be used to analyze captured traffic to identify sensitive information, such as login credentials or credit card numbers.",
            "execution_count": 2,
            "last_process_tree": [
              {
                "command": "tcpdump -i <interface> -w <file> port <port>",
                "host_parent_process_id": 3286645,
                "host_process_id": 3313708,
                "name": "<redacted-binary>",
                "start_time": "2025-07-11T09:33:13Z"
              }
            ],
            "name": "tcpdump",
            "pattern": "FREQUENT",
            "status": "TERMINATED",
            "user_name": "<redacted-user>",
            "validation": ["MD5"]
          },
          "description": "Execution of suspicious process",
          "type": "PROCESS_EXECUTION"
        }
      ],
      "policy_id": "dp-xxxxxxxx-xxxx-xx",
      "policy_name": "network sniffing processes"
    }
  ],
  "type": "network_sniffing",
  "upwind_console_link": "https://console.upwind.io/threats?mainPageTab=Detections&sidePanel=detection-details&sidePanelItemId=uwd-xxxxxxxxxxxxxxxx"
}
```
