threatintel.bandura
- Juan Tomás Alonso Nieto (Unlicensed)
Introduction
The tags beginning with threatintel.bandura identify events generated by Bandura.
Valid tags and data tables
The full tag must have 4 levels. The first two are fixed as threatintel.bandura. The third level identifies the type of events sent, and the fourth level indicates the event subtype.
Technology | Brand | Type | Subtype |
|---|---|---|---|
threatintel | bandura |
|
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
|---|---|
threatintel.bandura.threatblockr.dnslog | threatintel.bandura.threatblockr.dnslog |
threatintel.bandura.threatblockr.dnsresplog | threatintel.bandura.threatblockr.dnsresplog |
threatintel.bandura.threatblockr.packetlog | threatintel.bandura.threatblockr.packetlog |
How is data sent to Devo?
Logs generated by Bandura are forwarded to Devo using a dedicated collector. Contact us if you need to forward these events to your Devo domain so we can guide you through the process.
Log samples
The following are sample logs sent to each of the threatintel.bandura data tables. Also, find how the information will be parsed in your data table under each sample log.
Extra columns
Fields marked as Extra in the table below are not shown by default in data tables and need to be explicitly requested in the query. You can find them marked as Extra when you perform a query so they can be easily identified. Learn more about this in Selecting unrevealed columns.