ACID: Managing Alert Databases (Purging and Archiving)
Purging (Deleting,Trimming) Alerts
The most obvious strategy to help mitigate the size of the Alert DB is simply to delete alerts. This action is quite appropriate and convenient when dealing with alerts that are false positives. Alerts can be deleting by following these steps:
From the left-most 'Action' combo-box choose 'Delete'.
The text-box following the combo-box should be left blank
Finally, the alerts which will be deleted need to be specified. This selection is achieved by choosing one of the three 'Action' buttons.
Archiving Alerts
Another strategy to shrink the size of the active database is to archive the already analyzed alerts into a separate database. In this manner, the "current" active database will remain manageable, but the already analyzed alerts are still preserved. Alerts can be archived by following these steps:
create_mysql/create_postgresql
script from the Snort distribution.
$archive_dbname, $archive_host, $archive_user, $archive_password, $archive_port
variables in the ACID configuration file acid_conf.php
to reference the archive database
From the left-most 'Action' combo-box choose 'Archive'. There are two types of archiving: "Archive -- copy", and "Archive -- move". The former action merely archives the specified alerts into the appropriate database, while the latter archives the alert into the alert database and then deletes these alerts from the current alert DB.
The text-box following the combo-box should be left blank
Finally, the alerts which will be archived need to be specified. This selection is achieved by choosing one of the three 'Action' buttons.