Java-Based Collection Plug-in Security Considerations

Oracle strongly recommends that you review security guidelines before developing Java-based collection plug-ins.

For sources, such as databases, that require a connection in order to extract audit records, it is your responsibility, as the developer, to properly document the privileges needed to perform this task. Oracle recommends that the account used for connection have only the minimal privileges needed for the job. Any extra privileges can create a security issue.

You must also parse the input audit records properly, and protect Oracle Database Security Central (Oracle DBSecCentral) from malicious data. For instance, audit records can be crafted to inject SQL or HTML into the audit trail, which could expose data stored in Oracle DBSecCentral to attacks. You must ensure that all incoming audit data is sanitized properly before it is given to the Collection Framework.