-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix documentation for "MITRE ATT&CK framework". Section "Customization" #7567
Comments
Initial testI tested the documentation on my current Wazuh setup (v4.7.4), and everything works, as seen in the screenshot below: This implies that the error is not from the rule or the steps in the documentation. Alert log
|
Testing on 4.9.0
|
Possible fixAfter several tests and tweaks, I noticed the Windows alert logs I copied from the 4.7.4 server had 4 slashes ( <group name="windows,sysmon,privilege-escalation">
<rule id="110011" level="10">
<if_sid>61615</if_sid>
<field name="win.eventdata.targetObject" type="pcre2">HKLM\\System\\CurrentControlSet\\Services\\PSEXESVC</field>
<field name="win.eventdata.eventType" type="pcre2">^SetValue$</field>
<field name="win.eventdata.user" type="pcre2">NT AUTHORITY\\SYSTEM</field>
<description>PsExec service running as $(win.eventdata.user) has been created on $(win.system.computer).</description>
<mitre>
<id>T1543.003</id>
</mitre>
</rule>
</group> This works. I am guessing there has been a change in how Windows logs are processed which means that rules that were written to account for the extra slashes would no longer work. The successful test result is below:
|
I will keep this issue open until I close the corresponding issue in wazuh/wazuh, but no documentation changes will be made, the parser functionality will be left as it works in 4.8.1. |
During the wazuh/wazuh#24852, I deployed a distributed Wazuh (one server for each central component) using the Offline Installation method step by step.
The related documentation is here: https://documentation-dev.wazuh.com/v4.9.0-alpha3/deployment-options/offline-installation/step-by-step.html
After a successful installation, I execute the MITRE ATT&CK Customization.
The related documentation is here: https://documentation-dev.wazuh.com/v4.9.0-alpha3/user-manual/ruleset/mitre.html#customization
After executing each step, I found that no alert was present in the dashboard with rule.id "110011", which is expected to be generated in this test.
The test was done in a first attempt using an agent Windows Server 2019. In a second attempt using an agent Windows 11 as the documentation describes.
In both cases, no alerts with rule.id "110011" were present on the dashboard.
The text was updated successfully, but these errors were encountered: