<group name="local,custom">
<rule id="100901" level="11">
<if_sid>67017</if_sid>
<description>67017 triggered</description>
</rule>
<rule id="100902" level="11">
<if_sid>92650</if_sid>
<description>92650 triggered</description>
</rule>
<!-- Correlate rule 92650 with details from 67017 -->
<rule id="100903" level="11" timeframe="5">
<if_sid>100901</if_sid>
<if_sid>100902</if_sid>
<description>
Correlate 92650 and 67017. 92650 is the service creation, 67017 shows network access if done remotely.
</description>
</rule>
</group>Hi Vetter,
I believe your goal is to hunt for the 67017 that happened a couple of seconds before the 92650 event which shows the remote user access.
We can write a rule like this to check if 100901 or 100902 triggered 2 times within a time frame.
<group name="local,custom1">
<rule id="100901" level="11">
<if_sid>67017</if_sid>
<description>67017 triggered</description>
</rule>
<rule id="100902" level="11">
<if_sid>92650</if_sid>
<description>92650 triggered</description>
</rule>
<!-- Correlate rule 92650 with details from 67017 -->
</group>
<group name="local,custom2">
<rule id="100903" level="11" frequency="2" timeframe="360">
<if_matched_group>custom1</if_matched_group>
<description>
Correlate 92650 and 67017. 92650 is the service creation, 67017 shows network access if done remotely.
</description>
</rule>
</group>