-
Notifications
You must be signed in to change notification settings - Fork 4
Archive DB Information
Nathan Gibbs edited this page May 16, 2023
·
2 revisions
Alerts can be archived by following these steps:
- In preparation to archive alerts, a separate database must be created.
- This archive database must be the same schema version as the one from which alerts will be copied.
- Use the appropriate create_mysql/create_postgresql script from the Snort or Barnyard2 distribution.
- In the BASE configuration file
base_conf.php
.- Update the following to reference the Archive DB.
$archive_dbname
$archive_host
$archive_user
$archive_password
$archive_port
- Set '$archive_exists' to 1.
- Update the following to reference the Archive DB.
- Run the query which contains the alerts to be archived.
- At the bottom of the query results will be an 'Action' box.
- From the left-most 'Action' combo-box choose an Archive action.
- Archive alert(s) (copy) - Copy the specified alerts into the archive DB.
- Archive alert(s) (move) - Copy the specified alerts into the archive DB, then delete the alerts from the alert DB.
- The text-box following the combo-box should be left blank
- The alerts which will be archived need to be specified.
- This selection is achieved by choosing one of the three 'Action' buttons.
- Selected: archives those alerts which have been checked (note the check boxes in the extreme left-hand column)
- ALL on Screen: archives all alerts currently displayed on the screen
- Entire Query: archives all alerts in this query/report
- This selection is achieved by choosing one of the three 'Action' buttons.
Adapted from: https://acidlab.sourceforge.net/acid_archive_instruct.html & https://www.andrew.cmu.edu/user/rdanyliw/snort/acid_archive_instruct.html