| sidebar_position | 3 | ||
|---|---|---|---|
| sidebar_label | Syslog Audit | ||
| sidebar_custom_props |
|
Forwards audit log events to your syslog server. Supports optional filtering to control which audit events are delivered.
- Go to Integrations and open the Available tab.
- Click + Add on the Syslog Audit tile.
- Fill in the connection parameters:
| Field | Required | Description |
|---|---|---|
| Syslog Server IP/Domain | Yes | IP address or hostname of your syslog server |
| Syslog Server Port | Yes | Port your syslog server listens on |
| Protocol | Yes | Transport protocol: TCP, UDP, or TLS |
| Message Format | No | RFC 5424 (default) or RFC 3164 |
| Facility | No | Syslog facility to use for outgoing messages |
| Forwarding Scope | Yes | Send All Audits forwards every audit event. Send Filtered Audits activates the user condition filter below. |
- If you selected Send Filtered Audits, use Configure user condition to add filter rules that control which audit events are forwarded.
- Click Save.
Messages are delivered using the selected wire format. RFC 5424 example:
<142>1 2024-01-15T10:30:00Z hostname quilr-siem-service - - - {json_body}
The JSON body contains the audit log event:
{
"event_source": "quilr-audit",
"event": {
"trace_id": "uuid-v4",
"subscriber": "subscriber-id",
"tenant": "acme-corp",
"service_name": "quilr-entities-service",
"event_code": "USR-001",
"task": "CREATE_USER",
"category": "USER_MANAGEMENT",
"resource_type": "USER",
"resource": "user@acme.com",
"status": "SUCCESS",
"log_level": "INFO",
"actioned_by": "admin@acme.com",
"actioned_at": "2024-01-15T10:30:00.000Z",
"extra_info": {},
"error_info": {}
}
}