Comments (7)
alexkornitzer
commented on May 17, 2024
1
Apologies for the delay, potentially this weekend, I should be able to get an alpha ready by the end of Sunday.
from chainsaw.
jvmendezp
commented on May 17, 2024
1
hello, I added this comment #77 (comment) requesting sigma tags, and sigma rule id in the results. if we can get arbitrary data from matched sigma rule, this will be wonderful
FYI: @jurelou
from chainsaw.
alexkornitzer
commented on May 17, 2024
Will factor it into the v2 rework which is now underway.
from chainsaw.
jurelou
commented on May 17, 2024
Do you know when this will be implemented?
This is a major feature for me.
tell me if i can help you
from chainsaw.
alexkornitzer
commented on May 17, 2024
Okay so a tad delayed and not properly finished but the next branch can now do what you requested. So if urgent while I still finish up the code if you are happy with no guarantees then you can make use of that. Eventually when the code is ready, I will prepare a proper alpha release. For now you can do:
git clone https://github.com/countercept/chainsaw.git
cd chainsaw
git checkout next
cargo build --release
cd target/release
./chainsaw hunt -m ../../mappings/sigma-event-logs.yml /tmp/sigma/rules /tmp/evtx-attack-samples --json > /tmp/test.json
The output will look something like this:
[
{
"authors": [
"Daniil Yugoslavskiy",
"oscd.community"
],
"group": "Suspicious Command Line",
"kind": "individual",
"document": {
"kind": "evtx",
"data": {
"Event": {
"EventData": {
"CommandLine": "",
"NewProcessId": "0xcfc",
"NewProcessName": "C:\\Users\\user01\\Desktop\\plink.exe",
"ProcessId": "0xe60",
"SubjectDomainName": "EXAMPLE",
"SubjectLogonId": "0x2ed80",
"SubjectUserName": "user01",
"SubjectUserSid": "S-1-5-21-1587066498-1489273250-1035260531-1106",
"TokenElevationType": "%%1936"
},
"System": {
"Channel": "Security",
"Computer": "PC01.example.corp",
"Correlation": null,
"EventID": 4688,
"EventRecordID": 227714,
"Execution_attributes": {
"ProcessID": 4,
"ThreadID": 56
},
"Keywords": "0x8020000000000000",
"Level": 0,
"Opcode": 0,
"Provider_attributes": {
"Guid": "54849625-5478-4994-A5BA-3E3B0328C30D",
"Name": "Microsoft-Windows-Security-Auditing"
},
"Security": null,
"Task": 13312,
"TimeCreated_attributes": {
"SystemTime": "2019-02-13T18:03:28.318440Z"
},
"Version": 1
}
},
"Event_attributes": {
"xmlns": "http://schemas.microsoft.com/win/2004/08/events/event"
}
}
},
"level": "medium",
"name": "Exfiltration and Tunneling Tools Execution",
"rule": "sigma",
"status": "test",
"timestamp": "2019-02-13T18:03:28.318440"
},
{
"authors": [
"frack113"
],
...
Hopefully that output format will not change but this is alpha, and I am double checking my design decisions today along with trying to get this stuff finished up.
from chainsaw.
alexkornitzer
commented on May 17, 2024
Have made more progress today, currently chainsaw will run slower than v1 as I have not put the optimisations in yet. But I should be able to get a stable alpha out soon for user feedback due the huge number of changes I have made.
from chainsaw.
alexkornitzer
commented on May 17, 2024
This is addressed in v2.0.0-alpha.0
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.