Intel471 Threat Intel Source

Beta

Intel471 is a cybersecurity firm specializing in providing cyber threat intelligence services. Their focus is primarily on delivering information about threats originating from the criminal underground, including malware, malicious actors, and their tactics, techniques, and procedures (TTPs). Intel471 provides these insights to help organizations protect themselves against cyber threats. Their intelligence-gathering efforts often involve monitoring and analyzing underground marketplaces, forums, and other communication channels used by cyber criminals.

The Intel471 source collects threat indicators using the Intel471 Stream API and sends them to Sumo Logic as normalized threat indicators for analysis.

Data collected

Polling Interval	Data
1 hour	Indicators

Setup

Vendor configuration

info

The Intel471 documentation is not public and can only be accessed by partners or customers.

The Intel471 Threat Intel source requires you to provide the Username and API Key found in the API section in the Intel471 portal.

Source configuration

When you create an Intel471 Threat Intel 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 an Intel471 Threat Intel 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 Collectors page, click Add Source next to a Hosted Collector.
3. Search for and select Intel471 Threat Intel.
4. Enter a Name to display for the Source in the Sumo web application. 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 Field link 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 that does not exist in the Fields schema it is ignored, known as dropped. 
7. Username. Enter your login ID or email address.
8. API Key. Enter the API key of the user account collected from the Intel471 Threat Intel platform.
9. Sumo Logic Threat Intel Source ID. Enter the Sumo Logic namespace where the indicators will be stored.
10. Polling Interval. The polling interval is set for one hour by default. You can adjust it based on your needs. This sets how often the source checks for new data.
11. Processing Rules for Logs. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
12. 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”: “Intel471 Threat Intel”}	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"}
username	String	Yes	null	Login ID or email address of the user.	"jimmy@organization.com"
apiKey	String	Yes	null	API Key of the account.
userSourceId	String	Yes	null	The Sumo Logic namespace in which the indicators will be stored.
pollingIntervalHour	integer	Yes	1 hour	Time interval (in hours) after which the source will check for new data.

JSON example

{
	"api.version": "v1",
	"source": {
		"config": {
			"name": "Intel471",
			"username": "pal@sumologic.com",
			"apiKey": "xxxx94429cexxxxxxc2e4ecc2e19xx190594935xxxxxx2316xxx",
			"userSourceId": "user_source_id",
			"pollingIntervalHour": "1h"
		},
		"schemaRef": {
			"type": "intel471 Threat Intel"
		},
		"sourceType": "Universal"
	}
}

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "intel471-threat-intel-source" {
  collector_id = sumologic_collector.collector.id
  schema_ref = {
    type = "Intel471 Threat Intel"
  }
  config = jsonencode({
                    "name": "Intel471",
			        "username": "pal@sumologic.com",
			        "apiKey": "xxxx94429cexxxxxxc2e4ecc2e19xx190594935xxxxxx2316xxx",
			        "userSourceId": "user_source_id",
			        "pollingIntervalHour": "1h"
  })
}
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.