NIOS
NIOS: Delivers secure DNS, DHCP, and IPAM (DDI) services with centralized network control and automation.
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
|
infloblox |
product |
meta.product
|
nios |
service |
meta.service.name
|
named, threat-protect-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 | source |
|---|---|---|
infoblox:threatprotect |
netids |
Infoblox:NIOS |
infoblox:dns |
netids |
Infoblox:NIOS |
Tested with: Splunk Add-on for Infoblox
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: INFOBLOX, INFOBLOX_DNS.
Sending data to Microsoft Sentinel
When sending the data collected from this source to a Microsoft Sentinel destination
, Axoflow normalizes the data and sends it to the following table: Syslog.