Differences

This shows you the differences between two versions of the page.

--- wiki:firewall [2021/07/30 02:33] – created guidebeacon
+++ wiki:firewall [2023/10/05 19:29] (current) – guidebeacon
@@ Line 1: / Line 1: @@
 ====== Firewall ======
-Beacontechnology uses CSF to manage the linux firewall
+The cPanel servers make use of various firewalling features
-===== General Management =====
+''chost.beacontechnology'' uses ''Host Access Control'' to manage the Linux firewall (nftables).
-==== Whitelisting IPs ====
+===== cPHulk =====
-IPs can be whitelisted two different ways, either via the web interface or SSH
+''cPHulk'' is part of cPanel and will ban IPs that log too many login failures. ''cPHulk'' does not normally completely firewall off blocked IPs, and instead only blocks them from logging in. This is fixed by a custom script that imports these rules into nftables on a schedule.
-If using the web interface:
+''cPHulk'' has a whitelist, blacklist and country management feature. These are managed by the user.
-  - Go to WHM > ConfigServer Security & Firewall
+The script that dumps the whitelist and country blacklist, and imports them into ''nftables''.
-  - Click "csf" tab near the top, under the banners
-  - Under "csf - ConfigServer Firewall" click "Firewall Allow IPs"
-  - Add IP and comment to list how the rest are
-  - Click Change
-  - Click Restart csf+lfd
-If using shell/ssh
+''/etc/cron.daily/update_firewall.sh''
-  - Edit ''/etc/csf/csf.allow''
+==== Whitelist Management  ====
-  - Add entries like the others and save the file
-  - Run: ''csf -ra''
-==== Removing Banned IPs ====
+In general it is a good idea to whitelist administrative IPs to avoid getting banned.
-=== CSF ===
+To do so:
-While the server only allows whitelisted IPs to connect, it might be possible that the server can ban someone that is on the list if they try to log in too many times.
+  - Go to WHM > cPHulk Brute Force Protection
+  - Click on Whitelist Management tab
+  - If logging in from an IP not on the list, there might be a popup with a button that can be pressed to add the current IP to the list.
+  - If not, add the IP to the box and put a comment with # character if needed.
+  - When done, click "Add"
-  - Under WHM > ConfigServer Security & Firewall
+To remove an IP from the whitelist, just click delete from the same interface.
-  - Go to: csf - ConfigServer Firewall
-  - Where it says: Search for IP, type in their IP and click Search.
-  - If something comes back, click Return
-  - Go to: csf - Quick Actions
-  - Type in the IP to Quick Unblock and click the button
+Do not forget to update the firewall by running the script: ''/etc/cron.daily/update_firewall.sh''
-=== cPHulk ===
+The script runs daily, but running it now will immediately update the firewall.
-cPHulk can also block IPs for various reasons.
+**Do not forget to add the IP to each of the 2 accounts, master on chost and beacontechnology on kingscpw01.**
-To find blacklisted IPs:
+[[wiki:firewall#allowing_ips_to_locked_down_cpanel_accounts|Click here to learn more]]
-Go to: WHM > cPHulk Brute Force Protection
+==== Blacklist Management ====
-Click "Blacklist Management"
-You should see all IPs block by cPHulk on this page
-If you want to remove an IP from the list, just click Delete and Continue
-You can also whitelist in cPHulk as well by going to the "Whitelist Management page". If you are whitelisting yourself from your current machine, you can just click "Add to Whitelist" on the red box.
+Sometimes the user might be banned, or can't connect to a specific service for some unknown reason. It could be cPHulk blocking them.
+To unblock:
-===== Installation General Information =====
+  - Go to WHM > cPHulk Brute Force Protection
+  - Click on Blacklist Management tab
+  - Search for the IP in question, if the IP is unknown, ask the user to go to: ipecho.net and read the IP back.
+  - When the record is located, click "Delete"
-Two main things need to be set up
+==== Troubleshooting ====
-  - CSF needs to be configured to not allow any ports
+It may  be the case that sometimes the script gives an error for various reasons, here are some steps to try to fix it:
-  - IPs need to be added to the ''csf.allow'' list
-==== Installation ====
+  - Try rebooting server
+  - Try making a change in cpHulk like adding/removing an IP and trying again
+  - Try this command: ''nft flush set inet filter ccblockset'' and try again
+  - try this command: WARNING, may result in getting locked out, add your IP to ''/etc/sysconfig/nftables.conf'' before proceeding... ''nft flush set inet filter adminwhitelist''
+===== Host Access Control =====
-The administrative security policy requires that only specified Ips are allow to connect to the dev server. CSF is one of the most popular cPanel plugins to somewhat easily control the linux firewall.
+New instructions:
-[[https://docs.cpanel.net/knowledge-base/security/additional-security-software/#configserver-software|Click Here]] for the documentation to set up CSF.
+CSF is no longer necessary, a basic firewall solution now comes with cPanel and is called ''Host Access Control''.
-Otherwise, run these commands:
+''Host Access Control'' provides a basic firewall interface that integrates with Linux nftables.
-<code>
+The current rules can be viewed by going to WHM > Host Access Control
-cd /root
-wget https://download.configserver.com/csf.tgz
-tar -xzf csf.tgz
-cd csf
-./install.cpanel.sh
-# reboot server
+Host Access Control is very basic and does not natively handle expressions like "any port", and so some rules say "undefined" for certain parts. This just means that the rule was manually added to ''/etc/sysconfig/nftables.conf''
-sed -ibak 's/^TESTING = "1"/TESTING = "0"/'
+To Add new rules:
-sed -r -ibak 's/^TCP_IN = "[0-9,]+"/TCP_IN = ""/' /etc/csf/csf.conf
-sync; csf -ra
+  - edit: ''/etc/sysconfig/nftables.conf''
+  - Scroll the sections where it says ''chain cPanel-HostAccessControl''
+  - Please copy an existing rule and edit it to what is needed.
+  - When done, save and exit
+  - run the command: ''systemctl restart nftables.service''
+  - When the WHM Host Access Control page is reloaded, the changes should now be reflected.
+Also note that rules are dynamically loaded into nftables by ''update_firewall.sh''.
+===== update_firewall.sh =====
+This script help managing nftables
+<code bash update_firewall.sh>
+#!/bin/bash
+# this script extends cpHulk to assist managing nftables.
+# country codes selected in CPhulk will be banned at the IP level
+# whitelisted ips will be included as administratively allowed
+set -e
+trap 'catch $? $LINENO' EXIT
+catch() {
+  if [ "$1" != "0" ]; then
+    echo failed to update firewall rules
+    echo "Error $1 occurred on $2"
+  fi
+}
+geoipdir='/usr/local/cpanel/3rdparty/share/geoipfree/country-cidrs'
+whitelist=$(mktemp)
+blacklist=$(mktemp)
+# get list of CCs that are blocked
+cclist=$( whmapi1 --output=json load_cphulk_config |
+          jq -r '.data.cphulk_config.country_blacklist' )
+# loop over list and concat all subnets from cpanel free geoip
+for i in ${cclist//,/ }; do
+  grep -oP '(\d+\.){3}\d+/\d+' $geoipdir/$i | tr '\n' ',' >> $blacklist
+done
+# write list of whitelist ips to temp file
+whmapi1 --output=json read_cphulk_records list_name='white' |
+        jq -r '.data.ips_in_list | keys[]' | grep -oP '(\d+\.){3}\d+' > $whitelist
+# generate new rules for nftables
+{
+  echo 'flush set inet filter ccblockset'
+  echo 'flush set inet filter adminwhitelist'
+  # create whitelist set
+  echo -n 'add element inet filter adminwhitelist { '
+  cat $whitelist | tr '\n' ','
+  echo ' }'
+  # create blacklist set
+  echo -n 'add element inet filter ccblockset { '
+  cat $blacklist | tr '\n' ','
+  echo ' }'
+} | nft -f -
+echo firewall was successfully updated
 </code>
+===== Allowing IPs to locked down cpanel accounts =====
+On some accounts, there is htaccess that whitelists IPs for extra security.
+The htaccess is normally at: ''/home/username/public_html/.htaccess''
+The area you are looking for looks something like this:
+<code>order allow,deny
+allow from xxx.xxx.xxx.xxx
+allow from xxx.xxx.xxx.xxx
+allow from xxx.xxx.xxx.xxx
+allow from xxx.xxx.xxx.xxx</code>
+Just add a similar new entry below the last one in the list