DataProtect

Send Cohesity DataProtect audit and data protection logs to Axoflow, and look up the labels that Axoflow adds to its data.

DataProtect: Backup and recovery cluster that sends cluster audit, API access, data protection, and SMB file audit events.

To onboard such a source to Axoflow, complete the generic appliance onboarding steps.

Labels

Axoflow automatically adds the following labels to data collected from this source:

Analytics label	Message field	value
`vendor`	`meta.vendor`	`cohesity`
`product`	`meta.product`	`dataprotect`
`service`	`meta.service.name`	`cluster_audit`, `api_audit`, `dataprotection_events`, `filesystem_audit`, `shell_commands_audit`, or `cli_audit`

The service label depends on the Cohesity log that the message comes from (the program name in the syslog header):

cluster_audit: Cluster audit log
api_audit: API access audit log
dataprotection_events: Data protection events
filesystem_audit: File system (SMB) audit log
shell_commands_audit: Shell commands audit log
cli_audit: CLI audit log

You can use the labels as:

labels in Customize Graph on the Analytics page,
in the Filter labels field during log tapping.

You can use the message fields

in Flow Processing steps, for example, in the Query field of Select Messages steps,
in AQL expressions in the search bars.

Sending data to Splunk

When sending the data collected from this source to Splunk, Axoflow uses the following sourcetype and index settings:

sourcetype	index
`cohesity:api:audit`	`infraops`
`cohesity:cluster:audit`	`infraops`
`cohesity:cluster:dataprotection`	`infraops`

The api_audit service uses the cohesity:api:audit sourcetype, the dataprotection_events service uses cohesity:cluster:dataprotection, and every other service uses cohesity:cluster:audit.

If the Axoflow classification doesn’t set the source field for the message automatically, and you haven’t set it in a flow processing step manually (by setting the meta.destination.splunk.source field), AxoRouter automatically sets the source to the name of the AxoRouter connector that received the message (for example, axorouter-syslog-tcp-514).

Sending data to Google SecOps

When sending the data collected from this source to a dynamic Google SecOps destination, Axoflow sets the following log type: COHESITY.