Versions Compared

Key

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

...

SentinelOne Deep Visibility extends the SentinelOne Endpoint Protection Platform (EPP) to provide full visibility into endpoint data. Its patented kernel-based monitoring allows a near real-time search across endpoints for all indicators of compromise (IOC) to empower security teams to augment real-time threat detection capabilities with a powerful tool that enables threat hunting.

Devo collector features

Feature

Details

Allow parallel downloading (multipod)

  • allowed

Running environments

  • collector server

  • on-premise

Populated Devo events

  • table

Flattening preprocessing

  • no

Data sources

Data source

Description

API endpoint

Collector service name

Devo table

Available from release

Cloud Funnel

Deep Visibility data stored in AWS via Cloud Funnel

AWS S3 and SQS (via boto3 libraries)

cloud_funnel

edr.sentinelone.dv.{event_category}

v1.0.0

For more information on how the events are parsed, visit our page.

Flattening preprocessing

Data source

Collector service

Optional

Flattening details

Source

Service

  • no

Flattening steps

Accepted authentication methods

Authentication method

AWS Access Key

AWS Secret Access Key

AWS access key/secret

Status
colourGreen
titleREQUIRED

Status
colourGreen
titleREQUIRED

Minimum configuration required for basic pulling

...

Info

This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details.

Setting

Details

aws_access_key_id

Credentials aws_access_key_id

aws_secret_access_key

Credentials aws_secret_access_key

region

AWS region

queue_name

AWS SQS queue_name

Info

See the Accepted authentication methods section to verify what settings are required based on the desired authentication method.

...

Rw ui tabs macro
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/
    └── <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: false
  id: not_used
  name: sentinelone_cloud_funnel
  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:
  cloud_funnel:
    id: <short_unique_id>
    enabled: <input_status>
    credentials:
      aws_access_key_id: <aws_access_key_id_value>
      aws_secret_access_key: <aws_secret_access_key_value>
    services:
      events:
        region: <region_value>
        queue_name: <queue_name_value>
        override_tag: <override_tag_value>
        request_period_in_seconds: <request_period_in_seconds_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

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.

short_unique_id

int

Mandatory

Minimum length: 5

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.

input_status

bool

Mandatory

true / false

If the value is true, the input definition will be executed. If the value is false, the service will be ignored.

aws_access_key_id_value

str

Mandatory

Minimum length: 1

The AWS access key ID provided by SentinelOne

aws_secret_access_key_value

str

Mandatory

Minimum length: 1

The AWS secret access key provided by SentinelOne

region_value

str

Mandatory

Minimum length: 1

The AWS region provided by SentinelOne

queue_name_value

str

Mandatory

Minimum length: 1

The AWS SQS queue name provided by Sentinel One

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 can be removed or commented.

request_period_in_seconds_value

int

Optional

Minimum length: 1

Period in seconds used between each data pulling. This value will overwrite the default value (60 seconds).

Info

This parameter can be removed or commented.

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-sentinelone_deep_visibility_with_cloud_funnel_if-docker-image-1.0.0

f549d27173ae5b398d9e6af34df6ba28448f356716159750fa0b8af8afb47152

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

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

Code Block
{
  "global_overrides": {
    "debug": false
  },
  "inputs": {
    "cloud_funnel": {
     "id": "<short_unique_id>",
      "enabled": <input_status>,
      "credentials": {
        "aws_access_key_id": "<aws_access_key_id_value>",
        "aws_secret_access_key": "<aws_secret_access_key_value>"
      },
      "services": {
        "events": {
          "region": "<region_value>",
          "queue_name": "<queue_name_value>",
          "override_tag": "<override_tag_value>",
          “request_period_in_seconds”: <request_period_in_seconds_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: 5

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.

input_status

bool

Mandatory

false / true

If the value is true, the input definition will be executed. If the value is false, the service will be ignored.

aws_access_key_id_value

str

Mandatory

Minimum length: 1

The AWS access key ID provided by SentinelOne.

aws_secret_access_key_value

str

Mandatory

Minimum length: 1

The AWS secret access key provided by SentinelOne.

region_value

str

Mandatory

Minimum length: 1

The AWS region provided by SentinelOne.

queue_name_value

str

Mandatory

Minimum length: 1

The AWS SQS queue name provided by SentinelOne.

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 can be removed or commented.

request_period_in_seconds_value

int

Optional

Minimum length: 1

Period in seconds used between each data pulling. This value will overwrite the default value (60 seconds).

Info

This parameter can be removed or commented.

Collector services detail

...

Expand
titleCheck memory usage

To check the memory usage of this collector, look for the following log records in the collector which are displayed every 5 minutes by default, always after running the memory-free process.

  • The used memory is displayed by running processes and the sum of both values will give the total used memory for the collector.

  • The global pressure of the available memory is displayed in the global value.

  • All metrics (Global, RSS, VMS) include the value before freeing and after previous -> after freeing memory

Code Block
INFO InputProcess::MainThread -> [GC] global: 20.4% -> 20.4%, process: RSS(34.50MiB -> 34.08MiB), VMS(410.52MiB -> 410.02MiB)
INFO OutputProcess::MainThread -> [GC] global: 20.4% -> 20.4%, process: RSS(28.41MiB -> 28.41MiB), VMS(705.28MiB -> 705.28MiB)
Info

Differences between RSS and VMS memory usage:

  • RSS is the Resident Set Size, which is the actual physical memory the process is using

  • VMS is the Virtual Memory Size which is the virtual memory that process is using

Change log for v1.x.x

Release

Released on

Release type

Details

Recommendations

v1.0.0

Status
colourPurple
titleNEW FEATURE

New features:

  • Events service: Deep Visibility events stored in AWS via Cloud Funnel. These events are of different types, the collector autocategorizes them and sends them to different tables in Devo.

Recommended version