Know Your Enemy: Honeynets

From: Lance Spitzner (lance@honeynet.org)
Date: 12/11/01 

Date: Tue, 11 Dec 2001 07:57:12 -0600 (CST)
From: Lance Spitzner <lance@honeynet.org>
To: Focus on Intrusion Detection Systems <FOCUS-IDS@SECURITYFOCUS.COM>

The Honeynet Project is excited to announce a highly
updated version of the paper "Know Your Enemy: Honeynets".
This paper describes what a Honeynet is, its value, how
it works, and the issues/risks invovled.

The Project has spent two months updating the paper to
include new technologies, documentation, configuration
files, and legal issues. The updated paper includes the
following:

 - Honeynet Definitions, Requirements, and Standards doc
 - Updated configuration files
 - Data Collection
 - GenII (2nd generation) technologies
 - Virtual Honeynets
 - Legal Issues

We recommend that individuals or organizations interested in
Honeynet technologies review the updated documentation.

  http://project.honeynet.org/papers/honeynet/

Thanks! 

-- 
Lance Spitzner
http://project.honeynet.org

Relevant Pages

  • REVIEW: "Know Your Enemy", Honeynet Project
    ... Second Edition: Learning About Security ... The first edition of "Know Your Enemy" was a lot of fun, ... more detailed information on the analytical aspects of honeynet ... my point, first, because the Honeynet Project members have not used ...
    (comp.security.misc)
  • REVIEW: "Know Your Enemy", Honeynet Project
    ... Second Edition: Learning About Security ... The first edition of "Know Your Enemy" was a lot of fun, ... more detailed information on the analytical aspects of honeynet ... my point, first, because the Honeynet Project members have not used ...
    (alt.computer.security)
  • Scan of the Month - October
    ... Hey all, ... The Honeynet Project is putting these on hold ... This list is provided by the SecurityFocus ARIS analyzer service. ...
    (Incidents)
  • Know Your Enemy: Honeynets
    ... The Honeynet Project is excited to announce a highly ... This paper describes what a Honeynet is, its value, how ... include new technologies, documentation, configuration ... - Updated configuration files ...
    (Incidents)