Sysdig Secure

The Sumo Logic app for Sysdig Secure integrates Sysdig Secure’s security insights with Sumo Logic's powerful analytics to help security teams monitor and protect Kubernetes and containerized environments. It provides real-time visibility into vulnerabilities, compliance, and threats by analyzing security events from various sources such as Kubernetes clusters, container registries, and runtime environments. With it's intuitive dashboards, Sysdig Secure helps security professionals understand risks, assess vulnerability impact, and monitor runtime behavior to detect threats before they affect production environments. By centralizing data and presenting it through clear visualizations, the app enables effective collaboration, proactive defense, faster remediation, and continuous compliance in dynamic, containerized environments.

info

This app includes built-in monitors. For details on creating custom monitors, refer to Create monitors for Sysdig Secure app.

Log types

This app uses Sumo Logic’s Sysdig Secure Source to collect the detected open vulnerabilities and active assets from the Sysdig Secure platform.

Sample log messages

Runtime Scan

{
    "mainAssetName": "mcr.microsoft.com/azure-policy/policy-kubernetes-addon-prod:1.10.1",
    "policyEvaluationResult": "failed",
    "resourceId": "sha256:73fce251be0bb71b38a642a3eed2831e5cb26e02f49023bf89fa76ce7ab2ca7d",
    "resultId": "18393741b66ab761884752af58d8ac32",
    "runningVulnTotalBySeverity": {
        "critical": 0,
        "high": 0,
        "low": 0,
        "medium": 0,
        "negligible": 0
    },
    "sbomId": null,
    "scope": {
        "asset.type": "workload",
        "kubernetes.cluster.name": "gke-alliances-test",
        "kubernetes.namespace.name": "kube-system",
        "kubernetes.pod.container.name": "konnectivity-agent-metrics-collector",
        "kubernetes.workload.name": "konnectivity-agent",
        "kubernetes.workload.type": "deployment",
        "workload.name": "konnectivity-agent",
        "workload.orchestrator": "kubernetes"
    },
    "vulnTotalBySeverity": {
        "critical": 0,
        "high": 1,
        "low": 1,
        "medium": 0,
        "negligible": 0
    }
}

Full Scan of Vulnerability

{
  "_resultId": "18392a48e55ef07e827e47719a5295d1",
  "_resourceId": "1489835514684399099",
  "assetType": "host",
  "stage": "runtime",
  "metadata": {
    "architecture": "x86_64",
    "hostId": "1489835514684399099",
    "hostName": "eksa-vsphere-conformitron-md-0-28n7h-vzqdk",
    "os": "bottlerocket 1.26.1"
  },
  "vulnerability": {
    "c360bd86-4f6d-49bf-b9ce-9fa26d2e4eac": {
      "cisaKev": {},
      "cvssScore": {
        "score": 5.5,
        "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
        "version": "3.1"
      },
      "disclosureDate": "2024-11-19",
      "exploitable": false,
      "fixVersion": "6.1.128",
      "mainProvider": "bottlerocket",
      "name": "CVE-2024-50304",
      "packageRef": "ebe6d690-3753-4749-8001-b5391b9ba0a3",
      "providersMetadata": {
        "amazon": {
          "publishDate": "2025-02-12T22:57:00Z"
        },
        "euleros": {
          "publishDate": "2025-02-08T14:57:02Z"
        },
        "first.org": {
          "epssScore": {
            "score": 0.00045,
            "percentile": 0.13532,
            "timestamp": "2025-04-23T00:00:00Z"
          }
        },
        "nvd": {
          "publishDate": "2024-11-19T18:15:22.343Z",
          "cvssScore": {
            "version": "3.1",
            "score": 5.5,
            "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
          },
          "severity": "medium"
        },
        "rhel": {
          "publishDate": "2024-11-19T00:00:00Z",
          "cvssScore": {
            "version": "3.1",
            "score": 5.5,
            "vector": "AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
          },
          "severity": "medium"
        },
        "ubuntu": {
          "publishDate": "2024-11-19T18:15:00Z"
        },
        "vulndb": {
          "publishDate": "2024-11-19T00:00:00Z"
        }
      },
      "riskAcceptRefs": null,
      "severity": "medium",
      "solutionDate": "2025-02-25"
    }
  }
}

Full Scan of Package

{
  "_resultId": "18392a48e55ef07e827e47719a5295d1",
  "_resourceId": "1489835514684399099",
  "assetType": "host",
  "stage": "runtime",
  "metadata": {
    "architecture": "x86_64",
    "hostId": "1489835514684399099",
    "hostName": "eksa-vsphere-conformitron-md-0-28n7h-vzqdk",
    "os": "bottlerocket 1.26.1"
  },
  "package": {
    "8edec454-c929-49b0-86e8-d72412592109": {
      "isRemoved": false,
      "isRunning": false,
      "name": "google.golang.org/grpc",
      "path": "/usr/bin/containerd-shim",
      "type": "golang",
      "version": "v1.59.0",
      "vulnerabilitiesRefs": null
    }
  }
}

