Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The table in this article provides a list of IoC types.

Data source description

Data source

Description

API endpoint

Collector service

Devo table

Pulses

Threat intelligence subscriptions

  • All pulses by users you are subscribed to

  • All pulses you are directly subscribed to

  • All pulses you have created yourself

  • All pulses from groups you are a member of

/api/v1/pulses/subscribed

alienvault_otx

threatintel.alienvault_otx.pulses.indicators

The data retrieved from AlientVault OTX is adapted to be stored in Devo. Each received pulse contains several hundred or thousands of indicators. Each indicator is stored individually in the Devo table threatintel.alienvault_otx.indicators, but combined with its pulse information.

...

<any_directory> └── devo-collectors/ └── devo-collector-alienvault-otx/ ├── certs/ │ ├── chain.crt

To enable the collector for a customer:

  1. In the Collector Server GUI, access the domain in which you want this instance to be created

  2. Click Add Collector and find the one you wish to add.

  3. In the Version field, select the latest value.

  4. In the Collector Name field, set the value you prefer (this name must be unique inside the same Collector Server domain).

  5. 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.

  6. In the Parameters section, establish the Collector Parameters as follows below:

Editing the JSON configuration

Rw ui tabs macro
Rw tab
titleCloud 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.

Rw tab
titleOn-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
Code Block
{
  "global_overrides": {
    "debug": false
  },
  "inputs": {
   "alienvault_otx": {
      "id": <short_unique_id>,
      "enabled": true,
      "requests_per_second": <requests_per_second>,
     ├── <your_domain>.key
 "override_base_url":  <override_base_url>,
      "credentials": {
   └── <your_domain>.crt       "api_key": <creds_api_key>
      },
└── config/     "services": {
        └── config.yaml

Devo credentials

In Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in devo-collector-alienvault-otx/certs. Learn more about security credentials in Devo here.

Image Removed

Editing the config.yaml file

Code Block
globals:
  debug: false
  id: not_used
  name: alienvault_collector
  persistence:
    type: filesystem "alienvault_otx": {
            "request_period_in_seconds": <period_in_seconds>,
         config:       directory_name: state

outputs:
  devo_1:"start_date": <start_date>
    type: devo_platform    }
config:      }
address: <devo_address>  }
    #address: collector-us.devo.io
      #address: collector-eu.devo.io
      port: 443
      type: SSL
      chain: <chain_filename>
      cert: <cert_filename>.crt
      key: <key_filename>.key
inputs:
  alienvault_otx:
    id: <shor_unique_id>
    enabled: true
    requests_per_second: <requests_per_second>
    override_base_url: <override_base_url>
    credentials:
      api_key: <creds_api_key>
    services:
      alienvault_otx:
        request_period_in_seconds: <period_in_seconds>
        start_date: <start_date>

Replace the placeholders with the required values:

Parameter

Data type

Type

Value range

Details

devo_address

str

Mandatory

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

chain_filename

str

Mandatory

Minimum length: 4
Maximum length: 20

Use this param 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 param to identify the file.cert downloaded from your Devo domain.

key_filename

str

Mandatory

Minimum length: 4
Maximum length: 20

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

shor_unique_id

int

Mandatory

Minimum length: 1
Maximum length: 5

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

requests_per_second

int

Optional

Minimum value: 1

Customize the maximum number of API requests per second. If not used, the default setting will be used: 100000 requests/sec

This parameter can be left blank, removed or commented.

override_base_url

str

Optional

By default, this RegEx:

^(https?:\/\/)?([\da-z\.-]+)\.([a-z\.])([\/\w \.-]*)*([a-z])$

URL of the AlientVault OTX API, provided by AlienVault. Usually, it is not necessary to set this parameter, the default value should be adequate.

This parameter can be left blank, removed, or commented.

creds_api_key

str

Mandatory

Any

API Key downloaded from AlienVault tenant.

period_in_seconds

int

Optional

Minimum length: 1

By default, this service will run every 300 seconds. This parameter allows you to customize this behavior.

This parameter can be left blank, removed or commented.

start_date

str

Optional

Format expected: YYYY-MM-DD HH:MM:SS

Parameter used by the collector as the starting UTC point when it first pulls data. An example value can be 2022-03-25 18:00:00

This parameter can be left blank, removed, or commented.

Updating this value will produce the loss of all persisted data.

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

collector-alienvault-otx-docker-image-1.1.0.tgz

8e2fe5117df3a65b62e1b8205c90f31c2cca5eeacdff3ff5c278d47da56660e0

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

Code Block
gunzip -c collector-alienvault-otx-docker-image-<version>.tgz | docker load
Info

Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace "<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/devo-collector-alienvault-otx/

Code Block
docker run \
--name collector-alienvault-otx\
--volume $PWD/certs:/devo-collector/certs \
--volume $PWD/config:/devo-collector/config \
--volume $PWD/state:/devo-collector/state \
--env CONFIG_FILE=config.yaml \
--rm -it devo.com/collectors/alientvault_otx_collector_if:<version>
Note

Replace <version> with a proper value.

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/devo-collector-alienvault-otx/ directory.

Code Block
version: '3'
services:
  collector-alienvault-otx:
    image: devo.com/collectors/alientvault_otx_collector_if:${IMAGE_VERSION:-latest}
    volumes:
      - ./certs:/devo-collector/certs
      - ./config:/devo-collector/config
      - ./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/devo-collector-alienvault-otx/ directory:

Code Block
IMAGE_VERSION=<version> docker-compose up -d
Note
Replace <version> with a proper value.
}
}
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

