Page Comparison

...

Rw ui tabs macro

Rw tab

title	On-premise collector

This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running.

Structure

The following directory structure should be created for being used when running the collector:

Code Block

<any_directory>
└── devo-collectors/
    └── <product_name>/
        ├── certs/
        │   ├── chain.crt
        │   ├── <your_domain>.key
        │   └── <your_domain>.crt
        ├── state/
        └── config/ 
            └── config.yaml

Note
Replace `<product_name>` with the proper value.

Devo credentials

In Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in <product_name>/certs/. Learn more about security credentials in Devo here.

Note
Replace `<product_name>` with the proper value.

Editing the config.yaml file

Code Block

globals:
  debug: <debug_status>
  id: not_used
  name: defender_for_iot
  persistence:
    type: filesystem
    config:
      directory_name: state
outputs:
  devo_us_1:
    type: devo_platform
    config:
      address: <devo_address>
      port: 443
      type: SSL
      chain: <chain_filename>
      cert: <cert_filename>
      key: <key_filename>

inputs:
  defender_for_iot:
    id: <input_id_value>
    enabled: true
    environment: <environment_value>
    credentials:
      client_id: <client_id_value>
      client_secret: <client_secret_value>
      tenant_id: <tenant_id_value>
    services:
      iot_security_alerts:
        override_tag: <override_tag_value>
        start_time_in_utc: <start_time_in_utc_value>
        obfuscation_data: [<obfuscation_data_values>]
globals:
  debug: false
  id: not_used
  name: threatquotient_collector
  persistence:
    type: filesystem
    config:
      directory_name: state

outputs:
  devo_1:
    type: devo_platform
    config:
      address: <your-ingestion-endpoint>
      port: 443
      type: SSL
      chain: chain.crt
      cert: <your_domain>.crt
      key: <your_domain>.key
inputs:
  threatquotient_data_puller:
    id: <short_unique_id>
    debug: <enable_debug_logs>
    enabled: <input_status>
    requests_per_second: <requests_per_second>
    credentials:
      username: <threatq_username>
      password: <threatq_password>
    services:
      events:
        request_period_in_seconds: <request_period_in_seconds>
        reset_persistence_auth: <reset_persistence_auth>
        api_base_url: <api_base_url>
        verify_host_ssl_cert: <verify_host_ssl_cert>
        historical_poll_datetime: <historical_poll_datetime>
        event_fetch_limit_in_items: <event_fetch_limit_in_items>

Info
All defined service entities will be executed by the collector. If you do not want to run any of them, just remove the entity from the `services` object.

Replace the placeholders with your required values following the description table below:

Parameter

Data type

Type

Value range / Format

Details

debug_status

bool

Mandatory

true / false

If the value is true, the debug logging traces will be enabled when running the collector. If the value is false, only the info, warning, and error logging levels will be printed.

devo_address

str

Mandatory

collector-us.devo.io

collector-eu.devo.io

Use this parameter to identify the Devo Cloud where the events will be sent.

chain_filename

str

Mandatory

minimum length: 4

maximum length: 20

Use this parameter to identify the chain.cert file downloaded from your Devo domain. Usually this file's name is: chain.crt.

cert_filename

str

Mandatory

minimum length: 4

maximum length: 20

Use this parameter to identify the file.cert downloaded from your Devo domain.

key_filename

str

Mandatory

minimum length: 4

maximum length: 20

Use this parameter to identify the file.key downloaded from your Devo domain.

input_id_value

str

Mandatory

minimum Minimum length: 5

maximum Maximum length: 15-

Use this parameter to give a unique ID to this input service.

Note
This parameter is used to build the persistence address. Do not use the same value for multiple collectors. It could cause a collision.

environment_value

str

Optional

Minimum length: 1

This is an optional control parameter that is injected into the events and allows to differentiate the environment. For example: dev and prod.

Info
This parameter should be removed if it is not used.

client_id_value

str

mandatory

minimum length: 1

The Azure application client ID.

client_secret_value

str

mandatory

minimum length: 1

The Azure application client secret.

tenant_id_value

str

mandatory

minimum length: 1

The Azure tenant ID.

override_tag_value

str

optional

Devo tag-friendly string (no special characters, spaces, etc.) For more information see Devo Tags.

An optional tag that allows users to override the service default tags.

Info
This parameter should be removed if it is not used.

start_time_in_utc_value

str

optional

UTC datetime string having datetime string format %-Y-%m-%d %H-%M-%S (e.g., “2000-01-01 00:00:01”)

This configuration allows you to set a custom date as the beginning of the period to download. This allows downloading historical data (one month back for example) before downloading new events.

Info
This parameter should be removed if it is not used.

obfuscation_data_values

array<object

optional

The objects in the array look like this:

obfuscation_data:

name:

credentials

"*"

value: "**********"

Each object represents the necessary configuration to obfuscate messages before these are sent to Devo.

Info
This parameter should be removed if it is not used.

