[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADY4VPKEFWS7JFPGN28BWG":3,"skill-same:01M6ADY4VPKEFWS7JFPGN28BWG":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6ADY4VPKEFWS7JFPGN28BWG","building-detection-rules-with-sigma",null,"Builds vendor-agnostic detection rules using the Sigma rule format for threat detection across SIEM platforms including Splunk, Elastic, and Microsoft Sentinel. Use when creating portable detection logic from threat intelligence, mapping rules to MITRE ATT&CK techniques, or converting community Sigma rules into platform-specific queries using sigmac or pySigma backends.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36078,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-detection-rules-with-sigma\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"building detection rules with sigma","cybersecurity","siem","threat intelligence","web","microsoft","mitre-attack","soc","splunk","T1059.001","sigma","detection-rules","elastic","sentinel","2026-11-10 10:12:30",false,"---\nname: building-detection-rules-with-sigma\ndescription: 'Builds vendor-agnostic detection rules using the Sigma rule format for\n  threat detection across SIEM platforms including Splunk, Elastic, and Microsoft\n  Sentinel. Use when creating portable detection logic from threat intelligence, mapping\n  rules to MITRE ATT&CK techniques, or converting community Sigma rules into platform-specific\n  queries using sigmac or pySigma backends.\n\n  '\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- soc\n- sigma\n- detection-rules\n- siem\n- mitre-attack\n- splunk\n- elastic\n- sentinel\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- Execution Isolation\n- Process Termination\n- Hardware-based Process Isolation\n- Web Session Access Mediation\n- Process Suspension\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1059.001\n- T1003.001\n- T1055\n- T1053.005\n- T1547.001\n---\n# Building Detection Rules with Sigma\n\n## When to Use\n\nUse this skill when:\n- SOC engineers need to create detection rules portable across multiple SIEM platforms\n- Threat intelligence reports describe TTPs requiring new detection coverage\n- Existing vendor-specific rules need standardization into a shareable format\n- The team adopts Sigma as a detection-as-code standard in CI\u002FCD pipelines\n\n**Do not use** for real-time streaming detection (Sigma is for batch\u002Fscheduled searches) or when the target SIEM has native detection features that Sigma cannot express (e.g., Splunk RBA risk scoring).\n\n## Prerequisites\n\n- Python 3.8+ with `pySigma` and appropriate backend (`pySigma-backend-splunk`, `pySigma-backend-elasticsearch`, `pySigma-backend-microsoft365defender`)\n- Sigma rule repository cloned: `git clone https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma.git`\n- MITRE ATT&CK framework knowledge for technique mapping\n- Understanding of target SIEM log source field mappings\n\n## Workflow\n\n### Step 1: Define Detection Logic from Threat Intelligence\n\nStart with a threat report or ATT&CK technique. Example: detecting Mimikatz credential dumping (T1003.001 — LSASS Memory):\n\n```yaml\ntitle: Mimikatz Credential Dumping via LSASS Access\nid: 0d894093-71bc-43c3-8d63-bf520e73a7c5\nstatus: stable\nlevel: high\ndescription: Detects process accessing lsass.exe memory, indicative of credential dumping tools like Mimikatz\nreferences:\n    - https:\u002F\u002Fattack.mitre.org\u002Ftechniques\u002FT1003\u002F001\u002F\n    - https:\u002F\u002Fgithub.com\u002Fgentilkiwi\u002Fmimikatz\nauthor: mahipal\ndate: 2024\u002F03\u002F15\nmodified: 2024\u002F03\u002F15\ntags:\n    - attack.credential_access\n    - attack.t1003.001\nlogsource:\n    category: process_access\n    product: windows\ndetection:\n    selection:\n        TargetImage|endswith: '\\lsass.exe'\n        GrantedAccess|contains:\n            - '0x1010'\n            - '0x1038'\n            - '0x1fffff'\n            - '0x40'\n    filter_main_svchost:\n        SourceImage|endswith: '\\svchost.exe'\n    filter_main_csrss:\n        SourceImage|endswith: '\\csrss.exe'\n    filter_main_wininit:\n        SourceImage|endswith: '\\wininit.exe'\n    condition: selection and not 1 of filter_main_*\nfalsepositives:\n    - Legitimate security tools accessing LSASS\n    - Windows Defender scanning\n    - CrowdStrike Falcon sensor\n```\n\n### Step 2: Validate Sigma Rule Syntax\n\nUse `sigma check` to validate the rule:\n\n```bash\n# Install pySigma and validators\npip install pySigma pySigma-validators-sigmaHQ\n\n# Validate rule\nsigma check rule.yml\n```\n\nAlternatively, validate with Python:\n\n```python\nfrom sigma.rule import SigmaRule\nfrom sigma.validators.core import SigmaValidator\n\nrule = SigmaRule.from_yaml(open(\"rule.yml\").read())\nvalidator = SigmaValidator()\nissues = validator.validate_rule(rule)\nfor issue in issues:\n    print(f\"{issue.severity}: {issue.message}\")\n```\n\n### Step 3: Convert to Target SIEM Query\n\n**Convert to Splunk SPL:**\n\n```python\nfrom sigma.rule import SigmaRule\nfrom sigma.backends.splunk import SplunkBackend\nfrom sigma.pipelines.splunk import splunk_windows_pipeline\n\npipeline = splunk_windows_pipeline()\nbackend = SplunkBackend(pipeline)\n\nrule = SigmaRule.from_yaml(open(\"rule.yml\").read())\nsplunk_query = backend.convert_rule(rule)\nprint(splunk_query[0])\n```\n\nOutput:\n```spl\nTargetImage=\"*\\\\lsass.exe\" (GrantedAccess=\"*0x1010*\" OR GrantedAccess=\"*0x1038*\"\nOR GrantedAccess=\"*0x1fffff*\" OR GrantedAccess=\"*0x40*\")\nNOT (SourceImage=\"*\\\\svchost.exe\") NOT (SourceImage=\"*\\\\csrss.exe\")\nNOT (SourceImage=\"*\\\\wininit.exe\")\n```\n\n**Convert to Elastic Query (Lucene):**\n\n```python\nfrom sigma.backends.elasticsearch import LuceneBackend\nfrom sigma.pipelines.elasticsearch import ecs_windows_pipeline\n\npipeline = ecs_windows_pipeline()\nbackend = LuceneBackend(pipeline)\nelastic_query = backend.convert_rule(rule)\nprint(elastic_query[0])\n```\n\n**Convert to Microsoft Sentinel KQL:**\n\n```python\nfrom sigma.backends.microsoft365defender import Microsoft365DefenderBackend\n\nbackend = Microsoft365DefenderBackend()\nkql_query = backend.convert_rule(rule)\nprint(kql_query[0])\n```\n\n### Step 4: Map to MITRE ATT&CK and Add Coverage Metadata\n\nTag every rule with ATT&CK technique IDs in the `tags` field:\n\n```yaml\ntags:\n    - attack.credential_access        # Tactic\n    - attack.t1003.001                # Sub-technique\n    - attack.t1003                    # Parent technique\n```\n\nTrack detection coverage using the ATT&CK Navigator:\n\n```python\nimport json\n\n# Generate ATT&CK Navigator layer from Sigma rules\nlayer = {\n    \"name\": \"SOC Detection Coverage\",\n    \"versions\": {\"attack\": \"14\", \"navigator\": \"4.9\", \"layer\": \"4.5\"},\n    \"domain\": \"enterprise-attack\",\n    \"techniques\": []\n}\n\n# Parse Sigma rules directory for technique tags\nimport os\nfrom sigma.rule import SigmaRule\n\nfor root, dirs, files in os.walk(\"sigma\u002Frules\u002Fwindows\u002F\"):\n    for f in files:\n        if f.endswith(\".yml\"):\n            rule = SigmaRule.from_yaml(open(os.path.join(root, f)).read())\n            for tag in rule.tags:\n                if str(tag).startswith(\"attack.t\"):\n                    technique_id = str(tag).replace(\"attack.\", \"\").upper()\n                    layer[\"techniques\"].append({\n                        \"techniqueID\": technique_id,\n                        \"color\": \"#31a354\",\n                        \"score\": 1\n                    })\n\nwith open(\"coverage_layer.json\", \"w\") as f:\n    json.dump(layer, f, indent=2)\n```\n\n### Step 5: Test Rule Against Sample Data\n\nCreate test data and validate the rule catches the expected events:\n\n```bash\n# Use sigma test framework\nsigma test rule.yml --target splunk --pipeline splunk_windows\n\n# Or manually test in Splunk with sample data\n# Upload Sysmon process_access log with known Mimikatz signature\n```\n\nValidate false positive rate by running against 7 days of production data in a non-alerting saved search.\n\n### Step 6: Deploy to Production SIEM\n\nDeploy the converted query as a scheduled search or correlation rule:\n\n**Splunk ES Correlation Search:**\n```spl\n| tstats summariesonly=true count from datamodel=Endpoint.Processes\n  where Processes.process_name=\"*\\\\lsass.exe\"\n  by Processes.src, Processes.user, Processes.process_name, Processes.parent_process_name\n| `drop_dm_object_name(Processes)`\n| where count > 0\n```\n\n**Elastic Security Rule (TOML format):**\n```toml\n[rule]\nname = \"LSASS Memory Access - Credential Dumping\"\ndescription = \"Detects suspicious access to LSASS process memory\"\nrisk_score = 73\nseverity = \"high\"\ntype = \"eql\"\nquery = '''\nprocess where event.action == \"access\" and\n  process.name == \"lsass.exe\" and\n  not process.executable : (\"*\\\\svchost.exe\", \"*\\\\csrss.exe\")\n'''\n\n[rule.threat]\nframework = \"MITRE ATT&CK\"\n[[rule.threat.technique]]\nid = \"T1003\"\nname = \"OS Credential Dumping\"\n```\n\n### Step 7: Version Control and CI\u002FCD Integration\n\nStore rules in Git with automated testing:\n\n```yaml\n# .github\u002Fworkflows\u002Fsigma-ci.yml\nname: Sigma Rule CI\non: [push, pull_request]\njobs:\n  validate:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-python@v5\n        with:\n          python-version: '3.11'\n      - run: pip install pySigma pySigma-validators-sigmaHQ\n      - run: sigma check rules\u002F\n      - run: sigma convert -t splunk -p splunk_windows rules\u002F > \u002Fdev\u002Fnull\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Sigma** | Vendor-agnostic detection rule format (YAML-based) that compiles to SIEM-specific queries via backends |\n| **pySigma** | Python library replacing legacy sigmac for rule conversion, validation, and pipeline processing |\n| **Backend** | pySigma plugin that translates Sigma detection logic into a target platform query language (SPL, KQL, Lucene) |\n| **Pipeline** | Field mapping configuration that translates generic Sigma field names to SIEM-specific field names |\n| **Logsource** | Sigma rule section defining the category (process_creation, network_connection) and product (windows, linux) of the target data |\n| **Detection-as-Code** | Practice of managing detection rules in version control with CI\u002FCD testing and automated deployment |\n\n## Tools & Systems\n\n- **SigmaHQ**: Official Sigma rule repository with 3,000+ community-maintained detection rules on GitHub\n- **pySigma**: Python-based Sigma rule processing framework with modular backends and pipelines\n- **ATT&CK Navigator**: MITRE tool for visualizing detection coverage mapped to ATT&CK techniques\n- **Uncoder.IO**: Web-based Sigma rule converter supporting 30+ SIEM platforms for quick translation\n\n## Common Scenarios\n\n- **New CVE Detection**: Write Sigma rule for exploitation indicators (e.g., Log4Shell JNDI lookup patterns in web logs)\n- **Hunting Rule Promotion**: Convert ad-hoc Splunk hunting query into Sigma rule for ongoing automated detection\n- **Multi-SIEM Migration**: Converting 500+ Splunk correlation searches to Sigma for migration to Elastic Security\n- **Purple Team Output**: Convert red team findings into Sigma rules for immediate defensive coverage\n- **Threat Intel Operationalization**: Transform IOC-based threat reports into behavioral Sigma rules\n\n## Output Format\n\n```\nSIGMA RULE DEPLOYMENT REPORT\n━━━━━━━━━━━━━━━━━━━━━━━━━━━\nRule ID:      0d894093-71bc-43c3-8d63-bf520e73a7c5\nTitle:        Mimikatz Credential Dumping via LSASS Access\nATT&CK:       T1003.001 - LSASS Memory\nSeverity:     High\nStatus:       Deployed to Production\n\nConversions:\n  Splunk SPL:    PASS — Saved search \"sigma_lsass_access\" created\n  Elastic EQL:   PASS — Detection rule ID elastic-0d894093 enabled\n  Sentinel KQL:  PASS — Analytics rule deployed via ARM template\n\nTesting:\n  True Positives:    4\u002F4 test cases matched\n  False Positives:   2 in 7-day backtest (svchost edge case — filter added)\n  Performance:       Avg execution 3.2s on 50M events\u002Fday\n```\n","# Building Detection Rules with Sigma\n\n## When to Use\n\nUse this skill when:\n- SOC engineers need to create detection rules portable across multiple SIEM platforms\n- Threat intelligence reports describe TTPs requiring new detection coverage\n- Existing vendor-specific rules need standardization into a shareable format\n- The team adopts Sigma as a detection-as-code standard in CI\u002FCD pipelines\n\n**Do not use** for real-time streaming detection (Sigma is for batch\u002Fscheduled searches) or when the target SIEM has native detection features that Sigma cannot express (e.g., Splunk RBA risk scoring).\n\n## Prerequisites\n\n- Python 3.8+ with `pySigma` and appropriate backend (`pySigma-backend-splunk`, `pySigma-backend-elasticsearch`, `pySigma-backend-microsoft365defender`)\n- Sigma rule repository cloned: `git clone https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma.git`\n- MITRE ATT&CK framework knowledge for technique mapping\n- Understanding of target SIEM log source field mappings\n\n## Workflow\n\n### Step 1: Define Detection Logic from Threat Intelligence\n\nStart with a threat report or ATT&CK technique. Example: detecting Mimikatz credential dumping (T1003.001 — LSASS Memory):\n\n```yaml\ntitle: Mimikatz Credential Dumping via LSASS Access\nid: 0d894093-71bc-43c3-8d63-bf520e73a7c5\nstatus: stable\nlevel: high\ndescription: Detects process accessing lsass.exe memory, indicative of credential dumping tools like Mimikatz\nreferences:\n    - https:\u002F\u002Fattack.mitre.org\u002Ftechniques\u002FT1003\u002F001\u002F\n    - https:\u002F\u002Fgithub.com\u002Fgentilkiwi\u002Fmimikatz\nauthor: mahipal\ndate: 2024\u002F03\u002F15\nmodified: 2024\u002F03\u002F15\ntags:\n    - attack.credential_access\n    - attack.t1003.001\nlogsource:\n    category: process_access\n    product: windows\ndetection:\n    selection:\n        TargetImage|endswith: '\\lsass.exe'\n        GrantedAccess|contains:\n            - '0x1010'\n            - '0x1038'\n            - '0x1fffff'\n            - '0x40'\n    filter_main_svchost:\n        SourceImage|endswith: '\\svchost.exe'\n    filter_main_csrss:\n        SourceImage|endswith: '\\csrss.exe'\n    filter_main_wininit:\n        SourceImage|endswith: '\\wininit.exe'\n    condition: selection and not 1 of filter_main_*\nfalsepositives:\n    - Legitimate security tools accessing LSASS\n    - Windows Defender scanning\n    - CrowdStrike Falcon sensor\n```\n\n### Step 2: Validate Sigma Rule Syntax\n\nUse `sigma check` to validate the rule:\n\n```bash\n# Install pySigma and validators\npip install pySigma pySigma-validators-sigmaHQ\n\n# Validate rule\nsigma check rule.yml\n```\n\nAlternatively, validate with Python:\n\n```python\nfrom sigma.rule import SigmaRule\nfrom sigma.validators.core import SigmaValidator\n\nrule = SigmaRule.from_yaml(open(\"rule.yml\").read())\nvalidator = SigmaValidator()\nissues = validator.validate_rule(rule)\nfor issue in issues:\n    print(f\"{issue.severity}: {issue.message}\")\n```\n\n### Step 3: Convert to Target SIEM Query\n\n**Convert to Splunk SPL:**\n\n```python\nfrom sigma.rule import SigmaRule\nfrom sigma.backends.splunk import SplunkBackend\nfrom sigma.pipelines.splunk import splunk_windows_pipeline\n\npipeline = splunk_windows_pipeline()\nbackend = SplunkBackend(pipeline)\n\nrule = SigmaRule.from_yaml(open(\"rule.yml\").read())\nsplunk_query = backend.convert_rule(rule)\nprint(splunk_query[0])\n```\n\nOutput:\n```spl\nTargetImage=\"*\\\\lsass.exe\" (GrantedAccess=\"*0x1010*\" OR GrantedAccess=\"*0x1038*\"\nOR GrantedAccess=\"*0x1fffff*\" OR GrantedAccess=\"*0x40*\")\nNOT (SourceImage=\"*\\\\svchost.exe\") NOT (SourceImage=\"*\\\\csrss.exe\")\nNOT (SourceImage=\"*\\\\wininit.exe\")\n```\n\n**Convert to Elastic Query (Lucene):**\n\n```python\nfrom sigma.backends.elasticsearch import LuceneBackend\nfrom sigma.pipelines.elasticsearch import ecs_windows_pipeline\n\npipeline = ecs_windows_pipeline()\nbackend = LuceneBackend(pipeline)\nelastic_query = backend.convert_rule(rule)\nprint(elastic_query[0])\n```\n\n**Convert to Microsoft Sentinel KQL:**\n\n```python\nfrom sigma.backends.microsoft365defender import Microsoft365DefenderBackend\n\nbackend = Microsoft365DefenderBackend()\nkql_query = backend.convert_rule(rule)\nprint(kql_query[0])\n```\n\n### Step 4: Map to MITRE ATT&CK and Add Coverage Metadata\n\nTag every rule with ATT&CK technique IDs in the `tags` field:\n\n```yaml\ntags:\n    - attack.credential_access        # Tactic\n    - attack.t1003.001                # Sub-technique\n    - attack.t1003                    # Parent technique\n```\n\nTrack detection coverage using the ATT&CK Navigator:\n\n```python\nimport json\n\n# Generate ATT&CK Navigator layer from Sigma rules\nlayer = {\n    \"name\": \"SOC Detection Coverage\",\n    \"versions\": {\"attack\": \"14\", \"navigator\": \"4.9\", \"layer\": \"4.5\"},\n    \"domain\": \"enterprise-attack\",\n    \"techniques\": []\n}\n\n# Parse Sigma rules directory for technique tags\nimport os\nfrom sigma.rule import SigmaRule\n\nfor root, dirs, files in os.walk(\"sigma\u002Frules\u002Fwindows\u002F\"):\n    for f in files:\n        if f.endswith(\".yml\"):\n            rule = SigmaRule.from_yaml(open(os.path.join(root, f)).read())\n            for tag in rule.tags:\n                if str(tag).startswith(\"attack.t\"):\n                    technique_id = str(tag).replace(\"attack.\", \"\").upper()\n                    layer[\"techniques\"].append({\n                        \"techniqueID\": technique_id,\n                        \"color\": \"#31a354\",\n                        \"score\": 1\n                    })\n\nwith open(\"coverage_layer.json\", \"w\") as f:\n    json.dump(layer, f, indent=2)\n```\n\n### Step 5: Test Rule Against Sample Data\n\nCreate test data and validate the rule catches the expected events:\n\n```bash\n# Use sigma test framework\nsigma test rule.yml --target splunk --pipeline splunk_windows\n\n# Or manually test in Splunk with sample data\n# Upload Sysmon process_access log with known Mimikatz signature\n```\n\nValidate false positive rate by running against 7 days of production data in a non-alerting saved search.\n\n### Step 6: Deploy to Production SIEM\n\nDeploy the converted query as a scheduled search or correlation rule:\n\n**Splunk ES Correlation Search:**\n```spl\n| tstats summariesonly=true count from datamodel=Endpoint.Processes\n  where Processes.process_name=\"*\\\\lsass.exe\"\n  by Processes.src, Processes.user, Processes.process_name, Processes.parent_process_name\n| `drop_dm_object_name(Processes)`\n| where count > 0\n```\n\n**Elastic Security Rule (TOML format):**\n```toml\n[rule]\nname = \"LSASS Memory Access - Credential Dumping\"\ndescription = \"Detects suspicious access to LSASS process memory\"\nrisk_score = 73\nseverity = \"high\"\ntype = \"eql\"\nquery = '''\nprocess where event.action == \"access\" and\n  process.name == \"lsass.exe\" and\n  not process.executable : (\"*\\\\svchost.exe\", \"*\\\\csrss.exe\")\n'''\n\n[rule.threat]\nframework = \"MITRE ATT&CK\"\n[[rule.threat.technique]]\nid = \"T1003\"\nname = \"OS Credential Dumping\"\n```\n\n### Step 7: Version Control and CI\u002FCD Integration\n\nStore rules in Git with automated testing:\n\n```yaml\n# .github\u002Fworkflows\u002Fsigma-ci.yml\nname: Sigma Rule CI\non: [push, pull_request]\njobs:\n  validate:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-python@v5\n        with:\n          python-version: '3.11'\n      - run: pip install pySigma pySigma-validators-sigmaHQ\n      - run: sigma check rules\u002F\n      - run: sigma convert -t splunk -p splunk_windows rules\u002F > \u002Fdev\u002Fnull\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Sigma** | Vendor-agnostic detection rule format (YAML-based) that compiles to SIEM-specific queries via backends |\n| **pySigma** | Python library replacing legacy sigmac for rule conversion, validation, and pipeline processing |\n| **Backend** | pySigma plugin that translates Sigma detection logic into a target platform query language (SPL, KQL, Lucene) |\n| **Pipeline** | Field mapping configuration that translates generic Sigma field names to SIEM-specific field names |\n| **Logsource** | Sigma rule section defining the category (process_creation, network_connection) and product (windows, linux) of the target data |\n| **Detection-as-Code** | Practice of managing detection rules in version control with CI\u002FCD testing and automated deployment |\n\n## Tools & Systems\n\n- **SigmaHQ**: Official Sigma rule repository with 3,000+ community-maintained detection rules on GitHub\n- **pySigma**: Python-based Sigma rule processing framework with modular backends and pipelines\n- **ATT&CK Navigator**: MITRE tool for visualizing detection coverage mapped to ATT&CK techniques\n- **Uncoder.IO**: Web-based Sigma rule converter supporting 30+ SIEM platforms for quick translation\n\n## Common Scenarios\n\n- **New CVE Detection**: Write Sigma rule for exploitation indicators (e.g., Log4Shell JNDI lookup patterns in web logs)\n- **Hunting Rule Promotion**: Convert ad-hoc Splunk hunting query into Sigma rule for ongoing automated detection\n- **Multi-SIEM Migration**: Converting 500+ Splunk correlation searches to Sigma for migration to Elastic Security\n- **Purple Team Output**: Convert red team findings into Sigma rules for immediate defensive coverage\n- **Threat Intel Operationalization**: Transform IOC-based threat reports into behavioral Sigma rules\n\n## Output Format\n\n```\nSIGMA RULE DEPLOYMENT REPORT\n━━━━━━━━━━━━━━━━━━━━━━━━━━━\nRule ID:      0d894093-71bc-43c3-8d63-bf520e73a7c5\nTitle:        Mimikatz Credential Dumping via LSASS Access\nATT&CK:       T1003.001 - LSASS Memory\nSeverity:     High\nStatus:       Deployed to Production\n\nConversions:\n  Splunk SPL:    PASS — Saved search \"sigma_lsass_access\" created\n  Elastic EQL:   PASS — Detection rule ID elastic-0d894093 enabled\n  Sentinel KQL:  PASS — Analytics rule deployed via ARM template\n\nTesting:\n  True Positives:    4\u002F4 test cases matched\n  False Positives:   2 in 7-day backtest (svchost edge case — filter added)\n  Performance:       Avg execution 3.2s on 50M events\u002Fday\n```\n",{"name":5,"tags":43,"author":44,"domain":25,"license":15,"version":45,"nist_csf":46,"subdomain":51,"description":52,"mitre_attack":53,"d3fend_techniques":58},[31,34,35,26,30,32,36,37],"mahipal","1.0",[47,48,49,50],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations","Builds vendor-agnostic detection rules using the Sigma rule format for threat detection across SIEM platforms including Splunk, Elastic, and Microsoft Sentinel. Use when creating portable detection logic from threat intelligence, mapping rules to MITRE ATT&CK techniques, or converting community Sigma rules into platform-specific queries using sigmac or pySigma backends.\n",[33,54,55,56,57],"T1003.001","T1055","T1053.005","T1547.001",[59,60,61,62,63],"Execution Isolation","Process Termination","Hardware-based Process Isolation","Web Session Access Mediation","Process Suspension","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fbuilding-detection-rules-with-sigma",4414,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-detection-rules-with-sigma",{"tool":80,"command":81},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-detection-rules-with-sigma",{"tool":83,"command":84},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-detection-rules-with-sigma","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-detection-rules-with-sigma\u002FSKILL.md",true,[88,93,99],{"path":89,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-detection-rules-with-sigma\u002FLICENSE",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fapi-reference.md","REFERENCE","参考文档",2127,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-detection-rules-with-sigma\u002Freferences\u002Fapi-reference.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",6449,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-detection-rules-with-sigma\u002Fscripts\u002Fagent.py",[106,133,157,185,211,238],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":38},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[112],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,115,116,117,118,25,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","identity","pr","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":38},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[139],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[141,129,142,143,118,144,25,121,145,146,147,148,149,150,151,152,153,154,155,156],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":167,"publishedAt":38},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[163,166],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[151,168,169,170,171,25,172,173,145,174,175,176,177,178,179,180,181,182,183,184],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":38},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[191],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[193,194,195,25,196,197,198,199,200,201,202,203,204,205,206,207,148,208,209,210],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":38},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[217],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[219,220,221,25,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":239,"name":240,"nameZh":6,"description":241,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":242,"categories":243,"keywords":245,"publishedAt":38},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[244],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[118,246,25,26,247,248,31,249,250,251,252,180,253,181,254,255,256,257,258,259],"triaging security incident","file","ioc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]