cancel
Showing results for 
Search instead for 
Did you mean: 

How to protect Contact Form from spam?

Sajid
Cirrostratus
Cirrostratus

Hi Guys,

 

Is there any solution from F5 to protect Contact Form from spam input?

 

I have tried ASM custom banned words, but it's not working.

 

any good solution?

 

Regards,

Sajid

1 ACCEPTED SOLUTION

Ivan_Chernenkii
F5 Employee
F5 Employee

You can use several approaches to protect it:

  1. As I said before, you can configure bot profile, to protect you application from bots.
  2. You can define appropriate parameter "name" in policy with some restrictions, like "Email" data type or aplha-numeric data type with maximum length (e.g. 50 characters) or with some regex rule or with some disallowed metacharacters
  3. You can create special valuecontent signature with special rule, which will match bad pattern

 

Thanks, Ivan

View solution in original post

3 REPLIES 3

Ivan_Chernenkii
F5 Employee
F5 Employee

Hello Sajid,

 

Could you provide any example of what you want to protect and from what inputs?

If you want to protect Form from input from bots, then you can use bot profile for you application, which was introduced in ASM starting from v13.0.0.

 

Thanks, Ivan

Sajid
Cirrostratus
Cirrostratus

Hi Ivan,

 

This kind of data getting from contact us form.

 

name=611__***ХОТИТЕ+ЗАРАБОТАТЬ+100000р.?+ЧИТАЙТЕ+ПОДРОБНОСТИ:+https://is.gd/JBvrvY++***__478&email=dmitrii.golub@mail.ru&contactnumber=249223&comment=544397&submit=?????

 

 

Regards,

Sajid

Ivan_Chernenkii
F5 Employee
F5 Employee

You can use several approaches to protect it:

  1. As I said before, you can configure bot profile, to protect you application from bots.
  2. You can define appropriate parameter "name" in policy with some restrictions, like "Email" data type or aplha-numeric data type with maximum length (e.g. 50 characters) or with some regex rule or with some disallowed metacharacters
  3. You can create special valuecontent signature with special rule, which will match bad pattern

 

Thanks, Ivan