Suricata EVE mqtt
Suricata EVE mqtt. 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 63
One complete record selected; values unchanged.
Download the exact sample · Offline research kit
SHA-256: db0bbe2f46266df5677adb2f0fe505f7082b1426aa3afddf6bd8b1db72d138ba
{
"timestamp": "2020-05-19T18:00:39.016985+0200",
"flow_id": 1454127794305760,
"pcap_cnt": 65,
"event_type": "mqtt",
"src_ip": "0000:0000:0000:0000:0000:0000:0000:0001",
"src_port": 60105,
"dest_ip": "0000:0000:0000:0000:0000:0000:0000:0001",
"dest_port": 1883,
"proto": "TCP",
"mqtt": {
"publish": {
"qos": 2,
"retain": false,
"dup": false,
"topic": "house/bulbs/bulb1",
"message_id": 3,
"message": "OFF"
},
"pubrec": {
"qos": 0,
"retain": false,
"dup": false,
"message_id": 3
},
"pubrel": {
"qos": 1,
"retain": false,
"dup": false,
"message_id": 3
},
"pubcomp": {
"qos": 0,
"retain": false,
"dup": false,
"message_id": 3
}
}
}
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 |
mqtt.publish.qos | int |
mqtt.publish.retain | bool |
mqtt.publish.dup | bool |
mqtt.publish.topic | str |
mqtt.publish.message_id | int |
mqtt.publish.message | str |
mqtt.pubrec.qos | int |
mqtt.pubrec.retain | bool |
mqtt.pubrec.dup | bool |
mqtt.pubrec.message_id | int |
mqtt.pubrel.qos | int |
mqtt.pubrel.retain | bool |
mqtt.pubrel.dup | bool |
mqtt.pubrel.message_id | int |
mqtt.pubcomp.qos | int |
mqtt.pubcomp.retain | bool |
mqtt.pubcomp.dup | bool |
mqtt.pubcomp.message_id | int |
- 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.