Send data to Devo
Most recent version: v1.2.0
Overview
Onum supports integration with Devo.
Devo is an integrated platform that includes data-powered SIEM, SOAR, and UEBA. It is a cloud-native logging and security analytics platform used to monitor and protect your organization.
Select Devo from the list of Data sink types and click Configuration to start.
Prerequisites
You’ll need a valid Devo tenant, with domain details (region, account) defined.
OAuth token with the correct permissions.
The data you send must include a “tag” or metadata so that Devo knows how to route/process it (which table, which parser) and avoid being classified as unknown.
You’ll typically use TLS/SSL and will need to provide certificates
You’ll need to know the correct ingestion endpoint (which region, protocol: syslog/TLS, HTTP, etc).
Ensure the data you send is in a format that Devo expects (JSON, syslog, etc) and mapped to the correct tag so Devo can parse it into tables properly
Onum Setup
Log in to your Onum tenant and click Data Sinks> New Data sink.
Double-click the Devo Sink.


Enter a Name for the new Data Sink. Optionally, add a Description and some Tags to identify the Sink.


Decide whether or not to include this Data sink info in the metrics and graphs of the Home area.


Specify the Devo Cloud* environment you wish to send your data to (US, EU, or CA). For details on the URLs, see here.
Enter the rules for connecting to this cloud environment:
Net buffer size
Define the number of bytes allocated for buffering network data during transmission to Devo. The minimum value is -1.
Write timeout
Enter the number of milliseconds to wait before considering the request a timeout. The minimum value is 1.
Idle timeout
Enter the milliseconds the connection remains open and idle before it is automatically terminated or closed. The minimum value is 1.
Dial timeout
The maximum time (in ms) allowed for establishing a connection before the attempt is aborted. The minimum value is 1.
Connection Time to Live
The maximum duration (in ms) the connection remains active before it is forcibly closed, regardless of whether it is idle or in use. The minimum value is 1.


Click New secret to create a new one:
Give the secret a Name.
Turn off the Expiration date option.
Click Add new value and paste the corresponding value.
Click Save.


Learn more about secrets in Onum in this article.
You can now select the created secrets in the configuration.
Click Finish when complete. Your new Data sink will appear in the Data sinks area list.
Pipeline configuration
When it comes to using this Data sink in a Pipeline, you must configure the following output parameters. To do it, simply click the Data sink on the canvas and select Configuration.
Output configuration
If your message already has the required format, toggle Passthrough to send on the message exactly as the sink receives it. Uncheck Passthrough to manually format the message:
Type
Output type
The Syslog format to send in:
The original BSD format (Syslog RFC 3164)
The “new” format (Syslog RFC 5424)
If you are unsure about the veracity of the fields you have chosen, you can click Validate to check if they are valid. For the Syslog RCF 3164 type, you have the option to Auto-fix the values to correctly populate them.


You must select the incoming fields that correspond to each value to build the end message in Devo. The fields to configure will differ depending on the Syslog type chosen.
Header
Enter the header parameters:
Priority*/ Severity & Facility* - The field corresponding to the Priority OR the fields corresponding to the Severity and Facility that will be used to make the Priority field.
Timestamp - The field containing the timestamp value.
Hostname - The field containing the hostname.
Message
Enter the fields used to build the body of the message:
Tag - The field containing the tag.
ProcId - The incoming field with the process ID.
Content - The field used as the content field.
Test mode
Decide if you want to send events while they are still processing. This is useful to test the Pipeline without the need for a valid destination.


Header
Enter the header parameters:
Priority* / Severity & Facility* - The field corresponding to the Priority OR the fields corresponding to the Severity and Facility that will be used to make the Priority field.
Timestamp - The field containing the timestamp value.
Hostname - The field containing the hostname.
Appname - The field containing the application name.
ProcID - The field containing the Process ID.
Message ID - The field containing the Message ID.
Structured data
Structured data - Where to source the structured data from.
Message
Enter the fields used to build the body of the message:
Message - The field containing the message body.
Test mode
Decide if you want to send events while they are still processing. This is useful to test the Pipeline without the need for a valid destination.


Click Save to save your configuration.
Last updated
Was this helpful?



