Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Nmap Hackers: Re: Examples of legit nmap usage?

Re: Examples of legit nmap usage?

From: Bennett Todd <bet_at_mordor.net>
Date: Mon, 20 Sep 1999 18:32:21 -0400

1999-09-20-15:52:27 Andreas Kostyrka:
> [ a lengthy explanation of the deficiencies of the "hard outside, shoft
> chewy inside security design, with poor internal security and a firewall ]

I don't disagree with you; I sincerely hope that a combination of replacing
bad OSes with good ones, replacing bad apps with good ones, and using good
automation and management tools will make it possible to systematically harden
the inside to the point where we can toss the firewalls.

I don't defend the poor-internal-security design; I simply caution it exists.
The fact is, there are machines on in-house nets that nmap will crash. It's
not good that they exist. Keeping them around and unprotected where any
in-house user can crash them is not a good practice. Lobbying to improve
things is a good professional pursuit.

But doing unauthorized things (e.g. a big nmap scan) that goes out and crashes
them needlessly is a bad idea, particularly if people can figure out that it
was you who did it when they need someone to blame. The argument "they
shouldn't have left a crashable machine like that" won't impress management,
you'll still catch the blame, and the severity of the consequences will depend
more on who got inconvenienced and how badly than on what you did.

-Bennett
Received on Sep 20 1999

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]