Cyble Vision collector

[ 1 Overview ] [ 2 Devo collector features ] [ 3 Data sources ] [ 4 Minimum configuration required for basic pulling ] [ 5 Accepted authentication methods ] [ 6 Run the collector ] [ 7 Collector services detail ] [ 8 Change log ]

Overview

Cyble Vision is a comprehensive cybersecurity platform designed to keep businesses a step ahead of cyber threats. Cyble Vision swiftly identifies incidents and provides advanced intelligence for rapid response, helping to mitigate attack damages. The Cyble Vision collector allows users to fetch and analyze incidents and fetch IOCs for further triage in the Devo platform.

Devo collector features

Feature	Details

Feature	Details
Allow parallel downloading (`multipod`)	`not allowed`
Running environments	`collector server` `on-premise`
Populated Devo events	`table` `lookups`
Flattening preprocessing	`no`

Data sources

Data source	Description	API endpoint	Collector service name	Devo table / lookup	Available from release

Data source	Description	API endpoint	Collector service name	Devo table / lookup	Available from release
Alerts	Fetch alerts / incidents	`/apollo/api/v1/y/alerts`	`alerts`	`threatintel.cyble.vision.alert`	`v1.0.0`
IOCs	Fetch IOCs and store in a Devo lookup	`/engine/api/v2/y/iocs`	`iocs`	Lookup starting with `cyble_vision_iocs`	`v1.0.0`

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

Minimum configuration required for basic pulling

Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.

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

Setting	Details
`api_key`	Token for authentication

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

Accepted authentication methods

The user must specify an Access Key ID and Secret ID for the account/RAM to authenticate with the ActionTrail API or Log Service API.

Setting	Details

Setting	Details
bearer token	Required

Run the collector

Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).

Collector services detail

This section is intended to explain how to proceed with specific actions for services.

Devo categorization and destination

All events of this service are ingested into the table threatintel.cyble.vision.alert

Verify data collection

Once the collector has been launched, it is important to check if the ingestion is performed in a proper way. To do so, go to the collector’s logs console.

This service has the following components:

Component	Description

Component	Description
Setup	The setup module is in charge of authenticating the service and managing the token expiration when needed.
Puller	The setup module is in charge of pulling the data in an organized way and delivering the events via SDK.

Setup output

A successful run has the following output messages for the setup module:

2025-03-12T16:56:43.352    INFO InputProcess::MainThread -> AlertsPuller(cyble_vision#34215,alerts#predefined) - Starting thread
2025-03-12T16:56:43.353    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> Waiting until setup will be executed
2025-03-12T16:56:43.356    INFO InputProcess::MainThread -> InputMetricsThread -> Started thread for updating metrics values (update_period=10.0)
2025-03-12T16:56:44.038    INFO InputProcess::VisionPullerSetup(cyble_vision#34215,alerts#predefined) -> Authentication successful.
2025-03-12T16:56:44.039    INFO InputProcess::VisionPullerSetup(cyble_vision#34215,alerts#predefined) -> Check for <AlertsPuller> module has been successfully executed

Puller output

A successful initial run has the following output messages for the puller module:

Note that the PrePull action is executed only one time before the first run of the Pull action.

2025-03-12T17:01:44.407    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> Pull Started
2025-03-12T17:01:44.409    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> Fetching all alerts subject to the following parameters: {'orderBy': [{'created_at': 'asc'}], 'skip': 0, 'take': 1000, 'withDataMessage': False, 'where': {'created_at': {'gte': '2025-03-12T11:26:34Z', 'lte': '2025-03-12T11:31:44Z'}}}
2025-03-12T17:01:45.147    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> 34 record(s) returned for last batch which is less than limit of 1000. No new records remaining. Finishing pull.
2025-03-12T17:01:45.152    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1741779104406):Number of requests made: 1; Number of events received: 34; Number of duplicated events filtered out: 1; Number of events generated and sent: 33; Average of events per second: 44.347.
2025-03-12T17:01:45.153    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> Statistics for this pull cycle (@devo_pulling_id=1741779104406):Number of requests made: 1; Number of events received: 34; Number of duplicated events filtered out: 1; Number of events generated and sent: 33; Average of events per second: 44.285.
2025-03-12T17:01:45.154    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> The data is up to date!
2025-03-12T17:01:45.155    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> Data collection completed. Elapsed time: 0.749 seconds. Waiting for 299.251 second(s) until the next one

After a successful collector’s execution (that is, no error logs found), you will see the following log message:

2025-03-12T17:01:45.153    INFO InputProcess::AlertsPuller(cyble_vision#34215,alerts#predefined) -> Statistics for this pull cycle (@devo_pulling_id=1741779104406):Number of requests made: 1; Number of events received: 34; Number of duplicated events filtered out: 1; Number of events generated and sent: 33; Average of events per second: 44.285.

This collector uses persistent storage to download events in an orderly fashion and avoid duplicates. In case you want to re-ingest historical data or recreate the persistence, you can restart the persistence of this collector by following these steps:

Edit the configuration file.
Change the value of the initial_start_time_in_utc_value parameter to a different one.
Save the changes.
Restart the collector.

The collector will detect this change and will restart the persistence using the parameters of the configuration file or the default configuration in case it has not been provided.

Note that this action clears the persistence and cannot be recovered in any way. Resetting persistence could result in duplicate or lost events.

This collector has different security layers that detect both an invalid configuration and abnormal operation. This table will help you detect and resolve the most common errors.

Error Type	Error Id	Error Message	Cause	Solution
`InitVariablesError`	2	initial_start_time_in_utc is not set as per the datetime_format : {datetime_format}	The date in config is not as per required format	Ensure the date format is correct
`InitVariablesError`	3	Date {initial_start_time_str} is in the future	The date in configuration is greater than current time	Ensure the datetime is less than current time
`SetupError`	`102`	Failed to fetch data from `{endpoint}`. Source is not pullable.	The provided credentials are incorrect.	Revisit the configuration steps and ensure that the correct values were specified in the config file.

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

  INFO OutputProcess::MainThread -> [GC] global: 67.2% -> 67.2%, process: RSS(104.86MiB -> 104.86MiB), VMS(2.04GiB -> 2.04GiB)
  INFO InputProcess::MainThread -> [GC] global: 66.4% -> 66.4%, process: RSS(112.28MiB -> 112.28MiB), VMS(1.48GiB -> 1.48GiB)

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

Release	Released on	Release type	Details	Recommendations

Release

Released on

Release type

Details

Recommendations

v1.1.0

Mar 12, 2025

status:improvements

Improvements

Updated DevoCollectorSDK version from 1.9.2 to 1.15.0

Recommended version

v1.0.0

Sep 11, 2023

status:INITIAL RELEASE

-

Upgraded

Devo latest