Audit
Apart from standard application logs, the system offers two types of logging:
- Audit Log
- Signature Audit
Audit Log
The solution components log data in a special database table.
Audit Types and Events
This chapter describes audit types and related events.
Activation events
- Initialization
- Created
- Approved
- State changed to PENDING_COMMIT/ACTIVE/BLOCKED
Authentication events
- Validation successful
- Validation failed
Operation events
- Created
- Approved
- Approval failed
- Rejected
- Reject Failed
- Operation failed
- Approval via server call failed
- Operation via server call failed
- Canceled via server call
FIDO2 events
- Stored authenticator
- Assertion result
Signature events
- Validation successful
- Validation failed
Stored data
The system stores the Subject ID (usually the User ID) and additional data, including error details (if available) and information about the system environment.
Audit is implemented using our own Wultra Auditing Library where you can find structure of the database table and all configuration options.
REST API
The system offers a REST API that allows you to list all the actions for a given user ID within a selected time range.
Documentation for REST API is available under Audit API.
Signature Audit
We have one extra database table “Signature Audit” that stores records with values used for attempts for the signature validation.
Signature Types
Each record contains information about the signature type, indicating which authentication factors were used during the signature validation attempt.
We support following signature types:
- POSSESSION
- POSSESSION_BIOMETRY
- POSSESSION_KNOWLEDGE
- POSSESSION_KNOWLEDGE_BIOMETRY
Stored data
The system stores additional data alongside the signature itself, such as related activation and signature metadata and body, including all parameters that were part of the signature.
Database table is described in Database Structure in PowerAuth Server component.