Suricata EVE anomaly
Suricata EVE anomaly. 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 7
One complete record selected; values unchanged.
Download the exact sample · Offline research kit
SHA-256: 9120cc636c0ffbc3f27936e578c743d60f5f432a43435931acd16a1c099d9bca
{
"timestamp": "2023-09-18T06:13:58.882971+0000",
"flow_id": 1676750115612680,
"pcap_cnt": 2878,
"event_type": "anomaly",
"src_ip": "192.168.100.237",
"src_port": 49175,
"dest_ip": "142.11.240.191",
"dest_port": 35361,
"proto": "TCP",
"pkt_src": "wire/pcap",
"ether": {
"src_mac": "12:a9:86:6c:77:de",
"dest_mac": "52:54:00:36:3e:ff"
},
"tx_id": 3,
"anomaly": {
"app_proto": "http",
"type": "applayer",
"event": "UNABLE_TO_MATCH_RESPONSE_TO_REQUEST",
"layer": "proto_parser"
}
}
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 |
pkt_src | str |
ether.src_mac | str |
ether.dest_mac | str |
tx_id | int |
anomaly.app_proto | str |
anomaly.type | str |
anomaly.event | str |
anomaly.layer | 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.