Solved! Go to Solution.
It is not entirely true that you can't ban IP sources, albeit temporarily. In 5.3, we added SMTP authentication failure tracking. To configure: config system security authserver set status [enable, disable, monitor-only] end It uses a variety of adaptive factors, similar to our sender reputation feature to detect and block brute forcing (not just consecutive failures) and temporarily locks out (tarpitting) the user.
Carl
Dr. Carl Windsor
Chief Information Security Officer (CISO)
Fortinet
Hello Carl,
Thank you very much for your response, it's great news! I've just tested it in my lab, and it seams to be working just fine! :)))
However... :) Can you please point me to some documentation or something that would help me understand this feature better? Can I monitor it in the GUI (I already saw the 'diag system authserver scores')? Can I alter the timeout period? Stuff like that, which would help the end customer using this great feature.
Cheers,
Slavko
NSE 7
All oppinions/statements written here are my own.
PCNSE
NSE
StrongSwan
FWIW; I don' t think the ip/access-policy is where/what enables the SMTP-AUTH but you can check.
If you have a fortigate, I would write a SMTP-AUTH rule and block by tracking the server auth-failures and the destination address. This would give you a piece of mind and protection from any brute/dictionary or hybrid based attacks.
note: One more auth that can be disable in the same fashion is ;
config sys mailserver
set smtp-auth-smtps disable
end
I believe that take care of the SSMTP port 465;
cat services | grep smtp
smtp 25/tcp mail
ssmtp 465/tcp smtps # SMTP over SSL
Check and confirm by using mxtoolbox as outline in that blog.
PCNSE
NSE
StrongSwan
To revamp this post: what if I need SMTP authentication for my outside clients (people who are sending email from their mobile devices etc.), and disabling it is not an option?
NSE 7
All oppinions/statements written here are my own.
It is not entirely true that you can't ban IP sources, albeit temporarily. In 5.3, we added SMTP authentication failure tracking. To configure: config system security authserver set status [enable, disable, monitor-only] end It uses a variety of adaptive factors, similar to our sender reputation feature to detect and block brute forcing (not just consecutive failures) and temporarily locks out (tarpitting) the user.
Carl
Dr. Carl Windsor
Chief Information Security Officer (CISO)
Fortinet
Hello Carl,
Thank you very much for your response, it's great news! I've just tested it in my lab, and it seams to be working just fine! :)))
However... :) Can you please point me to some documentation or something that would help me understand this feature better? Can I monitor it in the GUI (I already saw the 'diag system authserver scores')? Can I alter the timeout period? Stuff like that, which would help the end customer using this great feature.
Cheers,
Slavko
NSE 7
All oppinions/statements written here are my own.
I would also like to get more information about this. Anyone know if or where Fortinet has a documentation?
In 5.3, we added SMTP authentication failure tracking.
FWIW; that feature would not be available in a FML100C model.
PCNSE
NSE
StrongSwan
| User | Count |
|---|---|
| 2677 | |
| 1412 | |
| 810 | |
| 703 | |
| 455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.