|
| Change Aanval path settings Aanval uses a standard php based configuration file to store console path and required database credentials. Aanval database and path information is stored at the following location: /path/to/aanval/conf/conf.php * Please use caution when editing this file, and only change settings you are familiar with. Reset "root" Aanval account password Resetting a lost or forgotten password manually through MySQL. If you have forgotten or lost the Aanval console's root account password, you may perform the following MySQL query to reset the password to the installation default (usually "specter"). Aanval 4 (the root user id is always 102) MySQL Query: "UPDATE idsUsers SET password = MD5('specter') WHERE id = '102';" Aanval 5 (the root user id is always 1) MySQL Query: "UPDATE idsUsers SET password = MD5('specter') WHERE id = '1';" * Note: You may use this on any account, provided you use the correct user id value. Default username and password for Aanval Aanval's default username and password is: Username: "root" Password: "specter" As always, we recommend this be changed immediately upon installation to prevent unauthorized access. Timezone configuration Timezone settings within Aanval are critical to the operation and display of system details and event data. In order for Aanval to function properly and provide meaningful results, the current timezone setting for the console, each user and each sensor must be correctly configured to reflect their appropriate timezone. Console Time The Aanval Console's timezone setting can be found within the System Manager and should reflect the timezone of the operating system in which the console is installed. User Time The user timezone setting can be found within each user account and should reflect the timezone of the users physical location. Sensor Time The sensor timezone setting can be found within the sensor edit feature of the appropriate Module Manager and should reflect the timezone setting of the sensors operating system. Timezone problems are very common, and many times can be resolved quickly by ensuring proper configuration within the console. First verify the correct timezone settings for console, user and sensor match their respecting operating system and physical environments. If no configuration problems are identified, ensure the console is logging and displaying the appropriate time / date by checking the timestamp if new entries in the Logs Manager. If you continue to have timezone problems after these checks, please contact your support staff or use the support forum for assistance. Snort Database and Sensor Configuration Logos and trademarks are property of their respective owners. |
