SIGMA-detection-rules VS LOLBAS

Compare SIGMA-detection-rules vs LOLBAS and see what are their differences.

SIGMA-detection-rules

Set of SIGMA rules (>320) mapped to MITRE ATT&CK tactic and techniques (by mdecrevoisier)

LOLBAS

Living Off The Land Binaries And Scripts - (LOLBins and LOLScripts) (by LOLBAS-Project)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
SIGMA-detection-rules LOLBAS
2 5
265 6,581
- 2.6%
6.4 8.2
about 2 months ago 8 days ago
XSLT
Creative Commons Zero v1.0 Universal GNU General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

SIGMA-detection-rules

Posts with mentions or reviews of SIGMA-detection-rules. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-04.
  • should we write our own custom rule
    2 projects | /r/cybersecurity | 4 Dec 2023
    I am currently employed as a cyber analyst, and we've recently implemented an Endpoint Detection and Response (EDR) system. Upon closer inspection, I've observed that numerous events are not being flagged as alerts. This raises a crucial question: should I take the initiative to create custom rules to ensure these events are brought to our attention, or should I rely solely on the EDR's intrinsic capabilities to detect and classify threats? As a potential solution, I'm contemplating the implementation of rules based on Sigma, such as those available at the following repository: here. Your insights and experiences on the effectiveness of this approach would be greatly appreciated. Thank you for your time and assistance.
  • Installed Graylog. 7 million log entries per month. Now what?
    5 projects | /r/sysadmin | 27 May 2022
    Depending on whether this is up your alley either look for a MSSP/MDR/Managed BlaBla provider or head on to - https://github.com/splunk/security_content - https://www.elastic.co/guide/en/security/current/prebuilt-rules.html - https://github.com/mdecrevoisier/SIGMA-detection-rules - https://github.com/Azure/Azure-Sentinel to get an idea of what to look for. MITRE ATT&CK and the related DETT&CT should serve as an additional eye opener. Ah yes - forgot the bible on log management from Anton Chuvakin in the above list.

LOLBAS

Posts with mentions or reviews of LOLBAS. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-05.

What are some alternatives?

When comparing SIGMA-detection-rules and LOLBAS you can also consider the following projects:

EVTX-to-MITRE-Attack - Set of EVTX samples (>270) mapped to MITRE ATT&CK tactic and techniques to measure your SIEM coverage or developed new use cases.

UltimateAppLockerByPassList - The goal of this repository is to document the most common techniques to bypass AppLocker.

Azure-Sentinel - Cloud-native SIEM for intelligent security analytics for your entire enterprise.

GoodHound - Uses Sharphound, Bloodhound and Neo4j to produce an actionable list of attack paths for targeted remediation.

security_content - Splunk Security Content

purple-team-exercise-framework - Purple Team Exercise Framework

gitlab-watchman - Finding exposed secrets and personal data in GitLab

slack-watchman - Slack enumeration and exposed secrets detection tool

LOLDrivers - Living Off The Land Drivers

LOOBins - Living Off the Orchard: macOS Binaries (LOOBins) is designed to provide detailed information on various built-in "living off the land" macOS binaries and how they can be used by threat actors for malicious purposes.