F.O.S.S.O.C. || Free & open-source Security Operations Centre
GithubTeam
  • Overview
    • Need for this project
    • Aim of this project
    • Network Architecture
    • System Specifications
  • Wazuh Manager
    • Setup
    • Log Behaviour
      • Creating logs for every event
      • Adding custom Wazuh Rules
        • CLI method
        • GUI method
    • Rules
      • Mimikatz Rule
    • Integration
      • With Shuffle
  • Wazuh Agent (Windows)
    • Setup
  • Sysmon
    • Setup
  • TheHive
    • Setup
    • Integrating with Shuffle
  • Cortex
    • Setup
  • Shuffle
    • Setup
    • Workflows
      • Mimikatz Workflow
  • Case Studies
    • Mimikatz
      • Mimikatz execution
      • Wazuh rule
      • Shuffle workflow
  • Conclusion
    • Team
Powered by GitBook
On this page

Was this helpful?

  1. Wazuh Manager
  2. Rules

Mimikatz Rule

The custom rule would look as follows:

Wazuh rule for detecting Mimikatz
++  <rule id="100002" level="10">
++    <if_group>sysmon_event1</if_group>
++    <field name="win.eventdata.originalFileName" type="pcre2">(?i)mimikatz\.exe</field>
++    <description>Mimikatz usage detected.</description>
++    <mitre>
++      <id>T1003</id>
++    </mitre>
++  </rule>    
  1. <rule id="100002" level="10">: This is the rule definition with an ID of 100002 and a severity level of 10.

  2. <if_group>sysmon_event1</if_group>: This specifies the condition or event group that triggers the rule. In this case, it's "sysmon_event1."

  3. <field name="win.eventdata.originalFileName" type="pcre2">(?i)mimikatz\.exe</field>: This part defines a condition on a specific field in the event data. It checks if the original file name in the Windows event data matches the regular expression "(?i)mimikatz.exe" case-insensitively.

    • name="win.eventdata.originalFileName": Specifies the field to check.

    • type="pcre2": Indicates the type of regular expression used.

    • (?i)mimikatz\.exe: The actual regular expression to match against the original file name.

  4. <description>Mimikatz usage detected.</description>: Provides a human-readable description of what the rule is checking for. In this case, it states that the rule is detecting the usage of Mimikatz.

  5. <mitre><id>T1003</id></mitre>: Associates the rule with a specific MITRE ATT&CK technique ID. In this case, it's T1003, which is "Credential Dumping."

Adding rules

We can follow either of the following methods to add custom rules:

PreviousRulesNextIntegration

Last updated 1 year ago

Was this helpful?

GUI method
CLI method