Ransomware artifacts added to File Creation config

README.md

@@ -1,20 +1,28 @@
-# sysmon-config | A Sysmon configuration file for everybody to fork #
+# sysmon-config | A ransomware focused Sysmon configuration file #
 
-This is a Microsoft Sysinternals Sysmon configuration file template with default high-quality event tracing.
+This is a Microsoft Sysinternals Sysmon configuration file template with
+default high-quality event tracing. This is a fork of
+[SwiftOnSecurity](https://twitter.com/SwiftOnSecurity/)'s awesome
+[sysmon-config](https://github.com/SwiftOnSecurity/sysmon-config), with an
+additional focus on ransomware artifacts.
 
-The file should function as a great starting point for system change monitoring in a self-contained and accessible package. This configuration and results should give you a good idea of what's possible for Sysmon. Note that this does not track things like authentication and other Windows events that are also vital for incident investigation.
+## Reasoning ##
 
-      **[sysmonconfig-export.xml](https://github.com/SwiftOnSecurity/sysmon-config/blob/master/sysmonconfig-export.xml)**
+Ransomware commonly encrypt documents and other files, often renaming them with
+deterministic file names and extensions in the process. In addition, they
+create instructions in the forms of text files, images or executables detailing
+how to restore these files (often in the form of payment). Monitoring for files
+that match these ransomware artifacts may provide security teams with early
+warnings of a ransomware outbreak.
 
-Because virtually every line is commented and sections are marked with explanations, it should also function as a tutorial for Sysmon and a guide to critical monitoring areas in Windows systems.
+It is strongly suggested that you configure your SIEM or alerting system when
+there is a large number of Sysmon Event Code 11 (File Creation or Overwrites)
+events that match file names or extensions commonly associated with ransomware.
 
-- For a far more exhaustive and detailed approach to Sysmon configuration from a different approach, see also **[sysmon-modular](https://github.com/olafhartong/sysmon-modular)** by [@olafhartong](https://twitter.com/olafhartong), which can act as a superset of sysmon-config.
-
-- Sysmon is a compliment to native Windows logging abilities, not a replacement for it. For valuable advice on these configurations, see **[MalwareArchaeology Logging Cheat Sheets](https://www.malwarearchaeology.com/cheat-sheets)** by [@HackerHurricane](https://twitter.com/hackerhurricane).
-
-Note: Exact syntax and filtering choices in the configuration are highly deliberate in what they target, and to have as little performance impact as possible. Sysmon's filtering abilities are different than the built-in Windows auditing features, so often a different approach is taken than the normal static listing of paths. 
-
-      **[See other forks of this configuration](https://github.com/SwiftOnSecurity/sysmon-config/network)**
+**N.B.** There are some ransomware variants that do not rename file extensions,
+or use completely random extensions, which will not be detected by this
+Sysmon configuration. Use your judgment, apply appropriate Anti-Virus and
+other controls, practice defense-in-depth.
 
 ## Use ##
 ### Install ###
@@ -35,15 +43,8 @@ Run with administrator rights
 sysmon.exe -u
 ~~~~
 
-## Required actions ##
-
-### Prerequisites ###
-Highly recommend using [Notepad++](https://notepad-plus-plus.org/) to edit this configuration. It understands UNIX newline format and does XML syntax highlighting, which makes this very understandable. I do not recommend using the built-in Notepad.exe.
-
-### Customization ###
-You will need to install and observe the results of the configuration in your own environment before deploying it widely. For example, you will need to exclude actions of your antivirus, which will otherwise likely fill up your logs with useless information.
-
-The configuration is highly commented and designed to be self-explanatory to assist you in this customization to your environment.
+## Thanks ##
 
-### Design notes ###
-This configuration expects software to be installed system-wide and NOT in the C:\Users folder. Various pieces of software install themselves in User directories, which are subject to extra monitoring. Where possible, you should install the system-wide version of these pieces of software, like Chrome. See the configuration file for more instructions.
+Thanks to [SwiftOnSecurity](https://twitter.com/SwiftOnSecurity/) for their well
+documented Sysmon configuration, and mark Russinovich and Thomas Garnier for
+developing Sysmon.