1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
|
:orphan: Document not referenced in a toctree, so add this.
DNS EVE Logging Changes for 8.0
===============================
Suricata 8.0 modifies the DNS logging in ``dns`` and ``alert`` records
to a version ``3`` logging format. These changes address a lack of
fidelity in alerts for DNS responses, as well as unify the format of
the ``dns`` object accross ``dns`` and ``alert`` objects.
Ticket: https://redmine.openinfosecfoundation.org/issues/6281
Additionally, version ``3`` DNS response messages will now use the IP
address of the responder as the ``src_ip``, not the client, ticket:
https://redmine.openinfosecfoundation.org/issues/6400
The changes are summarized below:
* DNS requests now have a type of ``request`` instead of ``query``.
* DNS responses now have a type of ``response`` instead of ``answer``.
* DNS requests will now log the queries in an array instead of logging
multiple request events in the case where the request contained
multiple queries. This was already done for DNS requests logged as
part of an ``alert``.
.. list-table::
:widths: 50 50
:header-rows: 1
* - 7.0
- 8.0
* - .. code-block::
{
"event_type": "dns",
"dns": {
"type": "query",
"id": 0,
"rrname": "www.suricata.io",
"rrtype": "A",
"tx_id": 0,
"opcode": 0
}
}
- .. code-block::
{
"event_type": "dns",
"dns": {
"version": 3,
"type": "request",
"tx_id": 0,
"id": 0,
"flags": "100",
"rd": true,
"opcode": 0,
"rcode": "NOERROR",
"queries": [
{
"rrname": "www.suricata.io",
"rrtype": "A"
}
]
}
}
* DNS responses now log the queries in a ``queries`` array instead of
logging the first ``rrname`` and ``rrtype`` directly in the ``dns``
object.
.. list-table::
:header-rows: 1
* - 7.0
- 8.0
* - .. code-block::
{
"event_type": "dns",
"dns": {
"version": 2,
"type": "answer",
"id": 0,
"flags": "8180",
"qr": true,
"rd": true,
"ra": true,
"opcode": 0,
"rrname": "www.suricata.io",
"rrtype": "A",
"rcode": "NOERROR",
"answers": [
{
"rrname": "www.suricata.io",
"rrtype": "CNAME",
"ttl": 3597,
"rdata": "suricata.io"
},
{
"rrname": "suricata.io",
"rrtype": "A",
"ttl": 597,
"rdata": "35.212.0.44"
}
]
}
}
- .. code-block::
{
"event_type": "dns",
"dns": {
"version": 3,
"type": "response",
"tx_id": 1,
"id": 0,
"flags": "8180",
"qr": true,
"rd": true,
"ra": true,
"opcode": 0,
"rcode": "NOERROR",
"queries": [
{
"rrname": "www.suricata.io",
"rrtype": "A"
}
],
"answers": [
{
"rrname": "www.suricata.io",
"rrtype": "CNAME",
"ttl": 3597,
"rdata": "suricata.io"
},
{
"rrname": "suricata.io",
"rrtype": "A",
"ttl": 597,
"rdata": "35.212.0.44"
}
],
}
}
* DNS requests logged in an alert object will now log the ``answers``
as an array. See above 8.0 example for the format. The ``dns``
object is now consistent across DNS requests and responses, as well
as in ``alerts``.
* Example of alert on DNS request
.. list-table::
:header-rows: 1
* - 7.0
- 8.0
* - .. code-block::
{
"event_type": "alert",
"dns": {
"query": [
{
"type": "query",
"id": 0,
"rrname": "www.suricata.io",
"rrtype": "A",
"tx_id": 0,
"opcode": 0
}
]
}
}
- .. code-block::
{
"event_type": "alert",
"dns": {
"version": 3,
"type": "request",
"tx_id": 0,
"id": 0,
"flags": "100",
"rd": true,
"opcode": 0,
"rcode": "NOERROR",
"queries": [
{
"rrname": "www.suricata.io",
"rrtype": "A"
}
]
},
}
* Example of alert on DNS response
.. list-table::
:header-rows: 1
* - 7.0
- 8.0
* - .. code-block::
{
"event_type": "alert",
"dns": {
"answer": {
"version": 2,
"type": "answer",
"id": 0,
"flags": "8180",
"qr": true,
"rd": true,
"ra": true,
"opcode": 0,
"rrname": "www.suricata.io",
"rrtype": "A",
"rcode": "NOERROR"
}
}
}
- .. code-block::
{
"event_type": "alert",
"dns": {
"version": 3,
"type": "response",
"tx_id": 1,
"id": 0,
"flags": "8180",
"qr": true,
"rd": true,
"ra": true,
"opcode": 0,
"rcode": "NOERROR",
"queries": [
{
"rrname": "www.suricata.io",
"rrtype": "A"
],
"answers": [
{
"rrname": "www.suricata.io",
"rrtype": "CNAME",
"ttl": 3597,
"rdata": "suricata.io"
},
{
"rrname": "suricata.io",
"rrtype": "A",
"ttl": 597,
"rdata": "35.212.0.44"
}
]
},
}
|
