Intel471 threat intel c2 c

cid-redirects.json

@@ -1613,6 +1613,7 @@
   "/cid/10196": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/zero-networks-segment-source",
   "/cid/10122": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/webex-source",
   "/cid/10125": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/druva-cyber-resilience-source",
+  "/cid/10127": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/intel-471-threat-intel-source",
   "/cid/10135": "/docs/manage/manage-subscription/manage-org-settings",
   "/cid/10136": "/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-logs-source",
   "/cid/10234": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/trellix-mvisio-epo-source",

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/intel-471-threat-intel-source.md

@@ -0,0 +1,99 @@
+---
+id: intel-471-threat-intel-source
+title: Intel 471 Threat Intel Source
+sidebar_label: Intel 471 Threat Intel
+tags:
+  - cloud-to-cloud
+  - intel-471-threat-intel
+description: This integration collects threat indicators from the Intel 471 API and sends them to Sumo Logic as normalized threat indicators for analysis.
+---
+import CodeBlock from '@theme/CodeBlock';
+import ExampleJSON from '/files/c2c/intel-471-threat-intel/example.json';
+import MyComponentSource from '!!raw-loader!/files/c2c/intel-471-threat-intel/example.json';
+import TerraformExample from '!!raw-loader!/files/c2c/intel-471-threat-intel/example.tf';
+import ForwardToSiem from '/docs/reuse/forward-to-siem.md';
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/send-data/intel471-threat-intel.png')} alt="intel471-threat-intel.png" width="50" />
+
+Intel 471 helps organizations protect against cyber threats by monitoring underground marketplaces and forums used by cybercriminals. They specialize in cyber threat intelligence, focusing on malware, malicious actors, their tactics, techniques, and procedures (TTPs).
+
+The Intel 471 source collects threat indicators from the [Intel 471 API](https://login.intel471.com/u/login/identifier?state=hKFo2SBJbDlzQnBDWGo0MU5wZEJndGh0YV9Eby0yQmRHb0dueqFur3VuaXZlcnNhbC1sb2dpbqN0aWTZIDY3NW1vbmdfdFktTTVDY01kY1ZncndOSU9ZZllxSXBao2NpZNkgR1dKRFJFclBoS3BRZGlWcmxNN2F5c0V6TDZXeEw5azI#tag/Indicators/paths/~1indicators~1stream/get) and sends them to Sumo Logic as normalized threat indicators for analysis.
+
+## Data collected
+
+| Polling Interval | Data |
+| :--- | :--- |
+| 1 hr | [Indicators](https://login.intel471.com/u/login/identifier?state=hKFo2SBnRnh4QWZIandtd2J2S2pOeGdWS1MwWWZ1bFpubzctR6Fur3VuaXZlcnNhbC1sb2dpbqN0aWTZIEZXOFR0UGtYNWJLV3lWWXY4ME1tRlVrWk0yd0tneFBFo2NpZNkgR1dKRFJFclBoS3BRZGlWcmxNN2F5c0V6TDZXeEw5azI#tag/Indicators) |
+
+## Setup
+
+### Vendor configuration
+
+:::info
+The Intel 471 API documentation is not public and can only be accessed by partners or customers.
+:::
+
+The Intel 471 Threat Intel source requires you to authenticate the **Username** and **API Key** found in the API section in the [portal](https://login.intel471.com/u/login/identifier?state=hKFo2SB4ckUwei1aN2JUaFhkTG5FQkstbF9sZldMTlFzdnZXMaFur3VuaXZlcnNhbC1sb2dpbqN0aWTZIG5HU3o1RVg3RTY2RWloTGFySjNTcWowLWVXRVJzYUxIo2NpZNkgR1dKRFJFclBoS3BRZGlWcmxNN2F5c0V6TDZXeEw5azI#section/Authentication).
+
+### Source configuration
+
+When you create an Intel 471 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](/docs/send-data/hosted-collectors/configure-hosted-collector).
+
+To configure an Intel 471 Threat Intel source:
+
+1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-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**.  
+1. On the Collectors page, click **Add Source** next to a Hosted Collector.
+1. Search for and select **Intel 471 Threat Intel**.
+1. Enter a **Name** to display for the Source in the Sumo web application. The description is optional.
+1. (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`.
+1. (Optional) **Fields.** Click the **+Add Field** link to define the fields you want to associate, each field needs a name (key) and value.
+   * ![green check circle.png](/img/reuse/green-check-circle.png) A green circle with a check mark is shown when the field exists in the Fields table schema.
+   * ![orange exclamation point.png](/img/reuse/orange-exclamation-point.png) 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. 
+1. **Username**. Enter the login ID or email address of the user.
+1. **API Key**. Enter the API key of the user account collected from the Intel 471 Threat Intel platform.
+1. **Sumo Logic Threat Intel Source ID**. Enter the Sumo Logic namespace where the indicators will be stored.
+1. **Polling Interval**. The polling interval is set for 5 minutes by default. You can adjust it based on your needs. This sets how often the source checks for new data.
+1. **Processing Rules for Logs**. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in [Create a Processing Rule](/docs/send-data/collection/processing-rules/create-processing-rule).
+1. 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](/docs/send-data/use-json-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](#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](/docs/search/get-started-with-search/search-basics/built-in-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](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_sourceCategory`. See [best practices](/docs/send-data/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. | `"[email protected]"` |
+| 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
+
+<CodeBlock language="json">{MyComponentSource}</CodeBlock>
+
+<a href="/files/c2c/intel-471-threat-intel/example.json" target="_blank">Download example</a>
+
+### Terraform example
+
+<CodeBlock language="json">{TerraformExample}</CodeBlock>
+
+<a href="/files/c2c/intel-471-threat-intel/example.tf" target="_blank">Download example</a>
+
+## FAQ
+
+:::info
+Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources.
+:::

static/files/c2c/intel-471-threat-intel/example.json

@@ -0,0 +1,16 @@
+{
+	"api.version": "v1",
+	"source": {
+		"config": {
+			"name": "Intel471",
+			"username": "[email protected]",
+			"apiKey": "xxxx94429cexxxxxxc2e4ecc2e19xx190594935xxxxxx2316xxx",
+			"userSourceId": "user_source_id",
+			"pollingIntervalHour": "1h"
+		},
+		"schemaRef": {
+			"type": "Intel47 Threat Intel"
+		},
+		"sourceType": "Universal"
+	}
+}

static/files/c2c/intel-471-threat-intel/example.tf

@@ -0,0 +1,17 @@
+resource "sumologic_cloud_to_cloud_source" "intel-471-threat-intel-source" {
+  collector_id = sumologic_collector.collector.id
+  schema_ref = {
+    type = "Intel 471 Threat Intel"
+  }
+  config = jsonencode({
+                    "name": "Intel471",
+			        "username": "[email protected]",
+			        "apiKey": "xxxx94429cexxxxxxc2e4ecc2e19xx190594935xxxxxx2316xxx",
+			        "userSourceId": "user_source_id",
+			        "pollingIntervalHour": "1h"
+  })
+}
+resource "sumologic_collector" "collector" {
+  name        = "my-collector"
+  description = "Just testing this"
+}