Comments (2)
Hi @Neo23x0
Thanks for raising this issue. I must have mis-understood the DRL as my interpretation was that as long as the sigma rule base remained unmodified, referenced and linked then showing the matching detections was okay without explicity naming the author for each detection.
My thought process for how the analyst workflow would work was:
Run Chainsaw -> View Detections -> Read Detection Logic -> Verify Chainsaw Detections Against Raw Data
The author information would be visible in the "Read Detection Logic" step when the analyst goes to the specific Sigma rule.
Regardless, I'm more than happy to add support for your requirements. I've opened PR #5 which adds --authors
as an optional flag to the hunt
module. Using this flag will add a new column to the table/CSV output which will include the author information. For example:
[+] Detection: (External Rule) - Suspicious File Creation
┌─────────────────────┬────┬────────────────────────────────┬───────────────────────────────────┬────────────────────────────┬──────────────────────────────────────────┬──────────────────────────────────────────┐
│ system_time │ id │ detection_rules │ rule_authors │ computer_name │ Event.EventData.TargetFilename │ image │
├─────────────────────┼────┼────────────────────────────────┼───────────────────────────────────┼────────────────────────────┼──────────────────────────────────────────┼──────────────────────────────────────────┤
│ 2019-03-17 19:09:41 │ 11 │ ‣ LSASS Memory Dump File │ ‣ Teymur Kheirkhabarov │ "PC04.example.corp" │ C:\Users\IEUser\Desktop\lsass.exe_190317 │ C:\Users\IEUser\Desktop\procdump.exe │
│ │ │ Creation │ oscd.community │ │ _120941.dmp │ │
├─────────────────────┼────┼────────────────────────────────┼───────────────────────────────────┼────────────────────────────┼──────────────────────────────────────────┼──────────────────────────────────────────┤
│ 2019-03-17 19:10:03 │ 11 │ ‣ LSASS Memory Dump File │ ‣ Teymur Kheirkhabarov │ "PC04.example.corp" │ C:\Users\IEUser\AppData\Local\Temp\lsass │ C:\Windows\system32\taskmgr.exe │
│ │ │ Creation │ oscd.community │ │ (2).DMP │ │
├─────────────────────┼────┼────────────────────────────────┼───────────────────────────────────┼────────────────────────────┼──────────────────────────────────────────┼──────────────────────────────────────────┤
│ 2019-05-14 14:04:05 │ 11 │ ‣ Hijack Legit RDP Session │ ‣ Samir Bousseaden │ "alice.insecurebank.local" │ C:\Users\administrator\AppData\Roaming\M │ C:\Windows\system32\mstsc.exe │
│ │ │ to Move Laterally │ │ │ icrosoft\Windows\Start Menu\Programs\Sta │ │
│ │ │ │ │ │ rtup\cmd.exe │ │
As long as you're happy that this satisfied the conditions of the DRL then I'll merge the PR.
from chainsaw.
This has been added to master with #11. It will be live in the next release.
from chainsaw.
Related Issues (20)
- Add timestamp format to help output HOT 2
- Deserialization error does't not show responsible file HOT 2
- Invalid Tau Key Pair error HOT 2
- Hunt with WEC/WEF HOT 2
- keyless identifiers cannot be converted HOT 3
- Check for potential I/0 error before processing HOT 1
- Erroneous Sigma Results using Hunt option HOT 7
- chainsaw project name collides with another rust project HOT 2
- Tau EventID Filter error HOT 6
- v2.4+ seems to be unable to recognize Sigma alerts HOT 1
- Sophos Antivirus Rule Not Parsing Data Events With Same Key Name HOT 5
- Print warning when loading Sigma rules with keyless search identifiers HOT 6
- Missing Sigma Base64 Encoding? HOT 3
- -o flag not recognized HOT 2
- No executable HOT 1
- Looking for clarity for mft yaml 'filter' issue HOT 3
- [Feature Request] Support for "contains", "|" and "all" in both chainsaw and sigma rules HOT 4
- Search feature doesn't parse backslashes HOT 2
- Feature Request: Event Log ID / Sigma Summary HOT 1
- '--timezone' and '--local' option not working as intended HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chainsaw.