I was getting blasted with SPAM through website forms, despite having Captchas in place and other security measures. I was able to analyze the log files over the course of a month and found that the vast majority of form submission SPAM was coming from just 3 ASN.
I blocked these 3 ASN in CC_DENY after extensive research:
AS36352 ColoCrossing
AS55286 Server Mania
AS60068 Datacamp
Luckily after adding those 3 ASN to CC_DENY literally every single web form SPAM stopped. However, a bigger problem developed in that WHM will no longer update. It hangs up trying to update packages. My guess is one of the above ASN hosts some type of updates for WHM.
I asked my managed provider for a solution but nothing really helped. I'm looking for some way to keep my CC_DENY entry while somehow bypassing it just for ports, and I'd need some kind of idea what ports are used for WHM updates. Any idea how I can keep my block in place but CSF whitelist WHM updates?
I blocked these 3 ASN in CC_DENY after extensive research:
AS36352 ColoCrossing
AS55286 Server Mania
AS60068 Datacamp
Luckily after adding those 3 ASN to CC_DENY literally every single web form SPAM stopped. However, a bigger problem developed in that WHM will no longer update. It hangs up trying to update packages. My guess is one of the above ASN hosts some type of updates for WHM.
I asked my managed provider for a solution but nothing really helped. I'm looking for some way to keep my CC_DENY entry while somehow bypassing it just for ports, and I'd need some kind of idea what ports are used for WHM updates. Any idea how I can keep my block in place but CSF whitelist WHM updates?