
reinke at e-softinc
Aug 24, 2001, 10:25 AM
Post #3 of 6
(252 views)
Permalink
|
This has been hashed through the list a number of times. There are any number of good reasons why this should not be done. The key one is that you get a limited saving of time by doing this, and you weaken the vulnerability test, because you cannot ensure that you have profiled the target properly. The question you have to ask yourself is: how do I KNOW for a FACT that the server is a Microsoft server? By it's TCP/IP fingerprint? That can be faked. By a web server signature? That can be faked. By what was there last time you ran the audit? That can be changed. While it is possible, I would avoid going there. It adds little real value (IMHO), and it introduces the opportunity to miss holes. So, ultimately: ask yourself what problem you are trying to solve by doing this, and then ask if the trade-offs are worth it? Thomas quentyn [at] fotango wrote: > > Bruno FAVRE wrote: > > > > Is there a way to define a target profile ? > > For exemple, when I test a web server, that I know is a microsft one, I > > enabled only certain plugins. > > But if it is an Apache, I have to enable some others. > > So i'd like to define, somewhere (?), the plugins that have to be > > enabled for the test of M$ IIs, the ones for Apache, the ones for a ftp > > server, and so on ...? > > > > Is it possible ? > > > > I think it could take the form of a .nasl plugin that make calls to the > > real plugins ... > > > > Any idea would be appreciate ! > > > > Thx > > Bruno. > > I was thinking about this was well > > it would save time when you are trying to repeatedly test servers after > config changes ( differing types) > > -- > ##################### > Quentyn Taylor > Sysadmin - Fotango > ##################### > xenaphobia: The fear of being beaten to a pulp by a leather-clad, New > Zealand woman. -- ------------------------------------------------------------ Thomas Reinke Tel: (905) 331-2260 Director of Technology Fax: (905) 331-2504 E-Soft Inc. http://www.e-softinc.com Publishers of SecuritySpace http://www.securityspace.com
|