ssfinney / honeypot-analyzer Goto Github PK

We need to make a select dropdown for choosing a log to display.

We need to set up a basic Django web app.

This can be done using Devise.

Screencast for Devise: http://railscasts.com/episodes/209-introducing-devise

The routing is not optimal for the site or the POST requests.

On the Log index view, we need a table with pagination, searching, and sorting capabilities.

I'll try to use DataTables for this since it's built for rails and seems simple enough to implement.

Screencasts for this: http://railscasts.com/episodes/340-datatables

We can also use Twitter Bootstrap to style this table later: http://moorberry.net/blog/datatables-twitter-bootstrap-pagination

Import Twitter Bootstrap into the rails app and begin styling what we have so far.

Our analytics need to be defined and implemented.

Do we want just pie/bar charts and a map for the geolocation? Do we want anything more? We should decide this ASAP.

I'll be working on getting our code to work with the GeoLite database.

A couple options for our implementations could include Google Charts. Here is a blog post about it.

Log entries should be geo-located by IP address for country, city, organization, etc. We'll use GeoCity for this. Download the database and then join it with ours.

Since we're now using a regular SQL database, let's modify the Python code (again) to send data over to the Rails app to be inserted. The change will be minimal since we'll send it over a RESTful URL.

Then, update the Rails app to receive and process these inserts.

The show action in the users controller prevents the user from logging out.

We need a plan for the documentation on this thing.

We can do Python docs for the code, methods, variables, etc but we need a larger plan for the analysis & design documents to turn in for the class.

When the user reaches a page that's not found, he should get a 404 page instead of a Rails exception. This should apply for 500 and other responses too.

Railscast: http://railscasts.com/episodes/53-handling-exceptions-revised

Find out what inputs (if any) need to be sanitized by Rails or by our Python code. I think Rails does most of this, but we should be sure that ActiveRecord will do this for us before going live.

The app should handle an active HoneyD instance updating a single log file on demand.

The app should handle multiple log files for a single user (or server) and parse them one-by-one until finished.