Difference between revisions of "Projects/Audit"

Revision as of 11:06, 2 October 2012

Purpose

The primary focus of this project will be on creating an Audit infrastructure within MIT Kerberos to monitor security related events on the KDC. The initial set of the audible events will be identified. Also, the special attention will be paid to the content of the log entries so they would be relevant and useful for effective audit analysis.

Requirements

The new audit system should be:

• build-time enabled;
• run-time pluggable;
• simple, so it could be easily replaced with the OS specific implementations;
• if possible, record the i18n- and l10n-ready log messages.

Events

This section details the list of the events, the content of the log entries and the level of the event (minimum, basic or detailed).

Each record must contain at least the timestamp of the event, the event id (type), and the status of the event (success or failure). Startup and shutdown of the audit system must be recorded by audit system.

Categories:

Audit plugin

loaded, unloaded;

KDC

started: stopped;

AS exchange

AS attempt (unsuccessful) and AS done (success):

TGS exchange

Successful or unsuccessful attempt and alternative TGS;

Secret

Session key generation and cleaning them up;

Policy

Policies violation when processing requests;

Design details

TODO

Test implementation

We will use libaudit module available on Fedora, Debian, Suse for the first round.

Some simple audit plugin will be implemented and Python test system will become aware of its existence. This would allow "make check" store audit messages into audit log file (if configuration was done with audit flag set).