Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
mehdi_ouazaa
New Contributor II

Multiple ssh auth with different username

Hi all,

 

On systems events I discovered that there is a lot of ssh auth failed attempts with different usernames and from different ips from all over the world. for me it smells like some one/script is trying to access my fortgate.

 

Could you please advice on better actions to take

1 Solution
emnoc
Esteemed Contributor III

you have a few items to lookat

 

ssh-pub-key ( just build a strong password  but enforce the ssh pub key )

http://socpuppet.blogspot...ess-login-fortios.html

 

GEOIP block the  external interface ( e.g I use a local-in policy and block any thing outside of the USA )

https://forum.fortinet.com/tm.aspx?m=136899

 

change the SSH ports

http://socpuppet.blogspot.com/2014/12/hardening-your-unix-ssh-server-access.html

 

disable  ssh on the wan and force your admins to  sshin and then use  allowaccess ssh in the ssl.root interface

http://socpuppet.blogspot.com/2015/03/sslvpn-sslroot-management-access.html

 

Or use a MFA access for any admins, this would be the best along with the aboves.

 

 

Ken

 

PCNSE 

NSE 

StrongSwan  

View solution in original post

PCNSE NSE StrongSwan
6 REPLIES 6
mhe
Contributor II

Why don't you disable SSH on the external interface??

xsilver_FTNT
Staff
Staff

If it's not super critical then disable SSH from outside as mhe mentioned.

If not possible then change default port to some other less obvious/predictable.

You can also utilize trusted hosts so SSH will not respond to anyone outside allowed ranges/IPs.

 

And obviously, have strong passwords for admins.

Tomas Stribrny - NASDAQ:FTNT - Fortinet Inc. - TAC Staff Engineer
AAA, MFA, VoIP and other Fortinet stuff

emnoc
Esteemed Contributor III

you have a few items to lookat

 

ssh-pub-key ( just build a strong password  but enforce the ssh pub key )

http://socpuppet.blogspot...ess-login-fortios.html

 

GEOIP block the  external interface ( e.g I use a local-in policy and block any thing outside of the USA )

https://forum.fortinet.com/tm.aspx?m=136899

 

change the SSH ports

http://socpuppet.blogspot.com/2014/12/hardening-your-unix-ssh-server-access.html

 

disable  ssh on the wan and force your admins to  sshin and then use  allowaccess ssh in the ssl.root interface

http://socpuppet.blogspot.com/2015/03/sslvpn-sslroot-management-access.html

 

Or use a MFA access for any admins, this would be the best along with the aboves.

 

 

Ken

 

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
mehdi_ouazaa
New Contributor II

Thank you guys,

 

I will think to all of this and tell you what I've done

Toshi_Esumi

One last thing in addition to above: use trusthosts to limit the access to certain trusted ranges of IPs.

emnoc
Esteemed Contributor III

Keep in mind the trusthost will not change the port22 being exposed to the internet.

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors