Suricata EVE pgsql
Suricata EVE pgsql. EVE JSON emits typed records from the Suricata network engine.
Source and collection
Configured eve-log output, commonly eve.json.
Record Suricata version, enabled EVE types, ruleset and IDS versus inline IPS mode.
Native example and provenance
publisher documentation example. Published example; no independent capture provenance claimed.
Original publisher / pinned upstream fixture — preformatted example 77
One complete record selected; values unchanged.
Download the exact sample · Offline research kit
SHA-256: 78aceb48bb95c3fbe3eb0cf4fdcc72223b5c8d3db885fe0d6b7443a2c12e1135
{
"timestamp": "2021-11-24T16:56:24.403417+0000",
"flow_id": 1960113262002448,
"pcap_cnt": 780,
"event_type": "pgsql",
"src_ip": "172.18.0.1",
"src_port": 54408,
"dest_ip": "172.18.0.2",
"dest_port": 5432,
"proto": "TCP",
"pgsql": {
"tx_id": 4,
"request": {
"simple_query": "select * from rule limit 5000;"
},
"response": {
"field_count": 7,
"data_rows": 5000,
"data_size": 3035751,
"command_completed": "SELECT 5000"
}
}
}
Structure and field interpretation
| Field/path | Serialized type |
|---|---|
timestamp | str |
flow_id | int |
pcap_cnt | int |
event_type | str |
src_ip | str |
src_port | int |
dest_ip | str |
dest_port | int |
proto | str |
pgsql.tx_id | int |
pgsql.request.simple_query | str |
pgsql.response.field_count | int |
pgsql.response.data_rows | int |
pgsql.response.data_size | int |
pgsql.response.command_completed | str |
- event_type
- Selects the payload schema.
- flow_id
- Flow correlation identifier; preserve numeric precision.
- timestamp
- Event time with offset.
- alert
- Rule-match context when present.
Investigation uses
- Correlate flow_id and event_type with related protocol and alert records.
- For alerts, review signature, action and packet context before assigning a verdict.
Validation boundaries
An alert is a rule match, not independently confirmed compromise. Fields and nested structures differ by event type and version.
This sample passed byte-integrity and JSON/XML parsing checks, including the catalogue’s specified event discriminators. This is not a complete vendor-schema validation or a tested detection.
For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.
Related sources
Ecosystem connections
- Telemetry Library — ATT&CK data components
- Detection Rules — candidate detection content
- Threat hunting — from intelligence to validated defense
- Practical security learning paths
- AdversaryGraph — evidence-led investigation
References
Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.