Moving a Target from One Host Machine to Another

Learn how to handle when a target is moved from one host machine to another.

There are a few changes to be made in Oracle Database Security Central console when a target is moved from one host machine to another. This depends on the type of the Audit Vault Agent.

An Audit Vault Agent can be of two types:

1. When the Audit Vault Agent is installed on the target host machine, it is called as a local Agent.

2. When the Audit Vault Agent is not installed on the target host machine and is installed remotely, it is called as a remote Agent.

Local Agent, Table Trails, and Oracle Database, Oracle Key Vault Targets

1. Update the target Connection Details by following these steps:

   1. Log in to the Oracle Database Security Central console as an administrator.

   2. Select Targets. The Targets in the left navigation menu is selected by default.

   3. Select and select specific target.

   4. In the Database Firewall Monitoring section on the main page, select to modify the connection details. The Database Firewall Monitor dialog is displayed.

   5. Modify and update the Connection Details in the dialog.

   6. Select Save.

   7. Select Save in the main page.

2. Delete existing trail by following these steps:

   1. Select Targets.

   2. Select Audit Trails in the left navigational menu.

   3. Select the specific audit trail and select Stop.

   4. Select Delete.

3. Create a new trail and configure the Audit Vault Agent installed on the new host machine. Refer to Adding Audit Trails with Agent-Based Collection

Local agent, Non-table trail types, and Oracle Database target type

Trail types:

• DIRECTORY

• SYSLOG

• EVENT LOG

• TRANSACTION LOG

1. Update the target Connection Details.

2. Delete the existing trail.

3. Create a new trail by configuring the Audit Vault Agent installed on the new host machine and using the new trail location of the new host machine.

Local agent, Non-table trail types, and Non-Oracle Database Target types

Trail types:

• DIRECTORY

• SYSLOG

• EVENT LOG

• TRANSACTION LOG

Target Types:

• MySQL

• Microsoft SQL Server

• PostgreSQL

• IBM DB2

• Quick JSON

• Oracle Solaris

• Linux

• IBM AIX

• Microsoft Windows

• Microsoft Active Directory

1. Delete the existing trail.

2. Create a new trail by configuring the Audit Vault Agent installed on the new host machine and using the new trail location of the new host machine.

Local agent and Network trail

Target Types:

• Oracle Database

• MySQL

• Microsoft SQL Server

• IBM DB2

1. Delete the existing trail.

2. Create a new trail by configuring the Audit Vault Agent installed on the new host machine.

Remote agent, Table trail, and Oracle Database; Oracle Key Vault target types

1. Update the target Connection Details.

2. There is no need to delete and recreate the trails. Stop the existing trail.

3. Start the trail.

Remote agent, Non-table trail, and Oracle Database target type

Trail types:

• DIRECTORY

• SYSLOG

• EVENT LOG

• TRANSACTION LOG

1. Update the target Connection Details.

2. In case the trail location has changed, then delete the existing trail.

3. Create a new trail and specify the new trail location.

Remote agent, Non-table trail, and Non-Oracle Database trail types

Trail types:

• DIRECTORY

• SYSLOG

• EVENT LOG

• TRANSACTION LOG

Target Types:

• MySQL

• Microsoft SQL Server

• PostgreSQL

• IBM DB2

• Quick JSON

• Oracle Solaris

• Linux

• IBM AIX

• Microsoft Windows

• Microsoft Active Directory

1. In case the trail location has changed, then delete the existing trail.

2. Create a new trail and specify the new trail location.

Related Topics

• Behavior Changes, Deprecated, and Desupported Platforms and Features