Project

General

Profile

Actions

Feature #7391

open
JF OD

detect/config: 'scope' can't be applied to 'flow'

Feature #7391: detect/config: 'scope' can't be applied to 'flow'

Added by Juliana Fajardini Reichow almost 2 years ago. Updated 15 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Description

Although the documentation already states this (see https://docs.suricata.io/en/latest/rules/config.html#keyword), from the code,
it seems that this should be allowed.

There are also optimization requests that would require this option to exist (cf.: #5643 )


Related issues 2 (1 open1 closed)

Related to Suricata - Optimization #5643: pcap: rule based conditional pcap loggingNewOISF DevActions
Related to Suricata - Bug #6663: Config rules does not disable logging.RejectedActions

JF Updated by Juliana Fajardini Reichow almost 2 years ago Actions #1

  • Related to Optimization #5643: pcap: rule based conditional pcap logging added
  • Related to Bug #6663: Config rules does not disable logging. added

PA Updated by Philippe Antoine about 1 year ago Actions #2

This is not a bug, just a feature for support of scope flow. am I getting it right ?

PA Updated by Philippe Antoine about 1 year ago Actions #3

  • Status changed from New to Feedback

PA Updated by Philippe Antoine about 1 month ago Actions #4

  • Tracker changed from Bug to Feature

JF Updated by Juliana Fajardini Reichow 15 days ago Actions #5

Philippe Antoine wrote in #note-2:

This is not a bug, just a feature for support of scope flow. am I getting it right ?

To me, it's either a bug, or the doc needs improvement. Because from the documentation, I if I see that the `type` can be `flow`,
I expect that a `scope` should be possibly applied to a flow.

(To be honest, the doc is confusing to me and I think we would benefit from examples there, to clarify them)

Actions

Also available in: PDF Atom