{"id":117,"date":"2024-10-11T11:54:00","date_gmt":"2024-10-11T16:54:00","guid":{"rendered":"https:\/\/danielbondurantcybersecurityportfolio.online\/?p=117"},"modified":"2024-11-07T10:00:55","modified_gmt":"2024-11-07T16:00:55","slug":"custom-firewall-with-suricata-part-3-ip-reputation","status":"publish","type":"post","link":"https:\/\/danielbondurantcybersecurityportfolio.online\/?p=117","title":{"rendered":"Custom Firewall with Suricata Part 3: IP Reputation"},"content":{"rendered":"\n

This is the final part for building a custom firewall with the utilization of IP Reputation within Suricata.<\/p>\n\n\n\n

The first step to take is to go into ‘suricata.yaml’, go to the IP Reputation section, and remove the comment tags from the configurations. The next step is to create the necessary files and directory that are listed. So make the ‘iprep’ directory and make ‘categories.txt’ and ‘reputation.list’ inside of the directory.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

For formatting these two files properly, here are screenshots from the Suricata documentation:<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

\n\n\n\n
\n\n\n\n

For this example, here is the ‘categories.txt’ file:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

And here is the ‘reputation.list’ file:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This example reputation will trigger on any IP address in the 1.0.0.0\/24 range.<\/p>\n\n\n\n

Now we need to go to the ‘custom.rules’ file we made with the custom Suricata alert rules and add a new rule using IP Rep.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This rule alerts on IP activity from the home network going to any IP address. <\/p>\n\n\n\n

iprep:dst,Custom,>,0;<\/code><\/pre>\n\n\n\n
For the ‘iprep’ section of the rule, we are using destination, not source, to prevent blocking our internal IP address. ‘Custom’ is the category name from the ‘categories.txt’ file. The ‘>,0’ indicates that anything with a reputation greater than 0 will be detected and blocked. This allows the potential to block thousands of IP addresses without having to make thousands of rules in the firewall.<\/p>\n\n\n\n
\n\n\n\n
Now to put everything together, first we will check firewall with ‘iptables’:<\/p>\n\n\n\n
<\/p>\n\n\n\n
Currently nothing being blocked. <\/p>\n\n\n\n
Next, we will make sure Supervisor is running with our alert daemon:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
This shows the alert daemon is running.<\/p>\n\n\n\n
Now we can start Suricata, then ping any address in the 1.0.0.0\/24 range:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
We can see that the alert was generated in the fast log, and if we try to ping 1.0.0.1 again, there is 100% packet loss this time. Checking the ‘iptables’ shows that 1.0.0.1 has been added to the firewall and is being blocked.<\/p>\n","protected":false},"excerpt":{"rendered":"
This is the final part for building a custom firewall with the utilization of IP Reputation within Suricata. The first step to take is to go into ‘suricata.yaml’, go to the IP Reputation section, and remove the comment tags from the configurations. The next step is to create the necessary files and directory that are […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,9],"tags":[],"class_list":["post-117","post","type-post","status-publish","format-standard","hentry","category-linux","category-suricata"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=\/wp\/v2\/posts\/117","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=117"}],"version-history":[{"count":6,"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=\/wp\/v2\/posts\/117\/revisions"}],"predecessor-version":[{"id":139,"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=\/wp\/v2\/posts\/117\/revisions\/139"}],"wp:attachment":[{"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/danielbondurantcybersecurityportfolio.online\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}