short_unique_id

int

Mandatory

Minimum length: 1
Maximum length: 5

Use this param to give an unique id to this input service.

requests_per_second

int

Optional

Minimum value: 1

Customize the maximum number of API requests per second. If not used, the default setting will be used: 100000 requests/sec

This parameter can be left blank, removed or commented.

override_base_url

str

Optional

By default, this RegEx:

^(https?:\/\/)?([\da-z\.-]+)\.([a-z\.])([\/\w \.-]*)*([a-z])$

URL of the AlientVault OTX API, provided by AlienVault. Usually it is not necessary to set this parameter, the default value should be adequate.

This parameter can be left blank, removed or commented.

creds_api_key

str

Mandatory

Any

API Key downloaded from AlienVault tenant.

period_in_seconds

int

Optional

Minimum length: 1

By default, this service will run every 300 seconds. This parameter allows you to customize this behavior.

This parameter can be left blank, removed or commented.

start_date

str

Optional

Format expected: YYYY-MM-DD HH:mm:ss

Parameter used by the collector as the starting UTC point when it first pulls data. An example value can be 2022-03-25 18:00:00

This parameter can be left blank, removed or commented.

Note

Updating this value will produce the lost of all persisted data.

AlientVault_40.pngImage Added
Rw tab
titleOn-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/
    └── devo-collector-alienvault-otx/
          ├── certs/
          │   ├── chain.crt
          │   ├── <your_domain>.key
          │   └── <your_domain>.crt
          └── config/
              └── config.yaml

Devo credentials

In Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in devo-collector-alienvault-otx/certs. Learn more about security credentials in Devo here.

Image Added

Editing the config.yaml file

Code Block
globals:
  debug: false
  id: not_used
  name: alienvault_collector
  persistence:
    type: filesystem
    config:
      directory_name: state

outputs:
  devo_1:
    type: devo_platform
    config:
      address: <devo_address>
      #address: collector-us.devo.io
      #address: collector-eu.devo.io
      port: 443
      type: SSL
      chain: <chain_filename>
      cert: <cert_filename>.crt
      key: <key_filename>.key
