Infoblox BloxOne Threat Defense Event Collector
BloxOne Threat Defense is a hybrid cybersecurity solution that leverages DNS as the first line of defense to detect and block cyber threats.
Data Enrichment & Threat Intelligence · Infoblox Threat Defense with DDI
Details
| ID | Infoblox BloxOne Threat Defense Event Collector |
|---|---|
| Provider | Infoblox |
| Category | Data Enrichment & Threat Intelligence |
| From Version | 6.10.0 |
| Docker Image | demisto/python3:3.12.13.10116658 |
| Supported Modules | Agentix XSIAM |
README
BloxOne Threat Defense is a hybrid cybersecurity solution that leverages DNS as the first line of defense to detect and block cyber threats.
Configure Infoblox BloxOne Threat Defense Event Collector in Cortex
| Parameter | Description | Required |
|---|---|---|
| Service API Key | True | |
| First fetch time interval | False | |
| Max events per fetch | The maximum amount of events to retrieve for each event type (up to 10000 events). For more information about event types see the help section. | False |
| Trust any certificate (not secure) | False | |
| Use system proxy settings | False |
Commands
You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.
bloxone-td-event-collector-get-events
Gets events. This command is for debugging purposes.
Base Command
bloxone-td-event-collector-get-events
Input
| Argument Name | Description | Required |
|---|---|---|
| should_push_events | Set this argument to True in order to create events, otherwise the command will only display them. Possible values are: True, False. Default is False. | Required |
| from | Timestamp indicating when to start fetching events. | Required |
| to | Timestamp indicating when to stop fetching events. | Required |
| limit | Maximum number of events to fetch. Default is 1000. | Required |
| offset | offset of the events. | Required |
Context Output
| Path | Type | Description |
|---|---|---|
| TestGetEvents | Unknown | The event data. |
Configuration parameters
credentials— (required)first_fetch— First fetch time intervalmax_fetch— Max events per fetchinsecure— Trust any certificate (not secure)proxy— Use system proxy settings
Commands (1)
-
bloxone-td-event-collector-get-eventsGets events. This command is for debugging purposes.
## Infoblox BloxOne Threat Defense Event Collector Help ### Creating Service API Key You can create multiple service API keys that are associated with respective service API keys for specific purposes. You must have the required permission to create service API keys. For information, see [Configuring Service API Key](https://docs.infoblox.com/space/BloxOneCloud/35430173). To create a service API key, complete the following: 1. From the SSO portal, click **User Access** from the left navigation panel and then click the **Service API Keys** tab. 2. On the Service API Keys tab, click **Create**. 3. In the Create Service API Keys dialog, complete the following: - **Name**: Enter the name of the user API key. Use a name that can identify the purpose of the key. - **Service User**: Enter the name of the service users or choose one from the drop-down list. You can associate up to 10 service API keys per service user. - **Expires at**: Click the calendar icon to select a date and time when the service API key should expire. This date determines the duration of key validity. 4. Click **Save & Close** to save the configuration. The new service API key is generated. 5. In the API Access Key Generated dialog, click **Copy** to copy the key and save it in a place where you can locate the key in the future.