Project

General

Profile

Actions

Bug #6092

closed

eve/alert: missing pgsql metadata

Added by Philippe Antoine over 1 year ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Beginner, Good First Issue


Related issues 3 (0 open3 closed)

Related to Suricata - Optimization #3827: clean up logging initialization codeClosedPhilippe AntoineActions
Related to Suricata - Bug #6983: alert/metadata: no pgsql object encapsulationClosedJuliana Fajardini ReichowActions
Copied from Suricata - Bug #5977: eve/alert: missing KRB5 metadataClosedPhilippe AntoineActions
Actions #1

Updated by Philippe Antoine over 1 year ago

  • Copied from Bug #5977: eve/alert: missing KRB5 metadata added
Actions #2

Updated by Philippe Antoine 12 months ago

Actions #3

Updated by Juliana Fajardini Reichow 7 months ago

  • Status changed from New to In Progress
  • Assignee changed from OISF Dev to Juliana Fajardini Reichow
  • Target version changed from TBD to 8.0.0-beta1
Actions #4

Updated by Juliana Fajardini Reichow 7 months ago

  • Status changed from In Progress to In Review
Actions #5

Updated by Juliana Fajardini Reichow 7 months ago

  • Status changed from In Review to Closed
Actions #6

Updated by Philippe Antoine 7 months ago

@Juliana Fajardini Reichow I do not see a SV test with an alert event and pgsql metadata
Is there one ?

Actions #7

Updated by Juliana Fajardini Reichow 7 months ago

Philippe Antoine wrote in #note-6:

@Juliana Fajardini Reichow I do not see a SV test with an alert event and pgsql metadata
Is there one ?

No, I haven't finished work on PGSQL events yet. I only followed the approach as seen for MQTT, for proposing a solution for this ticket. Should I reopen this ticket?

Actions #8

Updated by Philippe Antoine 7 months ago

Juliana Fajardini Reichow wrote in #note-7:

No, I haven't finished work on PGSQL events yet. I only followed the approach as seen for MQTT, for proposing a solution for this ticket. Should I reopen this ticket?

I think you do not need events for this.

You can see for instance commit 4d2bd8cc38bb8d78cb8c473e831cb41140e3a80c in SV, about test output-eve-tftp-01 adding a check for an alert event with some tftp details

Actions #9

Updated by Juliana Fajardini Reichow 7 months ago

Philippe Antoine wrote in #note-8:

Juliana Fajardini Reichow wrote in #note-7:

No, I haven't finished work on PGSQL events yet. I only followed the approach as seen for MQTT, for proposing a solution for this ticket. Should I reopen this ticket?

I think you do not need events for this.

You can see for instance commit 4d2bd8cc38bb8d78cb8c473e831cb41140e3a80c in SV, about test output-eve-tftp-01 adding a check for an alert event with some tftp details

But would that work without detection capabilities for pgsql? :/

Actions #10

Updated by Philippe Antoine 7 months ago

I guess so : there is no tftp keyword

Actions #11

Updated by Juliana Fajardini Reichow 6 months ago

Philippe Antoine wrote in #note-10:

I guess so : there is no tftp keyword

Thanks, I was trying and my tests were failing, but turns out that I (once again) had forgotten to add alert event types to my EVE logs ;_;

Actions #12

Updated by Juliana Fajardini Reichow 6 months ago

  • Related to Bug #6983: alert/metadata: no pgsql object encapsulation added
Actions #13

Updated by Juliana Fajardini Reichow 6 months ago

Philippe Antoine wrote in #note-10:

I guess so : there is no tftp keyword

Philippe Antoine wrote in #note-6:

@Juliana Fajardini Reichow I do not see a SV test with an alert event and pgsql metadata
Is there one ?

Does this work? https://github.com/OISF/suricata-verify/pull/1796

Actions #14

Updated by Philippe Antoine 6 months ago

Looking good, will review it there

Actions

Also available in: Atom PDF