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
|
ENIP/CIP Keywords
=================
enip_command
------------
For the ENIP command, we are matching against the command field found in the ENIP encapsulation.
Examples::
enip_command:99;
enip_command:list_identity;
enip_command uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
It can also be specified by text from the enumeration.
cip_service
-----------
For the CIP Service, we use a maximum of 3 comma separated values representing the Service, Class and Attribute.
These values are described in the CIP specification. CIP Classes are associated with their Service, and CIP Attributes
are associated with their Service. If you only need to match up until the Service, then only provide the Service value.
If you want to match to the CIP Attribute, then you must provide all 3 values.
Examples::
cip_service:75
cip_service:16,246,6
(cf. http://read.pudn.com/downloads166/ebook/763211/EIP-CIP-V1-1.0.pdf)
Information on the protocol can be found here:
`<http://literature.rockwellautomation.com/idc/groups/literature/documents/wp/enet-wp001_-en-p.pdf>`_
enip.status
-----------
For the ENIP status, we are matching against the status field found in the ENIP encapsulation.
It uses a 32-bit unsigned integer as value.
enip.status uses an :ref:`unsigned 32-bits integer <rules-integer-keywords>`.
It can also be specified by text from the enumeration.
Examples::
enip.status:100;
enip.status:>106;
enip.status:invalid_cmd;
enip.protocol_version
---------------------
Match on the protocol version in different messages.
It uses a 16-bit unsigned integer as value.
enip.protocol_version uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.protocol_version:1;
enip.protocol_version:>1;
enip.cip_attribute
------------------
Match on the cip attribute in different messages.
It uses a 32-bit unsigned integer as value.
This allows to match without needing to match on cip.service.
enip.cip_attribute uses an :ref:`unsigned 32-bits integer <rules-integer-keywords>`.
Examples::
enip.cip_attribute:1;
enip.cip_attribute:>1;
enip.cip_instance
-----------------
Match on the cip instance in CIP request path.
It uses a 32-bit unsigned integer as value.
enip.cip_instance uses an :ref:`unsigned 32-bits integer <rules-integer-keywords>`.
Examples::
enip.cip_instance:1;
enip.cip_instance:>1;
enip.cip_class
--------------
Match on the cip class in CIP request path.
It uses a 32-bit unsigned integer as value.
enip.cip_class uses an :ref:`unsigned 32-bits integer <rules-integer-keywords>`.
This allows to match without needing to match on cip.service.
Examples::
enip.cip_class:1;
enip.cip_class:>1;
enip.cip_extendedstatus
-----------------------
Match on the cip extended status, if any is present.
For multiple service packet, will match on any of the seen statuses.
It uses a 16-bit unsigned integer as value.
enip.cip_extendedstatus uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.cip_extendedstatus:1;
enip.cip_extendedstatus:>1;
enip.revision
-------------
Match on the revision in identity message.
It uses a 16-bit unsigned integer as value.
enip.revision uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.revision:1;
enip.revision:>1;
enip.identity_status
--------------------
Match on the status in identity message (not in ENIP header).
It uses a 16-bit unsigned integer as value.
enip.identity_status uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.identity_status:1;
enip.identity_status:>1;
enip.state
----------
Match on the state in identity message.
It uses an 8-bit unsigned integer as value.
enip.state uses an :ref:`unsigned 8-bits integer <rules-integer-keywords>`.
Examples::
enip.state:1;
enip.state:>1;
enip.serial
-----------
Match on the serial in identity message.
It uses a 32-bit unsigned integer as value.
enip.serial uses an :ref:`unsigned 32-bits integer <rules-integer-keywords>`.
Examples::
enip.serial:1;
enip.serial:>1;
enip.product_code
-----------------
Match on the product code in identity message.
It uses a 16-bit unsigned integer as value.
enip.product_code uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.product_code:1;
enip.product_code:>1;
enip.device_type
----------------
Match on the device type in identity message.
It uses a 16-bit unsigned integer as value.
enip.device_type uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.device_type:1;
enip.device_type:>1;
enip.vendor_id
--------------
Match on the vendor id in identity message.
It uses a 16-bit unsigned integer as value.
enip.vendor_id uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.vendor_id:1;
enip.vendor_id:>1;
enip.product_name
-----------------
Match on the product name in identity message.
Examples::
enip.product_name; pcre:"/^123[0-9]*/";
enip.product_name; content:"swordfish";
``enip.product_name`` is a 'sticky buffer' and can be used as ``fast_pattern``.
enip.service_name
-----------------
Match on the service name in list services message.
Examples::
enip.service_name; pcre:"/^123[0-9]*/";
enip.service_name; content:"swordfish";
``enip.service_name`` is a 'sticky buffer' and can be used as ``fast_pattern``.
enip.capabilities
-----------------
Match on the capabilities in list services message.
It uses a 16-bit unsigned integer as value.
enip.capabilities uses an :ref:`unsigned 16-bits integer <rules-integer-keywords>`.
Examples::
enip.capabilities:1;
enip.capabilities:>1;
enip.cip_status
---------------
Match on the cip status (one of them in case of multiple service packet).
It uses an 8-bit unsigned integer as value.
enip.cip_status uses an :ref:`unsigned 8-bits integer <rules-integer-keywords>`.
Examples::
enip.cip_status:1;
enip.cip_status:>1;
|
