Cohesity collector
Overview
Cohesity gives you both data security and data management. Defend against ransomware with immutable backup, AI-based early threat detection, and rapid data.
The Cohesity collector takes events from v2/mcm/
endpoints. This API is very tough to work with, as it will add events over 1 hour later. To prevent this, the collector will perform a check every 10 minutes (now()-65m < evendate < now()-55m
) to guarantee the minimal amount of event loss.
Devo collector features
Feature | Details |
---|---|
Allow parallel downloading ( |
|
Running environments |
|
Populated Devo events |
|
Flattening preprocessing |
|
Allowed source events obfuscation |
|
Data sources
Data source | API endpoint | Collector service name | Devo table |
---|---|---|---|
Helios Audit |
|
|
|
Helios Alert |
|
|
|
For more information on how the events are parsed, visit our page.
Flattening preprocessing
The audit logs have flattening enabled. the have a dictionary inside the record called new record. The new record will be extracted and applied to the original log.
For example: {a: 1, b: 2, c: [{name: john},{name: scott}]}
will show up in Devo as unflattened. The flattening will happen and you'll get the additional logs, such as:
{"a": 1, "b": 2, "newRecord": [{"name": "john"}]} {"a": 1, "b": 2, "newRecord": [{"name": "scott"}]}
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 |
---|---|
| The name of the API given in setup. |
| The key generated in setup. |
Accepted authentication methods
Authentication method | api_key_name | api_key |
---|---|---|
OAuth2 | REQUIRED | REQUIRED |
Vendor setup
Follow these steps to get the required credentials:
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.
Alerts (alerts
)
Internal process and deduplication method
All alerts data are pulled with an Id value. The collector checks the Ids each run. Checkpoints are persisted to ensure that duplicate data is not sent to Devo.
Devo categorization and destination
All events of this service are ingested into the table dmp.cohesity.helios.alerts
.
Setup output
2024-04-09T09:56:19.561389088Z 2024-04-09T09:56:19.561 WARNING InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,alerts#predefined) -> Testing fetch from /mcm/alerts.
2024-04-09T09:56:19.771898077Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0
2024-04-09T09:56:19.772167710Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0
2024-04-09T09:56:19.772327665Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {}
2024-04-09T09:56:19.772395427Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {}
2024-04-09T09:56:19.772425735Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Sender: DevoSender(internal_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": True}
2024-04-09T09:56:19.772519048Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Sender: DevoSender(lookup_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": False}
2024-04-09T09:56:19.772601144Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Internal - Total number of messages: 6333 messages/bytes sent since/to "2024-04-09T09:51:19.771169+00:00/2024-04-09T09:56:19.772408+00:00": 25/13762, (elapsed 0.052 seconds)
2024-04-09T09:56:19.772631900Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Lookup - Total number of messages sent: 0, messages sent since "2024-04-09 09:51:19.770969+00:00": 0 (elapsed 0.000 seconds)
2024-04-09T09:56:20.261298432Z 2024-04-09T09:56:20.261 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,alerts#predefined) -> Successfully tested fetch from /mcm/alerts. Source is pullable.
2024-04-09T09:56:20.262730750Z 2024-04-09T09:56:20.262 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,alerts#predefined) -> Setup for module <CohesityPuller> has been successfully executed
Puller output
2024-04-09T09:56:22.704294203Z 2024-04-09T09:56:22.704 INFO InputProcess::CohesityPuller(cohesity,56752,alerts,predefined) -> Pull Started
2024-04-09T09:56:23.124016843Z 2024-04-09T09:56:23.123 INFO InputProcess::CohesityPuller(cohesity,56752,alerts,predefined) -> Updating the persistence
2024-04-09T09:56:23.124811682Z 2024-04-09T09:56:23.124 INFO InputProcess::CohesityPuller(cohesity,56752,alerts,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1712656582704):Number of requests made: 535; Number of events received: 2; Number of duplicated events filtered out: 0; Number of events generated and sent: 2; Average of events per second: 4.759.
Restart the persistence
Update the unique ID of the collector and restart, this will remove the Id values that have been pulled. This may cause duplicates.
Audit (audit
)
Internal process and deduplication method
Alerts are pulled with start time value, that value is updated anytime logs are found. If no logs are found the start time is not persisted. The start time will be used until logs are found.
Devo categorization and destination
All events of this service are ingested into the table dmp.cohesity.helios.audidt
.
Setup output
2024-04-09T09:56:19.561389088Z 2024-04-09T09:56:19.561 WARNING InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,audit#predefined) -> Testing fetch from /mcm/get-audit.
2024-04-09T09:56:19.771898077Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0
2024-04-09T09:56:19.772167710Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0
2024-04-09T09:56:19.772327665Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {}
2024-04-09T09:56:19.772395427Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {}
2024-04-09T09:56:19.772425735Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Sender: DevoSender(internal_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": True}
2024-04-09T09:56:19.772519048Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Sender: DevoSender(lookup_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": False}
2024-04-09T09:56:19.772601144Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Internal - Total number of messages: 6333 messages/bytes sent since/to "2024-04-09T09:51:19.771169+00:00/2024-04-09T09:56:19.772408+00:00": 25/13762, (elapsed 0.052 seconds)
2024-04-09T09:56:19.772631900Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Lookup - Total number of messages sent: 0, messages sent since "2024-04-09 09:51:19.770969+00:00": 0 (elapsed 0.000 seconds)
2024-04-09T09:56:20.261298432Z 2024-04-09T09:56:20.261 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,audit#predefined) -> Successfully tested fetch from /mcm/get-audit. Source is pullable.
2024-04-09T09:56:20.262730750Z 2024-04-09T09:56:20.262 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,audit#predefined) -> Setup for module <CohesityPuller> has been successfully executed
Puller output
Restart the persistence
Update the unique Id of the collector and restart, this will remove the Id values that have been pulled. This may cause duplicates.
Troubleshooting
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.
Common logic
Error type | Error ID | Error message | Cause | Solution |
---|---|---|---|---|
|
| Connection Error - Ensure the URL parameters are correct and that host has access to server. | Could Not connect to the Host | Ensure the endpoint is reachable with the credentials |
|
| Max Retries Error - Request attempts with {retries} retries failed. \n{reason} | Max Retries Hit | Update rate limits |
|
| Failed to fetch from {endpoint}. Error: {e} | The collector was unable to access the specified endpoint. | Ensure the endpoint is reachable with the credentials |
Collector operations
This section is intended to explain how to proceed with specific operations of this collector.
Change log
Release | Released on | Release type | Details | Recommendations |
---|---|---|---|---|
| Apr 9, 2024 | INITIAL RELEASE | Initial release |
|