Skip to content
KitploitKITPLOIT
उपकरणएक्सप्लॉइटब्लॉग
Log in
जमा करें
उपकरणएक्सप्लॉइटब्लॉग
जमा करें

हैकिंग, पेनटेस्ट और साइबर सुरक्षा उपकरण आपके सुरक्षा शस्त्रागार के लिए!

Kitploit हैकिंग, साइबर सुरक्षा और पेंटेस्टिंग टूल्स की एक निर्देशिका है। कमजोरियों को खोजने, सिस्टम का विश्लेषण करने, परीक्षण को स्वचालित करने और अपनी सुरक्षा को मजबूत करने के लिए नवीनतम प्रोजेक्ट अपडेट खोजें।

फ़ीडसंपर्कगोपनीयता© 2026 Kitploit

टूल निर्देशिका

श्रेणियाँ

सभी श्रेणियाँ देखें
Loading categories
TLDR — Sigma-based detection rules, log queries, atomic tests, and response procedures for monitoring and threat hunting in GitLab environments. | Kitploit
उपकरण/GitLabGitLab/gitlab-security-oss/tldr
Defensive ToolsIntrusion DetectionLearning & EducationIncident ResponseCurated ResourcesLog Analysis
GitLabgitlab-security-oss/tldr

TLDR

Sigma-based detection rules, log queries, atomic tests, and response procedures for monitoring and threat hunting in GitLab environments.

रिपॉजिटरी देखें
311146 दिन पहलेअभी तक समीक्षित नहीं
साझा करें
अनुरोधित भाषा में सामग्री उपलब्ध नहीं है। अंग्रेज़ी संस्करण दिखाया जा रहा है।

TLDR Framework

About

TLDR (Threat, Logs, Detection, Respond) is a public collection of security detections for GitLab. Each detection is one Markdown file that explains the threat, shows the log events it produces, gives a Sigma rule, and says what to do when it fires.

The repository answers the questions you ask when something happens on a GitLab instance, in your words:

  • A GitLab security advisory landed: am I exposed (which versions, which offering and tier)?
  • Would I see it (which logs carry the signal, and is that log available to me)?
  • What do I deploy (a Sigma rule you can convert for your SIEM, and a raw query for when you have none)?
  • What do I do when it fires (response steps)?

Who this is for

  • Administrators of self-managed and GitLab Dedicated instances, who can collect the application, API, audit and Workhorse logs.
  • Owners of GitLab.com groups on Ultimate, who can stream audit events to their own destination.
  • Detection engineers who convert Sigma rules to their SIEM's language.
  • Incident responders who need the threat, the log evidence and the response steps in one place.

How to navigate

There are two folders under Detections/platforms/GitLab/:

  • Threat Detections/: behaviour-based detections (for example a new administrator account, a deploy key created, silent mode enabled).
  • Vulnerability Detections/: detections tied to published CVEs, with the affected and fixed versions.

Every file starts with a small YAML frontmatter block that states the offering, tiers, log sources and (for vulnerabilities) the affected versions. index.yaml at the repository root (with an identical index.json) lists all 43 detections in one place, and is generated by scripts/build_index.py. The frontmatter schema is documented in docs/CONTRACT.md.

Starting from an advisory

The table below is generated from index.yaml (python scripts/build_index.py --readme README.md), and --check fails when it is stale. Detection files are listed by file name; the primary detection is the entry point for each CVE. CVE ranges are checked weekly against GitLab's CVE records; see the badge at the top of the project page. Each CVE also carries last_verified.

CVEfixed inprimary detectionother detections
CVE-2026-10543719.3.8, 19.4.6, 19.5.4git_merge_tree_child_process_crash
CVE-2026-11026418.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1org_mode_render_error_burstonigmo_native_worker_crash
CVE-2026-8570618.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2local_file_inclusion_path_enumerationlocal_file_inclusion_gitlab_yml_read, local_file_inclusion_metadata_path
CVE-2026-9357719.2.7, 19.3.3, 19.4.1ci_lint_workhorse_worker_crashci_lint_scripted_client_error_burst, ci_regexp_guard_rejection, graphql_cilint_hostile_regexp, onigmo_native_worker_crash
CVE-2026-9722919.2.8, 19.3.5, 19.4.2ci_lint_workhorse_worker_crashci_lint_scripted_client_error_burst, ci_regexp_guard_rejection, ci_regexp_oversized_non_ascii_path, graphql_cilint_hostile_regexp, onigmo_native_worker_crash

