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.

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

Identify suspicious connections and IP addresses #685

Open
GyulyVGC opened this issue Jan 24, 2025 · 0 comments
Open

Identify suspicious connections and IP addresses #685

GyulyVGC opened this issue Jan 24, 2025 · 0 comments
Labels
enhancement New feature, request, or improvement

Comments

@GyulyVGC
Copy link
Owner

GyulyVGC commented Jan 24, 2025

Identify suspicious connections and IP addresses:

  • such entries should be highlighted in:
    • the network host list in Overview page
    • the Inspect page table
  • a new notification kind should be added to warn about suspicious connections

Suspicious entries could be identified using a collection of IP blacklists available online (see ipsum).

Proper handling of the download and usage of such resource should also be taken into account:

  • download the resource on startup, only if the latest download is older than a certain date (one week?)
  • store the resource in a local file (MMDB? SQLite? Text?)
  • load the resource from memory on startup, or query it for each new observed IP address
  • create mirrors of the resource on GitLab / BitBucket / other, in case the ipsum repo is down on GitHub
@GyulyVGC GyulyVGC added the enhancement New feature, request, or improvement label Jan 24, 2025
@GyulyVGC GyulyVGC added this to the v1.4.0 milestone Jan 24, 2025
@GyulyVGC GyulyVGC self-assigned this Jan 24, 2025
@GyulyVGC GyulyVGC removed this from the v1.4.0 milestone Jan 25, 2025
@GyulyVGC GyulyVGC removed their assignment Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature, request, or improvement
Projects
None yet
Development

No branches or pull requests

1 participant