Re: [Full-disclosure] New round of SSH scan IP's
- From: James Lay <jlay@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 09 Jul 2008 07:07:19 -0600
On 7/9/08 3:20 AM, "Peter van den Heuvel" <peter@xxxxxxxx> wrote:
its not quite the best way, human resource-wise,We've replaced the allow ssh access to all with an allow on a need
to get on top of these damn scanners :-|
basis. So most national IP-ranges, several foreign ones and some static
IPs are allowed. All the rest is bumped. We have no customers in China,
Korea, Russia, etc. It sure cut down on the number of scans we see.
We'll probably add rate limitation on top.
Client certificates would cut it down completely, but is more expensive
to implement. It would also require everybody to always carry a USB (or
something) with their cert.
I have a homebrew setup...using snort and syslog and an app called wots it
adds a firewall rule the first time something naughty happens. It's bee
pretty effective all in all. Last time I posted a list of IP's I had a net
admin contact me wanting more info since one of the IP's was one under his
responsibility. Glad I could assist :D
James
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
- Follow-Ups:
- Re: [Full-disclosure] New round of SSH scan IP's
- From: Knud Erik Højgaard
- Re: [Full-disclosure] New round of SSH scan IP's
- References:
- Re: [Full-disclosure] New round of SSH scan IP's
- From: Peter van den Heuvel
- Re: [Full-disclosure] New round of SSH scan IP's
- Prev by Date: [Full-disclosure] Trixbox 2.6.1 and below, remote root shell through local file inclusion
- Next by Date: [Full-disclosure] DNS and Checkpoint
- Previous by thread: Re: [Full-disclosure] New round of SSH scan IP's
- Next by thread: Re: [Full-disclosure] New round of SSH scan IP's
- Index(es):
Relevant Pages
|