Go Up
You are here: AdministrationSettingsInvestigations

Investigations

By default, the Audit Database stores data up to 180 days. Once the retention period is over, the data is deleted from the Audit Database and becomes unavailable for reporting and search.

Depending on your company requirements you may need to investigate past incidents and browse old data stored in the Long-Term Archive. Netwrix Auditor allows importing data from the Long-Term Archive to a special "investigation" database. Having imported data there, you can run searches and generate reports with your past data.

To import audit data with the Archive Data Investigation wizard

NOTE: You must be assigned the Global administrator role to import investigation data. To view investigation data, you must be assigned the Global administrator or Global reviewer role.

  1. Navigate to Settings Investigations.
  2. Complete your SQL Server settings.

    Option Description

    SQL Server Instance

    Specify the name of the SQL Server instance to import your audit data to.

    NOTE: If you want to run searches and generate reports, select the same SQL Server instance as the one specified on Settings Audit Database page. See Audit Database for more information.

    Database

    Select import database name. By default, data is imported to a specially created the Netwrix_ImportDB database but you can select any other.

    NOTE: Do not select databases that already contain data. Selecting such databases leads to data overwrites and loss.

    Authentication

    Select the authentication type you want to use to connect to the SQL Server instance:

    • Windows authentication
    • SQL Server authentication

    User name

    Specify the account to be used to connect to the SQL Server instance.

    NOTE: This account must be granted the database owner (db_owner) role and the dbcreator server role. See Configure Audit Database Account for more information.

    Password

    Enter a password.

    Clear imported data

    Select to delete all previously imported data.

    NOTE: To prevent SQL Server from overfilling, it is recommended to clear imported data once it is longer needed.

  3. Review your New investigation configuration. Click Configure to specify the import scope.

    Option Description

    From... To...

    Specify the time range for which you want to import past audit data.

    Data sources

    Select data sources whose audit data you want to import to the Audit Database.

    Monitoring plans

    Select monitoring plans whose audit data you want to import to the Audit Database. Netwrix Auditor lists monitoring plans that are currently available in the product configuration.

    NOTE: Select All to import audit data for all monitoring plans, including those that were removed from the product (or removed and then recreated with the same name—Netwrix Auditor treats them as different monitoring plans).

    For example, you had a monitoring plan corp.local used for auditing Active Directory. You removed this monitoring plan, but its audit data was preserved in the Long-Term Archive. Then, you created a new monitoring plan for auditing Exchange and named it corp.local again. Its data is also stored in the Long-Term Archive. Netwrix Auditor treats both corp.local monitoring plans—the removed and the current—as different.

    If you select corp.local in the monitoring plans list, only Exchange data will be imported to Audit Database (as it corresponds to the current monitoring plan configuration). To import Active Directory data from the removed monitoring plan, select All monitoring plans.

  4. Click Run.

Go Up