Security / Audit trail
Every sensitive action produces an audit event
The audit trail is a first-class part of the data model. It is written by the same server code that performs the action, so it cannot be bypassed by the interface.
Audit event structure
| Field | Description |
|---|---|
| timestamp | Server time the action was committed |
| actor | Authenticated user that performed the action |
| role | Role in force at the time of the action |
| action | Structured event type, for example ORDER_EXECUTED |
| resource | Entity type and identifier the action applied to |
| previous_state | Relevant state before the change |
| new_state | Relevant state after the change |
| metadata | Request context such as device or address where appropriate |
Recorded event types
Account
USER_REGISTERED, KYC_STARTED, KYC_COMPLETED, ACCOUNT_FUNDED
Orders
ORDER_CREATED, ORDER_MODIFIED, ORDER_CANCELLED, ORDER_EXECUTED, ORDER_REJECTED
Derivatives
DERIVATIVES_ACCESS_REQUESTED, KNOWLEDGE_TEST_COMPLETED, DERIVATIVES_ACCESS_GRANTED
Suitability
SUITABILITY_UPDATED, DISCLOSURE_ACKNOWLEDGED
Risk
POSITION_LIMIT_CHANGED, RISK_ALERT_RAISED, ACCOUNT_RESTRICTED
Configuration
PRODUCT_PERMISSION_CHANGED, BROKER_CONFIGURATION_UPDATED
Searchable and filterable
Compliance and operations users can filter the log by actor, role, action, resource and date range. Records are append-only: they can be read and exported, but not edited.
Speak with the GIGX team
We work with licensed brokers, investment firms and market infrastructure operators.