Feature #5664
open
"Scope" bits should have an expiration
Added by Philippe Antoine almost 2 years ago.
Updated 5 months ago.
Description
New kind of "bits" need to be implemented. These should be able to have different scope like transaction. This means that the bits should expire when a tx does
Related issues
6 (6 open — 0 closed)
- Related to Task #4380: tracking: improvements to bits, ints, vars added
- Related to Task #5488: Suricon 2022 brainstorm added
- Assignee changed from OISF Dev to Shivani Bhardwaj
- Target version changed from TBD to 7.0.0-rc1
- Subject changed from Flowbit expiration to "Scope" bits with expiration
- Description updated (diff)
- Target version changed from 7.0.0-rc1 to 8.0.0-beta1
- Status changed from New to Assigned
- Related to Task #6443: Suricon 2023 brainstorm added
- Related to Feature #5665: rules: bidirectional transaction matching added
- Subject changed from "Scope" bits with expiration to "Scope" bits should have an expiration
filebit and txbit should have an expiration.
- Related to Feature #6455: txbits: support for new type of bits added
- Related to Feature #6459: filebits: support for new type of bits added
I think #5665 solves most of the needs for this
So, it would be nice to get #5665 and then get feedback again about this one
Also available in: Atom
PDF