Event Records

From Observer GigaFlow Support | VIAVI Solutions Inc.
Jump to: navigation, search

An Observer GigaFlow Event is a record that is created when a monitored flow pattern matches certain criteria.

Contents

What Generates an Event?

Some things that will trigger an event record include:

  • Attempts to access blacklisted resources.
  • Profile exceptions, i.e. behaviours deviating from norms.
  • A SYN flood event.
  • A lost neighbour.
  • A new connected device sending flows.
  • A connected device that stops sending flows.

See the Event definition in the Glossary and the main entry for Events in the Reference Manual

What is Recorded?

All GigaFlow flow records contain 29 fields or table columns. In the myipfix database associated with the GigaFlow installation, the netflow tables contain all flow records. See Flow Record Fields for the complete list.

Similarly, the Events tables contain all the Event records. See Event Record Fields for a complete list with descriptions. The Event record fields are:

id, customerid, device, firstseen, eventtype, eventsrctype, eventsrc, message, datatype, data, datasource, confidence, severity, category, target, country_src, division_src, latit_src, longd_src, country_dst, division_dst, latit_dst, longd_dst

Three events have both eventtype and posture set in the netflow and event tables in the database, i.e. these three event types can be determined immediately from Netflow records:

Record Field Type Code Description
postureBlackListSrc int -11 Attempted access by blacklisted resources. See also Watchlists in the Reference Manual.
postureBlackListDst int -12 Attempted access to blacklisted resources. See also Watchlists in the Reference Manual.
profilerException int -20 Profile exceptions, i.e. GigaFlow administrator-defined behaviours deviating from norms. See also Profiling in the Reference Manual.

In addition, all of these event types have only eventtype set in the event tables, i.e. these event types are classified with additional information or information from many records and have no postureid set in the netflow tables:

Record Field Type Code Description
synSrc int -100 SYN Source Network Sweep. See also SYN Forensics Monitoring in the Reference Manual.
synSrcPortException int -101 SYN Source Port Sweep. See also SYN Forensics Monitoring in the Reference Manual.
synSrcIPException int -102 SYN Source Unreachable IP. See also SYN Forensics Monitoring in the Reference Manual.
synSrcIPAndPortException int -103 SYN Source Network And Port Sweep. See also SYN Forensics Monitoring in the Reference Manual.
synDst int -120 SYN Destination Network Sweep. See also SYN Forensics Monitoring in the Reference Manual.
synDstPortException int -121 SYN Destination Port Sweep. See also SYN Forensics Monitoring in the Reference Manual.
synDstIPException int -122 SYN Destination Unreachable Server. See also SYN Forensics Monitoring in the Reference Manual.
synDstIPAndPortException int -123 SYN Destination Network And Port Sweep. See also SYN Forensics Monitoring in the Reference Manual.
lldpNewNeighbour int -130 A new connected device sending flows.
lldpLostNeighbour int -131 A lost neighbour.
deviceRestartsSendingFlows int -150 A connected device that stopped sending flows restarts sending flows.
deviceStopsSendingFlows int -151 A connected device that stops sending flows.

How are the Records Accessed?

Data can be accessed:

  1. As a normal user, via the GigaFlow interface. See Events in the Reference Manual.
  2. As an automated portal user, via the GigaFlow API. See Forensic Data Using the API.
  3. From the database directly using a viewer such as pgAdmin or in code using a postgreSQL connector such as Psycopg2 for Python.

Sample Records

See Event Record Fields for some typical records from an Event table with obfuscated IP addresses and locations. As an example:

postureBlackListSrc (-11)

Cut and pasted directly from an Events table:

805729 0 "-1407899398" "1541583542242" -11 8 "xxx.xxx.208.28" "Black List Src Hit(Botnet Strong) xxx.xxx.208.28->xxx.xxx.166.159" 1 {"Application":"SSH TCP/22","Black List":"https://lists.blocklist.de/lists/strongips.txt","Black List Type":"Source","Eventer":"xxx.xxx.208.28","appid":393238,"bytes":44,"device":"xxx.xxx.40.250","domain":"","dstadd":"xx.xxx.166.159","dstport":22,"duration":0,"eventname":"Black List Src","flags":2,"fwevent":0,"fwextcode":0,"inif":14,"macdst":"00:00:00:00:00:00","macsrc":"00:00:00:00:00:00","outif":13,"packets":1,"proto":6,"srcadd":"xxx.xxx.208.28","srcport":28148,"time":1541583574022,"timeH":"7-Nov-2018 09:39:34.22","tos":0,"user":""}" "https://lists.blocklist.de/lists/strongips.txt" 75 80 "Botnet Strong" "xxx.xxx.166.159" "CN" "Gansu" "0.00000000000" "0.00000000000" "IE" "County Sligo" "0.00000000000" "0.00000000000"

Arranged more neatly in a table:

Record Field Value
id 805729
customerid 0
device "-1407899398"
firstseen "1541583542242"
eventtype -11
eventsrctype 8
eventsrc "xxx.xxx.208.28"
message "Black List Src Hit(Botnet Strong) xxx.xxx.208.28->xxx.xxx.166.159"
datatype 1
data {"Application":"SSH TCP/22","Black List":"https://lists.blocklist.de/lists/strongips.txt","Black List Type":"Source","Eventer":"xxx.xxx.208.28","appid":393238,"bytes":44,"device":"xxx.xxx.40.250","domain":"","dstadd":"xx.xxx.166.159","dstport":22,"duration":0,"eventname":"Black List Src","flags":2,"fwevent":0,"fwextcode":0,"inif":14,"macdst":"00:00:00:00:00:00","macsrc":"00:00:00:00:00:00","outif":13,"packets":1,"proto":6,"srcadd":"xxx.xxx.208.28","srcport":28148,"time":1541583574022,"timeH":"7-Nov-2018 09:39:34.22","tos":0,"user":""}"
datasource "https://lists.blocklist.de/lists/strongips.txt"
confidence 75
severity 80
category "Botnet Strong"
target "xxx.xxx.166.159"
country_src "CN"
division_src "Gansu"
latit_src "0.00000000000"
longd_src "0.00000000000"
country_dst "IE"
division_dst "County Sligo"
latit_dst "0.00000000000"
longd_dst "0.00000000000"