Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split Blacklisted Flow Alert+Check #8354

Closed
lucaderi opened this issue Apr 24, 2024 · 1 comment
Closed

Split Blacklisted Flow Alert+Check #8354

lucaderi opened this issue Apr 24, 2024 · 1 comment
Assignees
@NicoMaio
Labels
Enhancement Priority Ticket Ready to Test a feedback is needed on a proposal or implementation

Comments

@lucaderi
Copy link
Member

lucaderi commented Apr 24, 2024 •
edited

Currently, the Blacklisted Flow Alert+Check is used for both ingress (remote host-> local) and egress (local -> remote). This is to request to

  • split the alert+check into two: Blacklist Client Contact, and Blacklist Server Contact
  • the first alert+check is triggered only for a remote blacklisted host that contacts a local host. the second is the opposite when a local host contacts (client) a remote blacklisted host (as a server)
  • the first alert+check is informative with low score (10 or so), the second is critical with max score
NicoMaio added a commit to NicoMaio/ntopng that referenced this issue Apr 24, 2024
@NicoMaio
Splitting blacklisted flow alert and creating two new alerts. (ntop#8354
c4292c6 
)
@NicoMaio NicoMaio mentioned this issue Apr 24, 2024
Merged
NicoMaio added a commit to NicoMaio/ntopng that referenced this issue Apr 24, 2024
@NicoMaio
Renaming to 'Blacklisted Client Contact' and 'Blacklisted Server Cont…
ce2f0dd 
…act'. (ntop#8354)
lucaderi pushed a commit that referenced this issue Apr 24, 2024
@NicoMaio
Splitting blacklisted flow alert and creating two new alerts. (#8354) (…
59075f5 
…#8355)

* Splitting blacklisted flow alert and creating two new alerts. (#8354)

* Renaming to 'Blacklisted Client Contact' and 'Blacklisted Server Contact'. (#8354)
@NicoMaio NicoMaio added the Ready to Test a feedback is needed on a proposal or implementation label Apr 24, 2024
@lucaderi
Copy link
Member Author

Verified as fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NicoMaio NicoMaio

Labels
Enhancement Priority Ticket Ready to Test a feedback is needed on a proposal or implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lucaderi @NicoMaio