Self-managed vs GitLab.com

What you can detect depends on what you can collect.

  • Self-managed and Dedicated: you can read the application logs on the host or in your cluster (production_json, api_json, application_json, graphql_json, exceptions_json, audit_json, Workhorse, Puma). Both folders apply.
  • GitLab.com: you do not have host logs. The only source is audit events streamed to a destination you control, which requires an Ultimate group. Only detections whose frontmatter lists saas in offering apply, and they read audit events only. Streamed events use event_type where audit_json.log uses event_name, so field names differ.

The log source names, paths and availability are in docs/CONTRACT.md. For GitLab's own documentation, see audit event streaming and GitLab logs.

Structure of a detection

Each TLDR detection starts with frontmatter (offering, tier, log sources, scenarios, and for vulnerabilities the CVEs and affected versions) followed by this structure:

  1. About: Overview of the threat
  2. Threat Details:
    • Technical Details/Impact
    • Business Impact
  3. Logs:
    • Required log sources
    • Sample event logs
  4. Detection:
    • SIGMA rule or equivalent
    • Raw Log Query (for environments without SIEM)
  5. Atomic Test: Instructions to reproduce the threat for testing
  6. Response: Guidance on handling the detected threat
  7. References: Additional resources and documentation

For a sample TLDR detection, see Maintainer or Owner Permission Added to a Project.

टूल डाउनलोड करें

सबसे लोकप्रिय

सभी देखें →

हमारे समुदाय द्वारा सबसे अधिक उपयोग किए जाने वाले उपकरण खोजें।

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 अंतिम OSINT टूलकिट: जाँच ग्राफ़, विश्वास स्कोरिंग, उपनाम परिवार, मानचित्र, टाइमलाइन और रिपोर्ट। 49 मॉड्यूल, 400+ साइटें, किसी API कुंजी की आवश्यकता नहीं।

    668
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # घोस्टलॉक वन-टैप निष्पादन ऐप (CVE-2026-43499)

    496
  • 3

    ARTEX

    baarai/artex

    प्लानर/वर्कर एजेंट, एसेट और एक्सप्लोरेशन ग्राफ़, MITM ट्रैफ़िक रिकॉर्डिंग, और भेद्यता पुनःपरीक्षण के साथ LLM मल्टी-एजेंट स्वायत्त पेनेट्रेशन टेस्टिंग प्लेटफ़ॉर्म।

    394
  • 4

    redforge

    cybersecurity91/redforge

    ब्राउज़र-साइड रेड टीम टूलकिट, जिसमें रेकॉन, पेलोड जनरेशन, क्रेडेंशियल हमलों, क्रिप्टो, एन्कोडिंग और एंगेजमेंट रिपोर्टिंग के लिए 102 ऑफ़लाइन टूल्स हैं।

    339
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI-मूल साइबरसुरक्षा के लिए कार्रवाई की प्रणाली—जहाँ इरादा नियंत्रित निष्पादन बन जाता है, साक्ष्य परिचालन स्मृति बन जाता है, और हर ऑपरेशन अगले को बेहतर बनाता है।

    258
  • 6

    antifox

    antifox-ai/antifox

    AI मल्टी-एजेंट स्वायत्त पेनेट्रेशन टेस्टिंग प्लेटफ़ॉर्म जो रेकॉन, अटैक-सरफ़ेस डिस्कवरी, एक्सप्लॉइटेशन वैलिडेशन और साक्ष्य-आधारित रिपोर्ट डिलीवरी संचालित करता है।

    254

सभी उपकरण खोजें

हमारे उपकरणों का संग्रह ब्राउज़ करें

सभी उपकरण देखें →