FAQ

What is Audit4j?

Audit4j is comprehensive auditing framework which is designed to track any kind of audit event including server, application and database. Audit4j is entirely annotation driven, hence you can adopt to your application using minimum configurations.

What Open Source License Agreement is Audit4j published under?

Audit4j is licensed under the liberal and business-friendly Apache Licence, Version 2.0 and is freely available on GitHub. This license is applicable for Audit4j Core, plugins and all the integrations.

What is different between Audit trace and Log?

A log is often unpreserved whereas; an audit trace is secure and preservable. As a result, recording sensitive information, or data which will be required at a later time will not be handled by a log. Other issue is usually logs are not recording actor(Who did), action(What did) and origin(Comes from), but audit log should contains those information. However, an audit trace addresses these issues.

What are the main features of Audit4j?

1. Asynchronous.
2. Very high performance.
3. Fully customizable annotations.
4. In-built plugins (File and Console).
5. Auto archive (Files only).
6. De-Identification.
7. Minimum configurations.
8. Customizable audit log format.
9. Encrypted audit trails.
10. Supports for Java, Scala and Groovy.
11. Rich extendible API – Custom/third party plugins can be implemented by via the API.

How is the performance after integrating the Audit4J with my application?

Audit4J supports asynchronous events. Since the architecture is based on asynchronous event mechanism, application will not be added additional latency (or less than 0.5 micro seconds.) after integrating the audit4j and its plugins. You can measure it by yourself with the Audit4j Benchmark projects.

How does the Audit4j architecture work?

Audit4J is entirely based on a modular architecture. There are three different types of plugins that support connecting various types of external tools with the core module.

1. Caller Plugins – Sending audit events from various sources.
2. Layout Plugins – Format and organize audit events.
3. Handler Plugins – Process and save audit information.
3. Filters – Filter audit events.

The javadoc api can be referred in order to obtain further information regarding this.

Currently, what are the available integrations for Audit4j?

1. Audit4j-Spring Integration.
2. Audit4j for CDI specification implementations.
3. Audit4j HTTP.
4. Audit4j integration for Tomcat Jboss and Wildfly. beeta
5. Audit4j integration for Oracle Glassfish. beeta
6. Audit4j integration for Jetty. beeta
7. Audit4j integration for JDBC. beeta