whids v1.8 beta6 releases: Very flexible Host IDS designed for Windows

WHIDS

Very flexible Host IDS designed for Windows. We are making use of a previously developed rule engine Gene designed to match Windows events according to custom rules. The rules are simple to write and easy to understand so that everyone can understand why a rule has triggered it.

With the democratization of Sysmon, this tool is perfect to quickly build hunting rules or simply monitoring rules to screen things of interest happening on your machine(s). With WHIDS you don’t have to bother with an overcomplicated Sysmon configuration which often turns to the nightmare when you want to be very specific. The simplest thing is just to enable all the logging capabilities of Sysmon and let WHIDS do his job, grab a coffee and wait for the juicy stuff to happen. The tool has very low overhead for the system, according to our current benchmarks.

This tool can be used on any Windows machine so you might install it easier on regular workstations or on Windows Event Collectors where you are receiving all the logs of your infrastructure. The output format is nothing else than JSON so it is very easy to handle the alerts generated by the HIDS in whatever tool you want to use for this purpose like ELK, Splunk or simply your favorite SIEM.

Changelog v1.8 beta6

• #90 v1.8.0 beta5 bug
• #91 Correlate and enrich Microsoft-Windows-Kernel-File ETW logs

Download

Example

Here is an example of a rule designed to catch suspicious access to lsass.exe as it is done by the well known Mimikatz credential dump tool.

{

  "Name": "MaliciousLsassAccess",

  "Tags": ["Mimikatz", "Credentials", "Lsass"],

  "Meta": {

    "EventIDs": [10],

    "Channels": ["Microsoft-Windows-Sysmon/Operational"],

    "Computers": [],

    "Traces": [],

    "Criticality": 10,

    "Author": "0xrawsec"

  },

  "Matches": [

    "$ct: CallTrace ~= 'UNKNOWN'",

    "$lsass: TargetImage ~= '(?i:\\\\lsass\\.exe$)'"

  ],

  "Condition": "$lsass and $ct"

}

You can find a bunch of other rules as well as a quick introduction to the syntax of the rules on the Gene repository.

Demo

Running WHIDS with an already running Powershell Empire agent which invokes Mimikatz module.

Hereafter is the kind of output returned by WHIDS. An additional section is added to the JSON event where the criticality of the alert is reported along with the different signatures which matched the event.

{

  "Event": {

    "EventData": {

      "CallTrace": "C:\\Windows\\SYSTEM32\\ntdll.dll+4bf9a|C:\\Windows\\system32\\KERNELBASE.dll+189b7|UNKNOWN(00000000259123BC)",

      "GrantedAccess": "0x1410",

      "SourceImage": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\powershell.exe",

      "SourceProcessGUID": "{49F1AF32-DD18-5A72-0000-0010042C0A00}",

      "SourceProcessId": "2248",

      "SourceThreadId": "3308",

      "TargetImage": "C:\\Windows\\system32\\lsass.exe",

      "TargetProcessGUID": "{49F1AF32-DB3B-5A72-0000-001013690000}",

      "TargetProcessId": "492",

      "UtcTime": "2018-02-01 11:24:53.331"

    },

    "GeneInfo": {

      "Criticality": 10,

      "Signature": [

        "MaliciousLsassAccess"

      ]

    },

    "System": {

        "Classical Windows Event System Section": "..."

    }

  }

}

Copyright 2018 qjerome

Source: https://github.com/0xrawsec/