Sample queries

Total Running Critical Severity Vulnerabilities
_sourceCategory=Labs/SysdigSecure mainAssetName
| json "mainAssetName", "resourceId", "runningVulnTotalBySeverity.critical","vulnTotalBySeverity.critical", "runningVulnTotalBySeverity.high", "vulnTotalBySeverity.high", "runningVulnTotalBySeverity.medium", "vulnTotalBySeverity.medium", "runningVulnTotalBySeverity.low", "vulnTotalBySeverity.low", "runningVulnTotalBySeverity.negligible", "vulnTotalBySeverity.negligible", "policyEvaluationResult", "$['scope']['asset.type']", "$['scope']['kubernetes.cluster.name']", "$['scope']['workload.name']", "$['scope']['kubernetes.workload.type']" as asset_name, resource_id, running_critical_vuln, total_critical_vuln, running_high_vuln, total_high_vuln, running_medium_vuln, total_medium_vuln, running_low_vuln, total_low_vuln, running_negligible_vuln, total_negligible_vuln, policy_result, asset_type, kubernete_cluster, workload_name, kubernete_workload_type nodrop

// global filters
| where asset_type matches "{{asset_type}}"
| where policy_result matches "{{policy_evaluation_result}}"
| where kubernete_cluster matches "{{kubernete_cluster}}"

// panel specific
| where !isNull(asset_name)
| first(running_critical_vuln) as running_critical_vuln group by asset_name, resource_id
| sum(running_critical_vuln)

Resources by Package Count
_sourceCategory=sysdig_secure_app
| json "_resourceId", "assetType", "metadata.os", "metadata.architecture", "vulnerability", "package" as resource_id, asset_type, os, architecture, vuln, package nodrop
| extract field=vuln "\"severity\":\s*\"(?<severity>[^\"]+)\"" nodrop
| extract field=vuln "\"exploitable\":\s*(?<exploitable>true|false)" nodrop

// global filters
| where os matches "{{os}}"
| where architecture matches "{{architecture}}"
| where isBlank(severity) or severity matches "{{severity}}"
| where isBlank(exploitable) or exploitable matches "{{exploitable_vuln}}"

// panel specific
| where !isNull(asset_type) and !isBlank(package)
| count as package_count by resource_id
| sort by package_count

Collection configuration and app installation

Depending on the set up collection method, you can configure and install the app in three ways:

Create a new collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under a new Sumo Logic Collector and later install the app, or
Use an existing collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under an existing Sumo Logic Collector and later install the app, or
Use existing source and install the app. Use your existing configured Sumo Logic Cloud-to-Cloud (C2C) source and install the app.

info

Use the Cloud-to-Cloud Integration for Sysdig Secure to create the source and use the same source category while installing the app. By following these steps, you can ensure that your Sysdig Secure app is properly integrated and configured to collect and analyze your Sysdig Secure data.

Create a new collector and install the app

To set up collection and install the app, do the following:

note

Next-Gen App: To install or update the app, you must be an account administrator or a user with Manage Apps, Manage Monitors, Manage Fields, Manage Metric Rules, and Manage Collectors capabilities depending upon the different content types part of the app.

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Install App.
note
Sometimes this button says Add Integration.
In the Set Up Collection section of your respective app, select Create a new Collector.
1. Collector Name. Enter a Name to display the Source in the Sumo Logic web application. The description is optional.
2. Timezone. Set the default time zone when it is not extracted from the log timestamp. Time zone settings on Sources override a Collector time zone setting.
3. (Optional) Metadata. Click the +Add Metadata link to add a custom log Metadata Fields. Define the fields you want to associate, each metadata field needs a name (key) and value.
  - A green circle with a checkmark is shown when the field exists and is enabled in the Fields table schema.
  - An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema or is disabled it is ignored, known as dropped.
4. Click Next.
Configure the source as specified in the Info box above, ensuring all required fields are included.
In the Configure section of your respective app, complete the following fields.
1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Each panel slowly fills with data matching the time range query received since the panel was created. Results will not immediately be available but will be updated with full graphs and charts over time.

Use an existing collector and install the app

To set up the source in the existing collector and install the app, do the following:

note

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Install App.
note
Sometimes this button says Add Integration.
In the Set Up Collection section of your respective app, select Use an existing Collector.
From the Select Collector dropdown, select the collector that you want to set up your source with and click Next.
Configure the source as specified in the Info box above, ensuring all required fields are included.
In the Configure section of your respective app, complete the following fields.
1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Use an existing source and install the app

To skip collection and only install the app, do the following:

note

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Install App.
note
Sometimes this button says Add Integration.
In the Set Up Collection section of your respective app, select Skip this step and use existing source and click Next.
In the Configure section of your respective app, complete the following fields.
1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Viewing the Sysdig Secure dashboards

All dashboards have a set of filters that you can apply to the entire dashboard. Use these filters to drill down and examine the data to a granular level.

You can change the time range for a dashboard or panel by selecting a predefined interval from a drop-down list, choosing a recently used time range, or specifying custom dates and times. Learn more.
You can use template variables to drill down and examine the data on a granular level. For more information, see Filtering Dashboards with Template Variables.
Most Next-Gen apps allow you to provide the scope at the installation time and are comprised of a key (_sourceCategory by default) and a default value for this key. Based on your input, the app dashboards will be parameterized with a dashboard variable, allowing you to change the dataset queried by all panels. This eliminates the need to create multiple copies of the same dashboard with different queries.

Runtime Scan

The Sysdig Secure - Runtime Scan dashboard provides real-time insights into the security posture of assets and Kubernetes environments during runtime. It aggregates data from Sysdig Secure’s runtime scanning API, allowing you to monitor active threats and vulnerabilities in running assets. Key features highlight vulnerabilities, track security events such as privilege escalations, and identify compliance violations. By presenting detailed information on runtime risks and potential attack vectors, the dashboard helps security professionals effectively mitigate threats and maintain secure, compliant environments.
Runtime-Scan

Full Scan

The Sysdig Secure - Full Scan dashboard serves as a strategic assessment tool, providing detailed information on asset packages and vulnerabilities based on results from the runtime scan API. It illustrates asset evolution over time and their distribution across operating systems and architectures. The dashboard also highlights the most frequent vulnerabilities, exploitable vulnerabilities, and detailed package data. By identifying the most at-risk assets, it supports the maintenance of a robust and secure infrastructure.
Full-Scan

Create monitors for Sysdig Secure app

From your App Catalog:

From the Sumo Logic navigation, select App Catalog.
In the Search Apps field, search for and then select your app.
Make sure the app is installed.
Navigate to What's Included tab and scroll down to the Monitors section.
Click Create next to the pre-configured monitors. In the create monitors window, adjust the trigger conditions and notifications settings based on your requirements.
Scroll down to Monitor Details.
Under Location click on New Folder.
note
By default, monitor will be saved in the root folder. So to make the maintenance easier, create a new folder in the location of your choice.
Enter Folder Name. Folder Description is optional.
tip
Using app version in the folder name will be helpful to determine the versioning for future updates.
Click Create. Once the folder is created, click on Save.

Sysdig Secure monitors

Name	Description	Trigger Type (Critical / Warning / MissingData)	Alert Condition
`Sysdig Secure - Critical Vulnerabilities`	This alert is triggered when the assets with 5 or more critical severity vulnerabilities are highlighted.	Critical	Count >= 5

Upgrading the Sysdig Secure app (Optional)

To update the app, do the following:

note

Select App Catalog.
In the Search Apps field, search for and then select your app.
Optionally, you can identify apps that can be upgraded in the Upgrade available section.
To upgrade the app, select Upgrade from the Manage dropdown.
1. If the upgrade does not have any configuration or property changes, you will be redirected to the Preview & Done section.
2. If the upgrade has any configuration or property changes, you will be redirected to the Setup Data page.
3. In the Configure section of your respective app, complete the following fields.
  1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
4. Click Next. You will be redirected to the Preview & Done section.

Post-update

Your upgraded app will be installed in the Installed Apps folder and dashboard panels will start to fill automatically.

note

See our Release Notes changelog for new updates in the app.

To revert the app to a previous version, do the following:

Select App Catalog.
In the Search Apps field, search for and then select your app.
To version down the app, select Revert to < previous version of your app > from the Manage dropdown.

Uninstalling the Sysdig Secure app (Optional)

To uninstall the app, do the following:

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Uninstall.

Log types​

Sample log messages​

Sample queries​

Collection configuration and app installation​

Create a new collector and install the app​

Use an existing collector and install the app​

Use an existing source and install the app​

Viewing the Sysdig Secure dashboards​​​

Runtime Scan​

Full Scan​

Create monitors for Sysdig Secure app​

Sysdig Secure monitors​

Upgrading the Sysdig Secure app (Optional)​

Uninstalling the Sysdig Secure app (Optional)​

Log types

Sample log messages

Sample queries

Collection configuration and app installation

Create a new collector and install the app

Use an existing collector and install the app

Use an existing source and install the app

Viewing the Sysdig Secure dashboards

Runtime Scan

Full Scan

Create monitors for Sysdig Secure app

Sysdig Secure monitors

Upgrading the Sysdig Secure app (Optional)

Uninstalling the Sysdig Secure app (Optional)