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 |
---|
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. StructureThe 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 credentialsIn 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: <short_unique_id>
name: <collector_name>
persistence:
type: filesystem
config:
directory_name: state
outputs:
devo_1:
type: devo_platform
config:
address: <devo_address>
port: 443
type: SSL
chain: <chain_filename>
cert: <cert_filename>
key: <key_filename>
inputs:
microsoft_graph:
id: <input_id>
enabled: <run_service>
request_per_second: <request_per_second>
credentials:
tenant_id: <tenant_id_value>
client_id: <client_id_value>
client_secret: <client_secret_value>
services:
secure_score_control_profile:
tag_version: v2
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
alerts:
tag_version: v2
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
secure_scores:
tag_version: v2
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
audit:
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
provisioning:
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
signIn:
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
signIn_nonInteractive:
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
signIn_servicePrincipal:
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_value>
signIn_managedIdentity:
request_period_in_seconds: <request_period_in_seconds_value>
start_time: <start_time_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. |
Replace the placeholders with your required values following the description table below: Parameter | Data type | Type | Value range / Format | Details |
---|
<debug_status>
| bool
| Mandatory
| false / true
| 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. |
---|
<collector_id>
| int
| Mandatory
| Minimum length: 1 Maximum length: 5 | Use this param to give a unique id to this collector. |
---|
<collector_name>
| str
| Mandatory
| Minimum length: 1 Maximum length: 10 | Use this param to give a valid name to this collector, like microsoft_graph . |
---|
<devo_address>
| str
| Mandatory
| collector-us.devo.io
collector-eu.devo.io
| 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. |
---|
<input_id>
| int
| Mandatory
| Minimum length: 1 Maximum length: 5 | Use this param 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. |
|
---|
<run_service>
| bool
| Mandatory
| false / true
| Use this param to enable or disable the given input logic when running the collector. If the value is true , the input will be run. If the value is false , it will be ignored. |
---|
<requests_per_second_value>
| int
| Optional
| Minimum value: 1 | Customize the maximum number of API requests per second. If not used, the default setting will be used: 60 requests/sec. Info |
---|
This parameter should be removed itf it is not used. |
|
---|
<tenant_id_value>
| str
| Mandatory
| UUID format | This is the Tenant’s ID you created in Azure AD. You can obtain it from the Overview page in your registered application. |
---|
<client_id_value>
| srt
| Mandatory
| UUID format | This is the Tenant’s ID you created in Azure AD. You can obtain it from the Overview page in your registered application. |
---|
<client_secret_value>
| srt
| Mandatory
| Any non-whitespace character | This is the Client’s secret you created in Azure AD. You can obtain it from the Certificates & secrets page in your registered application. |
---|
<request_period_in_seconds_value>
| int
| Optional
| Minimum value: 1 | The amount (in seconds) in which the service’s collection is scheduled. Info |
---|
This parameter should be removed itf it is not used. |
|
---|
<start_time_value>
| srt
| Optional
| Secure For the secure_scores service: YYYY-MM-DDTHH:mm:ssZ Rest For the rest of the services: YYYY-MM-DDTHH:mm:ss.SSSZ | This will allow you to start from a specific date in case you want to ingest historic events. If not set, it will start at the current time. Info |
---|
This parameter should be removed itf it is not used. |
|
---|
<tag_version>
| srt
| Optional
| Only accepts v1 (default) or v2 | The tag_version parameter is only implemented for the alerts , secure_scores and secure_score_control_profile(s) services. This parameter configured the destination tables according to their tagging: The detailed table destination depending on the tag_version 's value is available in the Devo categorization and destination section. Info |
---|
It is not necessary to include this parameter in the configuration to maintain backward compatibility. If there is no value, "v1" is assumed to maintain backward compatibility. With this, we can upgrade collectors whose version is previous to v1.1.3 without applying any changes. However, the recommendation is to set it to "v2" for new deployments. |
Info |
---|
This parameter should be removed itf it is not used. |
|
---|
Download the Docker imageThe 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: Use the following command to add the Docker image to the system: Code Block |
---|
gunzip -c <collector-ms-graph-collector-if-docker-image>-<1.2.0>.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: DockerExecute 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 ComposeThe 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. |
|