The shipping daemon will deliver the audit trails generated through the network to a master system, that will admin the trails to have the auditing centralized, ease to admin and practical. The admin will have all the trails in one system and can do the security auditing in one system (perhaps a special system to keep the auditing). Some mechanisms as MD5 checksum and cryptographic features will be implemented to guarantee the integrity of the delivery system.

Working Sergio Ligregni with the mentoring of Stacey Son

*May 24th - Jun 6th Code the shippd daemon and modify auditd to call it when a trail is finalized. *Jun 7th - Jun 27th Code the features of shipd daemon that will communicate with the master system, also, code the master daemon that will receive the files. In this phase, MD5 checksum will be implemented (as well as file listings comparison). *Jun 28th, Jul 4th Do the master work, this is, receive the files and perform the appropiate pathing, and the right naming (to prevent duplicates when errors occurs). *Jul 5th, Jul 16th Perform the mid-term prep testing *Jul 17th, Jul 31st Implement SSL in the network communication *Aug 1st, Aug 8th Perform the final testing. *Aug 9th, Aug 16th Document the tool.

DONE: *code the shipd daemon logical features:

1. it also gets the MD5 checksum for a trail.

Project's Perforce Repository

TO_DO: *code the shipd daemon network features. *code the master daemon to receive the trails.

TO_BE_DISCUSSED: *the changes to auditd daemon, maybe with audit_warn we have all the “signals” we want.