Document toolboxDocument toolbox

ids.extrahop

Owned by Juan Tomás Alonso Nieto (Deactivated)
Jul 06, 2022
1 min read
[ 1 Introduction ] [ 2 Tag structure ] [ 3 How is the data sent to Devo? ]

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. 

Technology

Brand

Type

Technology

Brand

Type

ids

extrahop

  • audit

  • detections

  • cifs

  • crwd

  • dhcp

  • dns

  • ftp

  • http

  • kerberos

  • ldap

  • llmnr

  • mongodb

  • nfs

  • ntlm

  • rdp

  • rfb

  • rpc

  • ssh

  • ssl

  • telnet

  • flow

Therefore, the valid tags and tables include:

  • ids.extrahop.audit

  • ids.extrahop.detections

  • ids.extrahop.cifs

  • ids.extrahop.crwd

  • ids.extrahop.dhcp

  • ids.extrahop.dns

  • ids.extrahop.ftp

  • ids.extrahop.http

  • ids.extrahop.kerberos

  • ids.extrahop.ldap

  • ids.extrahop.llmnr

  • ids.extrahop.mongodb

  • ids.extrahop.nfs

  • ids.extrahop.ntlm 

  • ids.extrahop.rdp

  • ids.extrahop.rfb

  • ids.extrahop.rpc

  • ids.extrahop.ssh

  • ids.extrahop.ssl

  • ids.extrahop.telnet

  • ids.extrahop.flow

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.