should we write our own custom rule

This page summarizes the projects mentioned and recommended in the original post on /r/cybersecurity

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • SIGMA-detection-rules

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

  • 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.

  • LOLBAS

    Living Off The Land Binaries And Scripts - (LOLBins and LOLScripts)

  • Fo example the usage of living off the land binaries https://lolbas-project.github.io/ , when I've implemented rules in order to detect this ,I've seen a lot of false positive because of the context ,but the rule was correct.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts