Document toolboxDocument toolbox

ids.extrahop

Introduction

The tags beginning with ids.extrahop identify events generated by ExtraHop.

Tag structure

The full tag must have three levels. The first two are fixed as ids.extrahop. The third level identifies the type of event sent. 

These are the valid tags and corresponding data tables that will receive the parsers' data:

Product / Service

Tags

Data tables

Product / Service

Tags

Data tables

ExtraHop solution

ids.extrahop.audit

ids.extrahop.audit

ids.extrahop.cifs

ids.extrahop.cifs

ids.extrahop.crwd

ids.extrahop.crwd

ids.extrahop.detections

ids.extrahop.detections

ids.extrahop.dhcp

ids.extrahop.dhcp

ids.extrahop.dns

ids.extrahop.dns

ids.extrahop.flow

ids.extrahop.flow

ids.extrahop.ftp

ids.extrahop.ftp

ids.extrahop.http

ids.extrahop.http

ids.extrahop.kerberos

ids.extrahop.kerberos

ids.extrahop.ldap

ids.extrahop.ldap

ids.extrahop.llmnr

ids.extrahop.llmnr

ids.extrahop.mongodb

ids.extrahop.mongodb

ids.extrahop.nfs

ids.extrahop.nfs

ids.extrahop.ntlm

ids.extrahop.ntlm

ids.extrahop.rdp

ids.extrahop.rdp

ids.extrahop.rfb

ids.extrahop.rfb

ids.extrahop.rpc

ids.extrahop.rpc

ids.extrahop.ssh

ids.extrahop.ssh

ids.extrahop.ssl

ids.extrahop.ssl

ids.extrahop.telnet

ids.extrahop.telnet

For more information, read more about Devo tags.

How is the data sent to Devo?

You can send the logs generated by ExtraHop using the tool NXLog. Learn more about how to configure your product and start forwarding logs to Devo here.

Table structure

These are the fields displayed in these tables: