[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HDJS40MQNFA549SBAFNM8T":3,"skill-same:01M6HDJS40MQNFA549SBAFNM8T":114},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6HDJS40MQNFA549SBAFNM8T","configuring-windows-event-logging-for-detection",null,"Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and...","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"windows","for","event","detection","configuring windows event logging for detection","logging","T1059.001","endpoint-security","detection-engineering","windows-security","event-logging","audit-policy","audit","T1543.003","cm","creation","de","generate","advanced","cybersecurity","2026-11-10 10:12:30",false,"---\nname: configuring-windows-event-logging-for-detection\ndescription: Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and...\ndomain: cybersecurity\nsubdomain: endpoint-security\ntags:\n- endpoint\n- windows-security\n- event-logging\n- audit-policy\n- detection-engineering\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.PS-02\n- DE.CM-01\n- PR.IR-01\nmitre_attack:\n- T1685.005\n- T1059.001\n- T1053.005\n- T1047\n- T1543.003\ncategory: configuring-windows-event-logging-for-detection\n---\n# Configuring-Windows-Event-Logging-For-Detection\n\n## Overview\nConfigures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and object access to feed SIEM detection rules. Activates for requests involving Windows audit policy, event log configuration, security logging, or detection-oriented logging.\n\n\n# Configuring Windows Event Logging for Detection\n\n## When to Use\n\nUse this skill when:\n- Configuring Windows Advanced Audit Policy for security monitoring\n- Enabling process creation auditing with command line logging (Event 4688)\n- Setting up logon\u002Flogoff auditing for authentication monitoring\n- Sizing event log storage and forwarding to SIEM platforms\n\n**Do not use** for Sysmon configuration (separate skill) or Linux audit logging.\n\n## Prerequisites\n\n- Windows Server or Windows 10\u002F11 systems with Group Policy management access\n- Active Directory environment with Group Policy Object (GPO) creation privileges\n- SIEM platform configured to receive Windows Event Log forwarding\n- Understanding of Windows security event IDs and audit categories\n\n## Workflow\n\n### Step 1: Configure Advanced Audit Policy via GPO\n\n```\nComputer Configuration → Windows Settings → Security Settings\n  → Advanced Audit Policy Configuration → Audit Policies\n\nRecommended settings:\nAccount Logon:\n  - Audit Credential Validation: Success, Failure\n  - Audit Kerberos Authentication: Success, Failure\n\nAccount Management:\n  - Audit Security Group Management: Success\n  - Audit User Account Management: Success, Failure\n\nLogon\u002FLogoff:\n  - Audit Logon: Success, Failure\n  - Audit Logoff: Success\n  - Audit Special Logon: Success\n  - Audit Other Logon\u002FLogoff Events: Success, Failure\n\nObject Access:\n  - Audit File Share: Success, Failure\n  - Audit Removable Storage: Success, Failure\n  - Audit SAM: Success\n\nPolicy Change:\n  - Audit Audit Policy Change: Success, Failure\n  - Audit Authentication Policy Change: Success\n\nPrivilege Use:\n  - Audit Sensitive Privilege Use: Success, Failure\n\nDetailed Tracking:\n  - Audit Process Creation: Success\n  - Audit DPAPI Activity: Success, Failure\n```\n\n### Step 2: Enable Command Line in Process Creation Events\n\n```powershell\n# Registry: Enable command line logging in Event 4688\nNew-ItemProperty -Path \"HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Audit\" `\n  -Name ProcessCreationIncludeCmdLine_Enabled -Value 1 -PropertyType DWORD -Force\n\n# GPO: Computer Configuration → Administrative Templates → System → Audit Process Creation\n# \"Include command line in process creation events\" → Enabled\n```\n\n### Step 3: Configure Event Log Sizes\n\n```powershell\n# Increase Security log to 1 GB (default 20 MB is insufficient)\nwevtutil sl Security \u002Fms:1073741824\n\n# Increase PowerShell Operational log\nwevtutil sl \"Microsoft-Windows-PowerShell\u002FOperational\" \u002Fms:536870912\n\n# Set log retention to overwrite as needed\nwevtutil sl Security \u002Frt:false\n\n# Configure via GPO:\n# Computer Configuration → Administrative Templates → Windows Components\n#   → Event Log Service → Security\n# Maximum log file size (KB): 1048576\n```\n\n### Step 4: Configure Windows Event Forwarding (WEF)\n\n```powershell\n# On collector server:\nwecutil qc \u002Fq\n\n# Create subscription for high-value events:\n# Event IDs: 4624 (logon), 4625 (failed logon), 4688 (process create),\n# 4672 (special privilege), 4720 (user created), 4728 (group membership),\n# 7045 (service installed), 1102 (log cleared)\n\n# On source endpoints (GPO):\n# Configure WinRM: winrm quickconfig\n# Configure event forwarding: Computer Configuration → Admin Templates\n#   → Windows Components → Event Forwarding\n# Configure target Subscription Manager: Server=http:\u002F\u002Fcollector:5985\u002Fwsman\u002FSubscriptionManager\u002FWEC\n```\n\n### Step 5: Key Event IDs for Detection\n\n```\nAuthentication Events:\n  4624 - Successful logon (Type 2=Interactive, 3=Network, 10=RemoteInteractive)\n  4625 - Failed logon attempt\n  4648 - Logon using explicit credentials (RunAs, pass-the-hash indicator)\n  4672 - Special privileges assigned (admin logon)\n  4776 - NTLM credential validation\n\nProcess Events:\n  4688 - Process creation (with command line if enabled)\n  4689 - Process termination\n\nAccount Events:\n  4720 - User account created\n  4722 - User account enabled\n  4724 - Password reset attempted\n  4728 - Member added to security group\n  4732 - Member added to local group\n  4756 - Member added to universal group\n\nService\u002FSystem Events:\n  7045 - New service installed (persistence indicator)\n  1102 - Audit log cleared (evidence tampering)\n  4697 - Service installed in the system\n\nLateral Movement Indicators:\n  4648 + 4624(Type 3) - Credential-based lateral movement\n  5140 - Network share accessed\n  5145 - Network share access check (detailed file share)\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Advanced Audit Policy** | Granular audit subcategories (58 subcategories vs. 9 basic categories) |\n| **Event ID 4688** | Process creation event; essential for tracking execution on endpoints |\n| **WEF** | Windows Event Forwarding; centralized log collection without third-party agents |\n| **Logon Type** | Numeric code indicating authentication method (2=interactive, 3=network, 10=RDP) |\n\n## Tools & Systems\n\n- **Windows Event Forwarding (WEF)**: Built-in centralized log collection\n- **NXLog**: Open-source log forwarding agent for Windows events\n- **Winlogbeat**: Elastic Agent for shipping Windows event logs to Elasticsearch\n- **Palantir WEF Configuration**: Open-source WEF subscription templates\n\n## Common Pitfalls\n\n- **Using basic audit policy instead of advanced**: Basic and advanced audit policies conflict. Always use advanced audit policy exclusively.\n- **Default log size too small**: 20 MB Security log fills in minutes on busy servers. Set minimum 1 GB.\n- **Missing command line logging**: Event 4688 without command line content has minimal detection value. Always enable ProcessCreationIncludeCmdLine_Enabled.\n- **Not forwarding logs**: Local event logs are lost when endpoints are wiped by ransomware. Forward to centralized SIEM immediately.\n","# Configuring-Windows-Event-Logging-For-Detection\n\n## Overview\nConfigures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and object access to feed SIEM detection rules. Activates for requests involving Windows audit policy, event log configuration, security logging, or detection-oriented logging.\n\n\n# Configuring Windows Event Logging for Detection\n\n## When to Use\n\nUse this skill when:\n- Configuring Windows Advanced Audit Policy for security monitoring\n- Enabling process creation auditing with command line logging (Event 4688)\n- Setting up logon\u002Flogoff auditing for authentication monitoring\n- Sizing event log storage and forwarding to SIEM platforms\n\n**Do not use** for Sysmon configuration (separate skill) or Linux audit logging.\n\n## Prerequisites\n\n- Windows Server or Windows 10\u002F11 systems with Group Policy management access\n- Active Directory environment with Group Policy Object (GPO) creation privileges\n- SIEM platform configured to receive Windows Event Log forwarding\n- Understanding of Windows security event IDs and audit categories\n\n## Workflow\n\n### Step 1: Configure Advanced Audit Policy via GPO\n\n```\nComputer Configuration → Windows Settings → Security Settings\n  → Advanced Audit Policy Configuration → Audit Policies\n\nRecommended settings:\nAccount Logon:\n  - Audit Credential Validation: Success, Failure\n  - Audit Kerberos Authentication: Success, Failure\n\nAccount Management:\n  - Audit Security Group Management: Success\n  - Audit User Account Management: Success, Failure\n\nLogon\u002FLogoff:\n  - Audit Logon: Success, Failure\n  - Audit Logoff: Success\n  - Audit Special Logon: Success\n  - Audit Other Logon\u002FLogoff Events: Success, Failure\n\nObject Access:\n  - Audit File Share: Success, Failure\n  - Audit Removable Storage: Success, Failure\n  - Audit SAM: Success\n\nPolicy Change:\n  - Audit Audit Policy Change: Success, Failure\n  - Audit Authentication Policy Change: Success\n\nPrivilege Use:\n  - Audit Sensitive Privilege Use: Success, Failure\n\nDetailed Tracking:\n  - Audit Process Creation: Success\n  - Audit DPAPI Activity: Success, Failure\n```\n\n### Step 2: Enable Command Line in Process Creation Events\n\n```powershell\n# Registry: Enable command line logging in Event 4688\nNew-ItemProperty -Path \"HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Audit\" `\n  -Name ProcessCreationIncludeCmdLine_Enabled -Value 1 -PropertyType DWORD -Force\n\n# GPO: Computer Configuration → Administrative Templates → System → Audit Process Creation\n# \"Include command line in process creation events\" → Enabled\n```\n\n### Step 3: Configure Event Log Sizes\n\n```powershell\n# Increase Security log to 1 GB (default 20 MB is insufficient)\nwevtutil sl Security \u002Fms:1073741824\n\n# Increase PowerShell Operational log\nwevtutil sl \"Microsoft-Windows-PowerShell\u002FOperational\" \u002Fms:536870912\n\n# Set log retention to overwrite as needed\nwevtutil sl Security \u002Frt:false\n\n# Configure via GPO:\n# Computer Configuration → Administrative Templates → Windows Components\n#   → Event Log Service → Security\n# Maximum log file size (KB): 1048576\n```\n\n### Step 4: Configure Windows Event Forwarding (WEF)\n\n```powershell\n# On collector server:\nwecutil qc \u002Fq\n\n# Create subscription for high-value events:\n# Event IDs: 4624 (logon), 4625 (failed logon), 4688 (process create),\n# 4672 (special privilege), 4720 (user created), 4728 (group membership),\n# 7045 (service installed), 1102 (log cleared)\n\n# On source endpoints (GPO):\n# Configure WinRM: winrm quickconfig\n# Configure event forwarding: Computer Configuration → Admin Templates\n#   → Windows Components → Event Forwarding\n# Configure target Subscription Manager: Server=http:\u002F\u002Fcollector:5985\u002Fwsman\u002FSubscriptionManager\u002FWEC\n```\n\n### Step 5: Key Event IDs for Detection\n\n```\nAuthentication Events:\n  4624 - Successful logon (Type 2=Interactive, 3=Network, 10=RemoteInteractive)\n  4625 - Failed logon attempt\n  4648 - Logon using explicit credentials (RunAs, pass-the-hash indicator)\n  4672 - Special privileges assigned (admin logon)\n  4776 - NTLM credential validation\n\nProcess Events:\n  4688 - Process creation (with command line if enabled)\n  4689 - Process termination\n\nAccount Events:\n  4720 - User account created\n  4722 - User account enabled\n  4724 - Password reset attempted\n  4728 - Member added to security group\n  4732 - Member added to local group\n  4756 - Member added to universal group\n\nService\u002FSystem Events:\n  7045 - New service installed (persistence indicator)\n  1102 - Audit log cleared (evidence tampering)\n  4697 - Service installed in the system\n\nLateral Movement Indicators:\n  4648 + 4624(Type 3) - Credential-based lateral movement\n  5140 - Network share accessed\n  5145 - Network share access check (detailed file share)\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Advanced Audit Policy** | Granular audit subcategories (58 subcategories vs. 9 basic categories) |\n| **Event ID 4688** | Process creation event; essential for tracking execution on endpoints |\n| **WEF** | Windows Event Forwarding; centralized log collection without third-party agents |\n| **Logon Type** | Numeric code indicating authentication method (2=interactive, 3=network, 10=RDP) |\n\n## Tools & Systems\n\n- **Windows Event Forwarding (WEF)**: Built-in centralized log collection\n- **NXLog**: Open-source log forwarding agent for Windows events\n- **Winlogbeat**: Elastic Agent for shipping Windows event logs to Elasticsearch\n- **Palantir WEF Configuration**: Open-source WEF subscription templates\n\n## Common Pitfalls\n\n- **Using basic audit policy instead of advanced**: Basic and advanced audit policies conflict. Always use advanced audit policy exclusively.\n- **Default log size too small**: 20 MB Security log fills in minutes on busy servers. Set minimum 1 GB.\n- **Missing command line logging**: Event 4688 without command line content has minimal detection value. Always enable ProcessCreationIncludeCmdLine_Enabled.\n- **Not forwarding logs**: Local event logs are lost when endpoints are wiped by ransomware. Forward to centralized SIEM immediately.\n",{"name":5,"tags":44,"author":46,"domain":38,"license":15,"version":47,"category":5,"nist_csf":48,"subdomain":26,"description":7,"mitre_attack":53},[45,28,29,30,27],"endpoint","mahipal","1.0.0",[49,50,51,52],"PR.PS-01","PR.PS-02","DE.CM-01","PR.IR-01",[54,25,55,56,32],"T1685.005","T1053.005","T1047","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fconfiguring-windows-event-logging-for-detection",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill configuring-windows-event-logging-for-detection",{"tool":71,"command":72},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill configuring-windows-event-logging-for-detection",{"tool":74,"command":75},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill configuring-windows-event-logging-for-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002FSKILL.md",true,[79,85,90,96,100,104,110],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Ftemplate.md","ASSET","资产文件",508,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002Fassets\u002Ftemplate.md",{"path":86,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002FLICENSE",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fapi-reference.md","REFERENCE","参考文档",1567,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002Freferences\u002Fapi-reference.md",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fstandards.md",391,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002Freferences\u002Fstandards.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fworkflows.md",349,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002Freferences\u002Fworkflows.md",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Fagent.py","SCRIPT","脚本",5816,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002Fscripts\u002Fagent.py",{"path":111,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fprocess.py",2043,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconfiguring-windows-event-logging-for-detection\u002Fscripts\u002Fprocess.py",[115,144,170,193,209,228],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":126,"publishedAt":39},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[127,128,129,130,20,131,38,132,133,134,135,136,22,137,138,139,140,141,142,143],"integrity","backup","recovery","validating backup integrity for recovery","testing","validate","verification","hash-verification","incident-response","ransomware","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":39},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[151,152,153,154,155,38,156,157,158,159,160,161,162,163,164,165,166,167,168,169],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":39},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[177,178,141,38,179,180,181,137,138,182,183,184,185,186,187,188,189,190,191,192],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":39},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[177,200,201,178,141,155,38,202,180,135,203,204,137,138,205,183,165,206,207,208],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":39},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[177,216,217,218,219,220,38,221,222,223,180,224,137,225,226,227,186,33,141,35],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":234,"publishedAt":39},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[235,236,237,238,38,239,240,241,242,243,244,225,245,246,33,247,35,248,249,250],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]