### Honeynet Definitions, Requirements, and Standards ###
ver 1.4.5
Updated: 4 February, 2002
PURPOSE:
--------
The purpose of this document is to state the definitions, requirements
and standards for a Honeynet. This will allow various organizations to
independently research, develop, and deploy their own Honeynets using
the same guidelines. For more information on what a Honeynet is, how it
works, and its value to information security, (and current copy of this
document) refer to
http://project.honeynet.org/papers/honeynet/
DEFINITIONS:
------------
The goal of a Honeynet is to create an environment where the tools and
behavior of blackhats can be captured and analyzed in the wild. Based
on this information, we can gain intelligence on threats faced by the
Internet community. A Honeynet works by creating a highly controlled
environment that is probed, attacked, and compromised by blackhats. To
create this highly controlled environment, two requirements must be met.
I. Data Control:
Once a honeypot within the Honeynet is compromised, we have
to contain the activity and ensure the honeypots are not used
to harm non Honeynet systems. There must be some means of
controlling how traffic can flow in and out of the Honeynet,
without blackhats detecting control activities.
II. Data Capture:
Capture all activity within the Honeynet and the information
that enters and leaves the Honeynet, without blackhats knowing
they are being watched.
If the Honeynet is part of a distributed environment, then
that Honeynet must meet the third requirement of Data Collection.
III. Data Collection
Once data is captured, it is securely forwarded to a centralized
data collection point. This allows data captured from numerous
Honeynet sensors to be centrally collected for analysis and
archiving.
REQUIREMENTS:
-------------
I. Data Control
This defines the specific requirements for data control.
a. Must have both automated and manual data control.
In other words, data control can be implemented via an
automated response or manual intervention.
b. At least two layers of data control to protect
against failure.
c. Be able to maintain state of all inbound and outbound
connections.
d. Be able to control any unauthorized activity. Unauthorized
activity is defined by the policy of the Honeynet
administrator. This implies some type of control to ensure
non Honeynet systems are not harmed.
e. Data Control enforcement must be must be configurable by the
administrator at any time.
f. Control connections in a manner as difficult as possible to
be detected by attackers.
g. At least two methods of alerting for activity, such as
when honeypots are compromised.
h. Remote administration of the data control.
II. Data Capture
This defines the specific requirements for data capture.
a. No Honeynet captured data will be stored locally on the
honeypot. (Data logged on honeypots is assumed to be unreliable,
and may be modified by intruders.) Honeynet captured data is any
logging or information capture associated with activity within a
Honeynet environment.
b. No data pollution can contaminate the Honeynet, invalidating
data capture. Data pollution is any activity that is non-standard
to the environment. An example would be a non blackhat testing a tool
by attacking a honeypot.
c. The following activity must be captured and archived for one year.
- Network Activity
- System Activity
- Application Activity
- User Activity
d. The ability to remotely view this activity in real time.
e. The automated archiving of this data for future analysis.
f. Maintain a standardized log of every honeypot deployed.
Refer to Appendix A (Honeypot Deployment) for template.
g. Maintain a standardized, detailed write-up of every honeypot
compromised. Refer to Appendix B (Honeypot Compromise) for
template.
h. Honeynet sensors' data capture must use the GMT time zone. Individual
honeypots may use local time zones, but data will have to be later converted
to GMT for analysis purposes.
i. Resources used to capture data must be secured against compromise
to protect the integrity of the data.
III. Data Collection
If the Honeynet is to be part of a distributed network, then the
following requirements must be met.
a. Honeynet naming convention and mapping so that the type
of site and a unique identifier is maintained for each
honeypot. This implies some kind of IP/DNS mapping
database.
b. A means for transmitting this captured data from sensors
to the collector in a secure fashion, ensuring the
confidentiality, integrity, and authenticity of the
data.
c. Organizations have the option of anonymizing the data.
This does not mean to anonymize the data of the attacker,
rather it gives the source organization the option of
anonymizing their source IP addresses or other information
they feel is confidential to their organization.
d. Distributed Honeynets are expected to standardize on NTP,
ensuring all Honeynet data capture is properly synched.
STANDARDS:
----------
The following standards apply to Data Capture and Data Collection. All
documentation will be done in either .txt or .html format.
NOTE: The Standards section is considered incomplete and under development.
The Honeynet Project has not yet determined what best practices are for
data capture/collection. What we have below is the current, minimum
standard.
I. Data Capture Standards
--------------------------
The following are standards for data capture. This is what data
and in what format should be captured at each Honeynet. This is
a minimum. It is expected that more forms of data then discussed
below can and will be captured.
a. All network activity must be captured in tcpdump binary format (OpenBSD
libpcap standards) and rotated/compressed (zip/gzip) on a daily basis.
The log will be named with the year-month-date.
snort-01-11-20.tar.gz
b. Network Intrusion Detection alerts will be in Snort 1.8.x Full
format.
c. Every newly initiated connection must be logged and archived in
the following tab delimited format. All ports must be in
numeric value.
(yy/mm/dd) (military time) (src IP) (dst IP) (protocol) (src port ) (dst port )
(icmp_type) (icmp_code)
d. Every new unique connection attempt in a 24 hr period must be logged
to a separate source, this is critical for trend analysis. Unique
connection is defined as a unique (different) source IP address.
All ports must be numeric value.
(yy/mm/dd) (military time) (src IP) (dst IP) (protocol) (src port ) (dst port )
(icmp_type) (icmp_code)
II. Data Collection Standards
-----------------------------
The following are standards for data collection. This is what data
and in what format data should be sent to a central collection point.
These standards define what format or naming convention will be used for
data when sent to the central collection site.
Every organization and their Honeynets will be given a unique identifier.
This identifier will be used to identify all data sent to a central data.
For the purposes of this document, we will call this ID (identifier).
There are currently six types of Honeynet data that can be
automatically forwarded to central point.
Snort Alerts, Full -> MySQL database - real time
Snort Alerts, Full -> ASCII text - daily
Snort Alerts, Fast -> ASCII text - daily
Snort binary log, Full -> snort.log - daily
Firewall logs, Full -> ASCII text - daily
Firewall logs, Unique -> ASCII text - daily
a. Snort Alerts, Full, MySQL database
Each Honeynet can forwarded in real time all alerts via MySQL
functionality. The central collection point will have an active
MySQL database for Alert collection and archiving which can then
be queried.
output database: log, mysql, user=(user_name) password=(passwd) dbname=snort host=db.honeynet.org sensor_name=identifier) detail=fast
b. Snort Alerts, Full, ASCII
Each Honeynet can forward daily Snort Full Alerts that are in ASCII format.
Use the following naming convention. The logs will then be rotated and
archived every month.
(identifier).snort-full-alerts-yy-mm.txt
c. Snort Alerts, Fast, ASCII.txt
Each Honeyent can forward daily Snort Fast Alerts that are in ASCII format.
Use the following naming convention. The logs will then be rotated and
archived every month.
(identifier).snort-fast-alerts-yy-mm.txt
d. Snort binary logs
Each Honeynet can forward dialy Snort binary log captures with the
following naming convention.
(identifier).snort-yy-mm-dd.tar.gz
e. Firewall logs, Full
Every inbound connection logged by the firewall can be sent in ASCII
text format on a daily basis. Use the following naming convention.
The logs will then be rotated and archived evry day.
(identifier).fw-full-inbound-yy-mm-dd.txt
f. Firewall logs, Unique
All unique inbound connections can be sent in ASCII text format on
a daily basis. Use the following naming convention. The logs will
then be rotated and archived very day.
(identifier).fw-unique-inbound-yy-mm-dd.txt
g. For all ssh communications, only ver2 is accepted using DSA
keys for authentication.
Appendix A: Honeypot Deployment
Appendix B: Honeypot Compromise
All comments, suggestions, or corrections should be sent to
project@honeynet.org.
--- The Honeynet Project