----------------------- Original Message -----------------------
From:    "steve" <securityfocus@delahunty.com>
To:      <security-basics@securityfocus.com>

Date:    Fri, 2 Jul 2004 14:39:29 -0400
Message-ID 038b01c46064$c8592ce0$b301a8c0@wdsdelahunty
Subject: recommended honeynet configuration

Have a project where we are able to set up a honeynet in order to learn from
the damage/results.  We have hardware and network connectivity apart from
our regular production network.  I think it would be interesting to maybe
set up a few machines on the honeynet, running various OSes and web servers
such as:
    Windows NT / IIS 4
    Windows 2000 / IIS 5
    Windows 2003 / IIS 6
    FreeBSD / Apache

I guess to make this a true honeynet we should do the base installs of each
OS and not patch them.  We need a firewall to restrict outbound but allow
inbound to the open ports.  We need to log events while keeping intruders
from knowing they are being monitored.  We need to analyze the data.

Is this the hardware above the right mix?  Should we have other services
running like SMTP and FTP?  Should we add other hardware like a router to be
exploited?  Has anyone run such a project and have recommendations / lessons
learned?  How to best save off the logs for review to determine impact? What
does the group think?

Here is an interesting presentation I found on the topic.

Ethical Hacking at the InfoSec Institute. Mention this ad and get $545 off
any course! All of our class sizes are guaranteed to be 10 students or less
to facilitate one-on-one interaction with one of our expert instructors.
Attend a course taught by an expert instructor with years of in-the-field
pen testing experience in our state of the art hacking lab. Master the skills
of an Ethical Hacker to better assess the security of your organization.
Visit us at:
--------------------- Original Message Ends --------------------

上のPPTファイルをローカルに保存しておくことに. ここ.

Honeypotsの本をねらってたところだったから, 興味がわいた.

0 件のコメント: