Security Considerations for Custom Collector Development
Learn about security considerations for Custom Collector Development.
Custom Collector Development
Learn about custom collector development.
Note the following if you develop custom collectors:
-
Prevent resource leaks. Ensure that JDBC resources are closed appropriately. These resources include the connections, result sets, and statements.
-
Prevent data loss. Ensure that your audit data is purged from the target system only after it has been successfully collected by the custom collector.
-
Avoid frequent queries to the target system.
-
Ensure that the custom collector does not consume a lot of system resources such as CPU and memory on the target host.
-
Avoid logging audit data because the audit records contain sensitive information.
-
Grant only the required privileges on the target system to users who have access to the Agent.
-
Ensure that only necessary files are added to custom collector
.jarfile. -
Ensure that your custom collector code collects the audit data from your target system securely.
Note: The collection framework ensures that audit data is transferred from the collector to Oracle Audit Vault Server securely.