What's Chainsaw?

Chainsaw is a powerful (and free) command-line tool created by F-Secure which in my experience is great for quick wins and providing start points in Windows endpoint investigations and Threat Hunts.

More info from the Chainsaw creators can be found here: https://labs.f-secure.com/tools/chainsaw/

And it is available on F-Secure Countercept’s GitHub here: https://github.com/Countercept/chainsaw

Chainsaw uses both in-built detection logic and external rules to identify threats in Windows Event logs. The external rules use the ‘Sigma’ signature format (written in YAML) which is designed to help security analysts describe and share information about logs easily.

More info on Sigma is available on SigmaHQ’s GitHub here: https://github.com/SigmaHQ/sigma

Chainsaw’s use of Sigma means you can add your own detection rules as and when you identify new event log Indicators of Compromise (IOCs). In this blog I’ll be showing you how to make and incorporate your own Sigma rules into Chainsaw.

Hunt syntax

Before we modify any files, it is useful to understand how they interact when Chainsaw is executed. Chainsaw has two functionalities, ‘search’ and ‘hunt’. The latter utilises external Sigma rules to match against .evtx files.

When you use Chainsaw’s ‘hunt’ functionality with external rules, you need to provide three parameters:

1)     The location of the .evtx files (the event logs you want hunt accross)

2)    The location of the .yml files (the Sigma rule IOCs you want to hunt for)

3)    The location of the .yml file used for rule mapping (the specific Event IDs within the .evtx to hunt in)

The hunt command will look something like:

chainsaw.exe hunt "C:\DirectoryContainingEventLogs" --rules “C:\DirectoryContainingSigmaRules” --mapping “C:\SigmaMappingFile.yml”

Why make your own rules?

Testing Chainsaw’s in-built detection logic and the Sigma rules available to download with the tool against sample data from previous incidents, I was able to identify Windows Event Log IOCs that weren’t being detected.

Specifically, the tool wasn’t detecting event logs that indicated usage of Base64 encoded PowerShell. These events were being logged with Event IDs 400 and 600 which weren’t part of the ‘out-of-the-box’ mapping file (sigma-mapping.yml) and the existing Sigma rules also weren’t configured to spot it.  Therefore, to successfully detect my encoded PowerShell IOC with Chainsaw, I needed to create/modify the external rules and mapping.

Creating Your Own Rules

First up, you can either create a new mapping file if you wanted to run your custom detections separately, or you can edit the existing mapping file ‘sigma-mapping.yml’. In this example, I modified the original so that my custom Sigma rules are added to the existing search logic.

In the mapping file, you are providing the Event ID you want Chainsaw to run the rules against, the provider of the logs, which fields of the log you want to become search fields, and what additional fields you want as table headers in the output.

To help the correct name of the ‘provider’ etc. it’s a good idea to open the ‘Friendly View’ details of the event log you’re creating a rule for in Event Viewer.

It’s also a good idea to use an existing Sigma rule as a template as YAML won’t forgive you if your indentations and spacings aren’t perfect.

Now we’ve told Chainsaw where it needs to look, we need to tell it what to look for with our Sigma rule. In this example I have created a new Sigma rule which contains among other things, the title of the detection (for output) and the strings that need to be present in the log to produce a match.

Happy Hunting!