DETER SEER Wiki

The Security Experimentation EnviRonment (SEER) is a set of tools and agents for helping an experimenter setup, script and perform experiments in the DETER environment. It includes agents for traffic generation, attack generation, traffic collection and analysis. SEER provides:

  • an extensible Java GUI interface
  • a module system for adding your own agents, collectors, aggregators or services
  • a module/software dependency setup with building and caching of 3rd party software

 Launch SEER Now

Requires Java,  Get it here

HOWTO

 HOWTO Setup An Experiment With SEER

About

SEER makes extensive use of other great open source software including:

Software

Beta 5 adds jython support and finalizes some interfaces for extending the GUI from jars in the experiment and restores support for the WINXP-UPDATE image

Beta 4 releases other agents from 1.5 such as IRC, Perf analysis, etc, some new context help for the controls and a fix for the SSL issues

Beta 3 fixes some backend bugs and offers some logging options in the GUI to help with SSL debugging, enabled Geo module in GUI

Beta 2 fixes setup on FreeBSD machines and updated control types for agent definitions

There are two software components to the SEER tools. The desktop GUI and the backend that is extracted on experiment nodes. The backend setup script is found on the DETER fileserver at /share/seer/v160/experiment-setup.py. It requires at least one module or group name argument so that some functionality is loaded.

The current development tree can be cloned from:

Access for writing is restricted to those with SSH access. If you wish to submit a patch you can do so using git facilities.

Documentation

GUI - Webstart

Supported OS Images

SEER should run on any image listed as officially supported at  https://www.isi.deterlab.net/showosid_list.php3 with some minor exceptions such as servers that won't run on Windows machines. It may also run on other images but minimal support will be given. On non supported images, the setup process may take longer and some software may fail to build which should be displayed in the ExpInfo tab. If this software includes m2crypto then the GUI will still be able to connect to DETER, but not the experiment itself and you must look in /local/logs on the control node to see what failed.

Help