Download the Docker image

The collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table:

Collector Docker image	SHA-256 hash
docker-image.tgz	`-`

Use the following command to add the Docker image to the system:

Code Block
gunzip -c <image_file>-<version>.tgz \| docker load

Note
Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace `<image_file>` and `<version>` with a proper value.

The Docker image can be deployed on the following services:

Docker

Execute the following command on the root directory <any_directory>/devo-collectors/<product_name>/

Code Block

docker run 
--name collector-<product_name> 
--volume $PWD/certs:/devo-collector/certs 
--volume $PWD/config:/devo-collector/config 
--volume $PWD/state:/devo-collector/state 
--env CONFIG_FILE=config.yaml 
--rm 
--interactive 
--tty 
<image_name>:<version>

Note
Replace `<product_name>`, `<image_name>` and `<version>` with the proper values.

Docker Compose

The following Docker Compose file can be used to execute the Docker container. It must be created in the <any_directory>/devo-collectors/<product_name>/ directory.

Code Block

version: '3'
services:
  collector-<product_name>:
    image: <image_name>:${IMAGE_VERSION:-latest}
    container_name: collector-<product_name>
    volumes:
      - ./certs:/devo-collector/certs
      - ./config:/devo-collector/config
      - ./credentials:/devo-collector/credentials
      - ./state:/devo-collector/state
    environment:
      - CONFIG_FILE=${CONFIG_FILE:-config.yaml}

To run the container using docker-compose, execute the following command from the <any_directory>/devo-collectors/<product_name>/ directory:

Code Block
IMAGE_VERSION=<version> docker-compose up -d

Note
Replace `<product_name>`, `<image_name>` and `<version>` with the proper values.

Rw tab

title	Cloud collector

We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, get in touch with us and we will guide you through the configuration.

To enable the collector for a customer:

In the Collector Server GUI, access the domain in which you want this instance to be created
Click Add Collector and find the one you wish to add.
In the Version field, select the latest value.
In the Collector Name field, set the value you prefer (this name must be unique inside the same Collector Server domain).
In the sending method select Direct Send. Direct Send configuration is optional for collectors that create Table events, but mandatory for those that create Lookups.
In the Parameters section, establish the Collector Parameters as follows below:

Editing the JSON configuration

Code Block

{
 "global_overrides": {
   "debug": false
 },
 "inputs": {
   "defender_for_iot": {
     "id": "<input_id_value>",
     "enabled": true,
     "credentials": {
       "client_id": "<client_id_value>",
       "client_secret": "<client_secret_value>",
       "tenant_id": "<tenant_id_value>"
     },
     "services": {
       "iot_security_alerts": {
         "override_tag": "<override_tag_value>",
         "start_time_in_utc": "<start_time_in_utc_value>",
         "obfuscation_data": ["<obfuscation_data_values>"]
       }
     }
   }
 }
}

Info
All defined service entities will be executed by the collector. If you do not want to run any of them, just remove the entity from the `services` object.

Please replace the placeholders with real world values following the description table below:

Parameter	Data type	Type	Value Range / Format	Details
`debug`	bool	mandatory	true / false	If the value is `true`, the debug logging traces will be enabled when running the collector. If the value is `false`, only the info, warning, and error logging levels will be printed.
`input_id_value`	int	mandatory	minimum length: 5 maximum length: 15	Use this parameter to give a unique ID to this input service. This parameter is used to build the persistence address. Do not use the same value for multiple collectors. It could cause a collision.
`environment_value`	str	optional	minimum length: 1	This is an optional control parameter that is injected into the events and allows to differentiate the environment. For example: dev and prod. This parameter should be removed if it is not used.
`client_id_value`	str	mandatory	minimum length: 1	The Azure application client ID.
`client_secret_value`	str	mandatory	minimum length: 1	The Azure application client secret.
`tenant_id_value`	string	mandatory	minimum length: 1	The Azure tenant ID.
`override_tag_value`	str	optional	Devo tag-friendly string (no special characters, spaces, etc.) For more information see Devo Tags.	An optional tag that allows users to override the service default tags. This parameter can be removed or commented.
`start_time_in_utc_value`	str	optional	UTC datetime string having datetime string format `%-Y-%m-%d %H-%M-%S` (e.g., “`2000-01-01 00:00:01`”)	This configuration allows you to set a custom date as the beginning of the period to download. This allows downloading historical data (one month back for example) before downloading new events. This parameter should be removed if it is not used.
`obfuscation_data_values`	array<object>	optional	The objects in the array look like this: `obfuscation_data:` name: credentials "" `value: "*********"`	Each object represents the necessary configuration to obfuscate messages before these are sent to Devo. This parameter can be removed or commented.

Image Added

Collector services detail

...

Versions Compared

Old Version 1

New Version Current

Key

Structure

Devo credentials

Editing the config.yaml file

Download the Docker image

Docker

Docker Compose

Editing the JSON configuration

Collector services detail