Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    SNORT mistaken classification

    Scheduled Pinned Locked Moved pfSense Packages
    2 Posts 2 Posters 601 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      strainu
      last edited by

      I encountered a weird behavior from SNORT today. It blocked a valid, useful IP (212.146….), which has happened before, only this time with the reason "ET COMPROMISED Known Compromised or Hostile Host Traffic UDP group 24".

      I checked the files /usr/local/etc/snort/rules/emerging-compromised.rules and /usr/local/etc/snort/rules/emerging-compromised-ips.txt , but the IP is not there. Is it a case of mistaken classification, a display error or just some kind of fuzzy rule that matched the traffic?

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        Did you double-check whether or not the rule specified a netblock that might encompass the IP?

        Bill

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.