Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Incidents
[Top] [All Lists]

Re: RE: Internet SSH scans

Subject: Re: RE: Internet SSH scans
Date: 23 Mar 2006 09:01:08 -0000
*urgh* thats why things go terribly wrong. 

Security by obscurity isn't save, wasnt and will never be, if you just dont 
want the LogEntrys, exclude it from your Syslog.

if you want to secure your SSH Service, try following steps:

 - if possible, use a seperate LAN (MGMT) and bind 
    your Service to this LAN only.
    if theres no physical seperated LAN, build a 
    virtual seperated LAN (IPSec, ...)
 - disable the weakest Authentication (Password)
 - enforce your Authentication (RSA Keys) by 
    limiting the usage (man sshd, look for from=)
 - enforce better policy in SSHD config, limit 
    retrys, ... for my understanding it doesnt 
    make sence to lockout root. there are enought 
    exploits to gain root access anyway.
 - if you still want to limit the IP/TCP access to  
    SSH Service, do it on your Router infront of 
    the Machine.

there are no 15 bricks to stumble over  for allowed access, its transparent for 
upgrades, and its even more secure as theres no forgotten dependency.

my 5 cents
Greetz mIke

<Prev in Thread] Current Thread [Next in Thread>