inputs:
  alienvault_otx:
    id: <shor_unique_id>
    enabled: true
    requests_per_second: <requests_per_second>
    override_base_url: <override_base_url>
    credentials:
      api_key: <creds_api_key>
    services:
      alienvault_otx:
        request_period_in_seconds: <period_in_seconds>
        start_date: <start_date>

Replace the placeholders with the required values:

Parameter

Data type

Type

Value range

Details

devo_address

str

Mandatory

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

chain_filename

str

Mandatory

Minimum length: 4
Maximum length: 20

Use this param 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 param to identify the file.cert downloaded from your Devo domain.

key_filename

str

Mandatory

Minimum length: 4
Maximum length: 20

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

shor_unique_id

int

Mandatory

Minimum length: 1
Maximum length: 5

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

requests_per_second

int

Optional

Minimum value: 1

Customize the maximum number of API requests per second. If not used, the default setting will be used: 100000 requests/sec

This parameter can be left blank, removed or commented.

override_base_url

str

Optional

By default, this RegEx:

^(https?:\/\/)?([\da-z\.-]+)\.([a-z\.])([\/\w \.-]*)*([a-z])$

URL of the AlientVault OTX API, provided by AlienVault. Usually, it is not necessary to set this parameter, the default value should be adequate.

This parameter can be left blank, removed, or commented.

creds_api_key

str

Mandatory

Any

API Key downloaded from AlienVault tenant.

period_in_seconds

int

Optional

Minimum length: 1

By default, this service will run every 300 seconds. This parameter allows you to customize this behavior.

This parameter can be left blank, removed or commented.

start_date

str

Optional

Format expected: YYYY-MM-DD HH:mm:ss

Parameter used by the collector as the starting UTC point when it first pulls data. An example value can be 2022-03-25 18:00:00

This parameter can be left blank, removed, or commented.

Updating this value will produce the loss of all persisted data.

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

collector-alienvault-otx-docker-image-1.1.0.tgz

8e2fe5117df3a65b62e1b8205c90f31c2cca5eeacdff3ff5c278d47da56660e0

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

Code Block
gunzip -c collector-alienvault-otx-docker-image-<version>.tgz | docker load
Info

Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace "<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/devo-collector-alienvault-otx/

Code Block
docker run \
--name collector-alienvault-otx\
--volume $PWD/certs:/devo-collector/certs \
--volume $PWD/config:/devo-collector/config \
--volume $PWD/state:/devo-collector/state \
--env CONFIG_FILE=config.yaml \
--rm -it devo.com/collectors/alientvault_otx_collector_if:<version>
Note

Replace <version> with a proper value.

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/devo-collector-alienvault-otx/ directory.

Code Block
version: '3'
services:
  collector-alienvault-otx:
    image: devo.com/collectors/alientvault_otx_collector_if:${IMAGE_VERSION:-latest}
    volumes:
      - ./certs:/devo-collector/certs
      - ./config:/devo-collector/config
      - ./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/devo-collector-alienvault-otx/ directory:

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

Replace <version> with a proper value.

Change log

Release

Released on

Release t

ype

Details

Recommendations

v1.1.0

Status
colourGreen
titleIMPROVEMENT

Improvements

  • Upgraded DCSDK from 1.1.4 to 1.9.1

    • Store lookup instances into DevoSender to avoid creation of new instances for the same lookup

    • Ensure service_config is a dict into templates

    • Ensure special characters are properly sent to the platform

    • Changed log level to some messages from info to debug

    • Changed some wrong log messages

    • Upgraded some internal dependencies

    • Changed queue passed to setup instance constructor

    • Added log traces for knowing the execution environment status (debug mode)

    • Fixes in the current puller template version

    • Improved log trace details when runtime exceptions happen

    • Refactored source code structure

    • New “templates” functionality

    • Functionality for detecting some system signals for starting the controlled stopping

    • Input objects sends again the internal messages to devo.collectors.out table

    • Upgraded DevoSDK to version 3.6.4 to fix a bug related to a connection loss with Devo

    • Refactored source code structure

    • Changed way of executing the controlled stopping

    • Minimized probabilities of suffering a DevoSDK bug related to “sender” to be null

    • Ability to validate collector setup and exit without pulling any data

    • Ability to store in the persistence the messages that couldn’t be sent after the collector stopped

    • Ability to send messages from the persistence when the collector starts and before the puller begins working

    • Ensure special characters are properly sent to the platform

    • Added a lock to enhance sender object

    • Added new class attrs to the setstate and getstate queue methods

    • Fix sending attribute value to the setstate and getstate queue methods

    • Added log traces when queues are full and have to wait

    • Added log traces of queues time waiting every minute in debug mode

    • Added method to calculate queue size in bytes

    • Block incoming events in queues when there are no space left

    • Send telemetry events to Devo platform

    • Upgraded internal Python dependency Redis to v4.5.4

    • Upgraded internal Python dependency DevoSDK to v5.1.3

    • Fixed obfuscation not working when messages are sent from templates

    • New method to figure out if a puller thread is stopping

    • Upgraded internal Python dependency DevoSDK to v5.0.6

    • Improved logging on messages/bytes sent to Devo platform

    • Fixed wrong bytes size calculation for queues

    • New functionality to count bytes sent to Devo Platform (shown in console log)

    • Upgraded internal Python dependency DevoSDK to v5.0.4

    • Fixed bug in persistence management process, related to persistence reset

    • Aligned source code typing to be aligned with Python 3.9.x

    • Inject environment property from user config

    • Obfuscation service can be now configured from user config and module definitonStore lookup instances into DevoSender to avoid creation of new instances for the same lookup

    • Ensure service_config is a dict into templates

    • Ensure special characters are properly sent to the platform

    • Changed log level to some messages from info to debug

    • Changed some wrong log messages

    • Upgraded some internal dependencies

    • Changed queue passed to setup instance constructor

    • Added log traces for knowing the execution environment status (debug mode)

    • Fixes in the current puller template version

    • Improved log trace details when runtime exceptions happen

    • Refactored source code structure

    • New “templates” functionality

    • Functionality for detecting some system signals for starting the controlled stopping

    • Input objects sends again the internal messages to devo.collectors.out table

    • Upgraded DevoSDK to version 3.6.4 to fix a bug related to a connection loss with Devo

    • Refactored source code structure

    • Changed way of executing the controlled stopping

    • Minimized probabilities of suffering a DevoSDK bug related to “sender” to be null

    • Ability to validate collector setup and exit without pulling any data

    • Ability to store in the persistence the messages that couldn’t be sent after the collector stopped

    • Ability to send messages from the persistence when the collector starts and before the puller begins working

    • Ensure special characters are properly sent to the platform

    • Added a lock to enhance sender object

    • Added new class attrs to the setstate and getstate queue methods

    • Fix sending attribute value to the setstate and getstate queue methods

    • Added log traces when queues are full and have to wait

    • Added log traces of queues time waiting every minute in debug mode

    • Added method to calculate queue size in bytes

    • Block incoming events in queues when there are no space left

    • Send telemetry events to Devo platform

    • Upgraded internal Python dependency Redis to v4.5.4

    • Upgraded internal Python dependency DevoSDK to v5.1.3

    • Fixed obfuscation not working when messages are sent from templates

    • New method to figure out if a puller thread is stopping

    • Upgraded internal Python dependency DevoSDK to v5.0.6

    • Improved logging on messages/bytes sent to Devo platform

    • Fixed wrong bytes size calculation for queues

    • New functionality to count bytes sent to Devo Platform (shown in console log)

    • Upgraded internal Python dependency DevoSDK to v5.0.4

    • Fixed bug in persistence management process, related to persistence reset

    • Aligned source code typing to be aligned with Python 3.9.x

    • Inject environment property from user config

    • Obfuscation service can be now configured from user config and module definiton

Recommended version