09-08-2014 12:45 AM
Hello
Could someone explain me why signature FTP evasion attack (id:30401) was disabled in thread update version 453?
This signature wasn't replaced by new one. Bruteforce attacs on FTP serwers still exist and nothing will change in this case.
With regards
SLawek
09-08-2014 06:31 AM
Hello Slv,
Content version 453, which was shipped on 9/3/2014, contained an erroneous entry. The last entry indicated that Threat ID 30401, "FTP Evasion Attack" had been disabled, when in fact no changes were made to this signature as part of content release 453. Please find below a KB article for the same: Release Notes Error for Content 453
Severity | ID | Attack Name | CVE ID | Vendor ID | Default Action | Minimum PAN-OS Version |
---|---|---|---|---|---|---|
critical | 30401 | FTP evasion attack | alert | 3.1.0 |
Hope this helps.
Thanks
09-08-2014 01:05 AM
Some update... there is another one signature "FTP: login Brute-force attempt id:40001", so 30401 was for different purposes.
09-08-2014 06:31 AM
Hello Slv,
Content version 453, which was shipped on 9/3/2014, contained an erroneous entry. The last entry indicated that Threat ID 30401, "FTP Evasion Attack" had been disabled, when in fact no changes were made to this signature as part of content release 453. Please find below a KB article for the same: Release Notes Error for Content 453
Severity | ID | Attack Name | CVE ID | Vendor ID | Default Action | Minimum PAN-OS Version |
---|---|---|---|---|---|---|
critical | 30401 | FTP evasion attack | alert | 3.1.0 |
Hope this helps.
Thanks
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!