Skip to content

Commit c473160

Browse files
authored
Update README.md
1 parent de57776 commit c473160

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,15 @@ All the detection patterns from the [threathunting-keywords](https://github.com/
1313
![image](https://github.com/mthcht/ThreatHunting-Keywords-yara-rules/assets/75267080/fda53ec2-28cb-4f16-bbb9-36f5afba922c)
1414

1515

16+
1617
- 🛠️ **offensive tool keyword**: These keywords relate to offensive tools or exhibit high confidence of malicious intent. It's important that these keywords remaons relevant and reliable in detecting potential threats (low false positive rate).
1718
- 🛠️ **greyware tool keyword**: Keywords in this category correspond to 'legitimate' tools that are abused by malicious actors. As these tools also have legitimate uses, the potential for false positives is inherently higher. It's important to interpret these results with the understanding that not all detections may signify malicious activity
1819
- 🛠️ **signature keyword**: These keywords may not directly associate with tools but may include security product signature names, specific strings, or words significant in threat detection.
1920

2021
- `all.yara`: Contains all the rules
2122
- `offensive_tools.yara`: all the offensive tools rules
2223
- `greyware_tools.yara`: all the greyware tools (more false positives expected - triage necessary)
24+
- I also added a folder named `specific` containing manually crafted YARA rules curated for sharing.
2325

2426
a sperated rule file exist for each tool, organized in alphabetical order to bypass the GitHub limitation of 1000 files per directory.
2527

0 commit comments

Comments
 (0)