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 FullDisclosure
[Top] [All Lists]

Re: [Full-Disclosure] Top 15 Reasons Why Admins Use Security Scan ners

Subject: Re: [Full-Disclosure] Top 15 Reasons Why Admins Use Security Scan ners
Date: Wed, 28 Apr 2004 19:40:34 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 28 April 2004 14:25, Stuart Fox (DSL AK) wrote:
And some more things for you to think about

Just some things to think about...

Top 15 Reasons Why Admins Use Security Scanners

Question: Should admins be using security scanners?

Someone should be.  Admins should be to confirm that their environment is
in the state that they believe it to be.

Yes!

I look at software development for an analogy.
Just because developers should not be tasked with maintaining metrics and 
configurations for validating QA targets, it does not follow that they 
shouldn't 'smoke-test' or perform individual unit checks against the derived 
objects of code they are about to commit.  It would be irresponsible /not/ to 
check...

But having done so, development is not entitled to the claim that the code is 
defect free, and meets all requirements.  The independent validation and 
measurement is still requisite.  So Admins can claim "due care" - without 
asserting policy compliance or eliminating audit requirements. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAkGsiJi2cv3XsiSARAuR+AKDMbGGSFsbovcoSijaJjmRp4EVnHACgkOwT
qRyyjk6MfJwirJlESookl90=
=qf2F
-----END PGP SIGNATURE-----


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