Sysdig Secure Source

Sysdig Secure is a comprehensive security platform that provides continuous security and compliance monitoring for cloud-native environments. This is designed specifically to address the security needs of modern containerised and Kubernetes infrastructures. Sysdig Secure enables organisations to detect, prevent, and respond to security threats and ensure compliance in real-time.

Data collected

Polling Interval	Data
24 hours	Runtime Scan Result
5 minutes	Full Scan Result

Setup

Vendor configuration

The Sysdig Secure Source supports API token-based authentication and requires you to provide the Sysdig Secure Base URL and API token to access the data.

Base URL

The Base URL is the Sysdig Secure domain URL that corresponds to the region in which the account is created. For example, https://api.us2.sysdig.com.

Bearer token

The Bearer Token is the API security token used to authenticate with Sysdig HTTP API. Follow the steps below to collect your Sysdig API token:

1. Sign in to the Sysdig Secure platform.
2. Select Settings from the User Menu.
3. In the Settings page, select User Profile to view the Sysdig Secure API token in the UI.
4. Copy the token or click the Reset Token button to generate a new one.

info

When a token is reset, the previously issued token will immediately become invalid.

Source configuration

When you create a Sysdig Secure Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector and Source.

To configure a Sysdig Secure Source:

1. Classic UI. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
   New UI. In the Sumo Logic top menu select Configuration, and then under Data Collection select Collection. You can also click the Go To... menu at the top of the screen and select Collection.
2. On the Collection page, click Add Source next to a Hosted Collector.
3. Search for and select Sysdig Secure.
4. Enter a Name for the Source. The description is optional.
5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
6. (Optional) Fields. Click the +Add button to define the fields you want to associate. Each field needs a name (key) and value.
   •  A green circle with a check mark is shown when the field exists in the Fields table schema.
   •  An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema is ignored, known as dropped.
7. Base URL. Enter the Sysdig Secure platform Base URL. For example, https://api.us2.sysdig.com.
8. Bearer Token. Enter the Sysdig Secure API token collected from the Sysdig Secure platform. For example, t3fPdsbxxxxxxxxxp4D6hbi4.
9. (Optional) Filters. Click the +Add button to define the filters you want to associate. Each filter needs a Field Name (key) and Field Value (value). For key-value pairs, the length is set to 256 characters and the API accepts a maximum length of 1024 characters for the filter.
10. (Optional) Processing Rules for Logs. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
11. When you are finished configuring the Source, click Save.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See Use JSON to Configure Sources for details. 

Parameter	Type	Value	Required	Description
schemaRef	JSON Object	{“type”: “Sysdig Secure”}	Yes	Define the specific schema type.
sourceType	String	"Universal"	Yes	Type of source.
config	JSON Object	Configuration object	Yes	Source type specific values.

Configuration Object

Parameter	Type	Required	Default	Description	Example
name	String	Yes	null	Type a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source.	"mySource"
description	String	No	null	Type a description of the source.	"Testing source"
category	String	No	null	Type a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details.	"mySource/test"
fields	JSON Object	No	null	JSON map of key-value fields (metadata) to apply to the collector or source. Use the boolean field _siemForward to enable forwarding to SIEM.	{"_siemForward": false, "fieldA": "valueA"}
baseURL	String	Yes	null	The Sysdig base URL of your region.	https://api.us2.sysdig.com
apiToken	String	Yes	null	The API token of your Sysdig account.	t3fPdsbxxxxxxxxxp4D6hbi4
filters	Array	No	null	An array of key-value pairs to filter the data. For key-value pairs, the length is set to 256 characters and the API accepts a maximum length of 1024 characters for the filter.

JSON example

{
	"api.version": "v1",
	"source": {
		"config": {
                	"name": "Sysdig",
  					"baseURL": "https://us2.app.sysdig.com",
  					"bearerToken": "wdwxxxxxqwedwedxxxxxqewdxxxxxxqwedxxxx",
  					"scope": [
    			        		{
      				            "fieldName": "Field",
      				            "fieldValue": "Value"
    			        		}
  			        		]
},
		            "schemaRef": {
            		            "type": "Sysdig"
        	                     },
        	        "sourceType": "Universal"
}}

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "sysdig-secure-source" {
  collector_id = sumologic_collector.collector.id
  schema_ref = {
    type = "Sysdig"
  }
  config = jsonencode({
                        "name": "Sysdig",
  			                "baseURL": "https://us2.app.sysdig.com",
  			                "bearerToken": "wdwxxxxxqwedwedxxxxxqewdxxxxxxqwedxxxx",
  			                "scope": [
    			                        {
      				                      "fieldName": "Field",
      				                      "fieldValue": "Value"
    			                        }
  			                         ]
                      })
}
resource "sumologic_collector" "collector" {
  name        = "my-collector"
  description = "Just testing this"
}

Download example

FAQ

info

Click here for more information about Cloud-to-Cloud sources.