New csf v8.08


  • Fixed csf.sips modification via UI on Redhat/CentOS v7.1
  • Raised csf.blocklist names from 9 to 25 characters long. This cannot be greater due to limits on ipset names on some OS’s and the use of prepended names for new ipset list swapping
  • Added output from netstat for PT_LOAD to loadalert.txt for new installs. For existing installs, latest file copied to /usr/local/csf/tpl/

New cxs v6.00


  • Added new major feature for cxs Watch: –Wmonitor [file] This option allows you to monitor and report on changes to a list of resources in [file]. See cxs POD for more information
  • Added option –Wmonignore [file] to use instead of –ignore [file] for use with –Wmonitor [file]
  • Added IO::Select as a required perl module (a core perl module so should always be present)
  • Improvements to php file detection
  • Improvements to deobfuscation routines
  • Fixed bug in display of atime for some quarantined files
  • Fix BCC header replacement field in email reports
  • Exploit fingerprint definitions database additions

New csf v8.07


  • Ensure spaces are stripped from values in /etc/cpanel/ea4/paths.conf on cPanel servers
  • Fixed issue with csf –add [ip] not always removing [ip] if present from csf.deny
  • Modified the LF_QOS regex to cater for additional log formats

New cxs v5.32


  • Force email Date: field incase the MTA fails to add one
  • Modified all report timestamps to use the same format
  • Exploit fingerprint definitions database additions

New cmc v2.00


  • Added Easyapache v4 support
  • Removed references to as it is no longer used by cPanel
  • Fixed modify file list to only list actual files

New csf v8.06


  • Added port 24441 to UDP_OUT and UDP6_OUT for new installs on cPanel servers for Pyzor that was added by cPanel in v11.52
  • Support added for EasyApache4 log locations in cPanel from /etc/cpanel/ea4/paths.conf
  • Added more executable files to csf.pignore on cPanel servers for cPanel EasyApache4
  • Modify Server Check to support cPanel EasyApache4
  • Added regex to support cPanel/WHM login failures with the new log format in v11.52+
  • If mod_ruid2 is enabled do not check for mod_userdir in Server Check
  • Always ensure binary exists and is executable before performing processing during Server Check
  • Modified ProFTPD regex to support more formats
  • vsftpd inbuilt log file format regex added
  • Modified cPanel antirelayd Server Check to also support popbeforesmtp added in v11.52
  • Added dbus and time systemd regexes to csf.logignore for new installs

New csf v8.05


  • Added alarms to HOST binary calls
  • Added new csf CLI option: –rbl [email]. This generates the report checking IP addresses against a set of RBLs. Optional configuration is available through /etc/csf/csf.rblconf
  • Added UI to utilise the new –rbl [email] option
  • Added systemd status output after lfd restart via the csf CLI
  • Modified Server Check to only report bind if a named configuration file exists
  • Require cPanel resellers to enter a Comment when allowing or denying an IP
  • Added new option UI_IP to allow binding to a specific IP address for the integrated UI

New cxs v5.31


  • Ensure only root can attempt to download the bayes corpus
  • Fixed POD reference to –bforget
  • Fixed POD formatting of long example commands
  • Updated Software Version Checking
  • Exploit regex definitions database additions
  • Exploit fingerprint definitions database additions

csf PT_USERKILL Recommendation

We wanted to reiterate the points made in the csf configuration and during csf restart regarding the PT_USERKILL option and the problems it can cause on servers as there appears to have been a spate of people enabling the option, which we do not recommend for stability reasons.

As csf itself now reports:

*WARNING* PT_USERKILL should not normally be enabled as it can easily 
lead to legitimate processes being terminated, use csf.pignore instead

And as stated in /etc/csf/csf.conf:

# Warning: We don't recommend enabling this option unless absolutely necessary
# as it can cause unexpected problems when processes are suddenly terminated.
# It can also lead to system processes being terminated which could cause
# stability issues. It is much better to leave this option disabled and to
# investigate each case as it is reported when the triggers above are breached