Final report for tiger team project (and related testing).
----------------------------------------------------------

This is due (final day) by noon.    It should be emailed to
the instructor as a PDF file.  .doc files will be ignored.
The final report should be due to team collaboration.
One person of course might be the editor.  It should
be submitted by the team captain and mailed to:

binkley.jim@gmail.com

This document should be 5-10 pages in length, and
should not be longer than 10 pages in any case.

The report should have the following parts:

1. attacks 
2. hardening and defensive measures/tools
3. forensics if necessary 
4. what work each team member did.

In addition, if you feel that a member of your team did NOT
hold up his or her end of the bargain, please send the instructor
private email and tell him about it.  Also please note
section #4 above.

More details:

1. attacks.  In this section summarize the attacks you observed,
and the attacks you made.  If you feel you did a good job making
some attack, please explain the attack, and where it succeeded.
If you observed attacks, please state what you observed and how
you think the attacks were made.

2. defensive measures/tool.  Please explain the tools you installed
or measures you took that helped you defend and
monitor what was going on from both the network
and host points of view.  Focus on what you believe was actually
useful.

3. if your tiger team was hacked, or DOS'ed, (and you knew it ...), please
briefly explain how you were hacked (or DOS'ed) and what if anything
you did about it.  If you already sent in a longer form of this,
please briefly summarize the longer form here.  If as far as you
know you were not hacked or DOS'ed, then say so (this section will be
easy).

4. for each member of your tiger team, briefly summarize their
contribution/s to the project.