[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AA2M2MVJ64K1A2EHZPWR0G":3,"skill-same:01M7AA2M2MVJ64K1A2EHZPWR0G":102},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7AA2M2MVJ64K1A2EHZPWR0G","performing-log-source-onboarding-in-siem",null,"Perform structured log source onboarding into SIEM platforms (Splunk, Elastic, Sentinel, QRadar, or similar) by prioritizing sources with a tiered value framework, configuring collectors, building parsers, normalizing fields to a common schema (e.g. CIM), and validating data quality. Use when planning or executing the integration of new log sources — such as Active Directory, firewalls, EDR, VPN, DNS, or cloud audit logs — into a SIEM for security monitoring and detection.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-log-source-onboarding-in-siem\ndescription: Perform structured log source onboarding into SIEM platforms (Splunk,\n  Elastic, Sentinel, QRadar, or similar) by prioritizing sources with a tiered value\n  framework, configuring collectors, building parsers, normalizing fields to a common\n  schema (e.g. CIM), and validating data quality. Use when planning or executing\n  the integration of new log sources — such as Active Directory, firewalls, EDR,\n  VPN, DNS, or cloud audit logs — into a SIEM for security monitoring and detection.\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- siem\n- log-onboarding\n- log-management\n- data-ingestion\n- parsing\n- normalization\n- soc\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1078\n- T1685.002\n- T1685.005\n- T1566\n---\n\n# Performing Log Source Onboarding in SIEM\n\n## Overview\n\nLog source onboarding is the systematic process of integrating new data sources into a SIEM platform to enable security monitoring and detection. Proper onboarding requires planning data sources, configuring collection agents, building parsers, normalizing fields to a common schema, and validating data quality. According to the UK NCSC, onboarding should prioritize log sources that provide the highest security value relative to their ingestion cost.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing log source onboarding in siem\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- SIEM platform deployed (Splunk, Elastic, Sentinel, QRadar, or similar)\n- Network access from source systems to SIEM collectors\n- Administrative access on source systems for agent installation\n- Common Information Model (CIM) or equivalent schema documentation\n- Change management approval for production system modifications\n\n## Log Source Priority Framework\n\n### Tier 1 - Critical (Onboard First)\n\n| Source | Log Type | Security Value |\n|---|---|---|\n| Active Directory | Security Event Logs | Authentication, privilege escalation |\n| Firewalls | Traffic logs | Network access, C2 detection |\n| EDR\u002FAV | Endpoint alerts | Malware, process execution |\n| VPN\u002FRemote Access | Connection logs | Unauthorized access |\n| DNS Servers | Query logs | C2 beaconing, data exfiltration |\n| Email Gateway | Email security logs | Phishing, BEC |\n\n### Tier 2 - High Priority\n\n| Source | Log Type | Security Value |\n|---|---|---|\n| Web Proxy | HTTP\u002FHTTPS logs | Web-based attacks, data exfiltration |\n| Cloud platforms (AWS\u002FAzure\u002FGCP) | Audit logs | Cloud security posture |\n| Database servers | Audit\u002Fquery logs | Data access, SQL injection |\n| DHCP\u002FIPAM | Address allocation | Asset tracking |\n| File servers | Access logs | Data access monitoring |\n\n### Tier 3 - Standard\n\n| Source | Log Type | Security Value |\n|---|---|---|\n| Application servers | App logs | Application-level attacks |\n| Print servers | Print logs | Data loss prevention |\n| Badge\u002Fphysical access | Access logs | Physical security correlation |\n| Network devices (switches\u002Frouters) | Syslog | Network anomalies |\n\n## Onboarding Process\n\n### Step 1: Discovery and Assessment\n\n```\n1. Identify the log source:\n   - System type and version\n   - Log format (syslog, CEF, JSON, Windows Events, etc.)\n   - Log volume estimate (EPS - events per second)\n   - Network location and firewall requirements\n\n2. Assess security value:\n   - What threats can this source help detect?\n   - Which MITRE ATT&CK techniques does it cover?\n   - Is there an existing SIEM parser?\n\n3. Estimate ingestion cost:\n   - Daily volume in GB\n   - License impact (per-GB or per-EPS pricing)\n   - Storage retention requirements\n```\n\n### Step 2: Configure Log Collection\n\n#### Syslog-Based Collection (Firewalls, Network Devices)\n\n```conf\n# rsyslog configuration for receiving syslog\n# \u002Fetc\u002Frsyslog.d\u002F10-siem-collection.conf\n\n# UDP reception\nmodule(load=\"imudp\")\ninput(type=\"imudp\" port=\"514\" ruleset=\"siem_forwarding\")\n\n# TCP reception\nmodule(load=\"imtcp\")\ninput(type=\"imtcp\" port=\"514\" ruleset=\"siem_forwarding\")\n\n# TLS reception\nmodule(load=\"imtcp\" StreamDriver.AuthMode=\"x509\u002Fname\"\n       StreamDriver.Mode=\"1\" StreamDriver.Name=\"gtls\")\ninput(type=\"imtcp\" port=\"6514\" ruleset=\"siem_forwarding\")\n\nruleset(name=\"siem_forwarding\") {\n    # Forward to SIEM\n    action(type=\"omfwd\" target=\"siem.company.com\" port=\"9514\"\n           protocol=\"tcp\" queue.type=\"LinkedList\"\n           queue.filename=\"siem_fwd\" queue.maxdiskspace=\"1g\"\n           queue.saveonshutdown=\"on\" action.resumeRetryCount=\"-1\")\n}\n```\n\n#### Windows Event Log Collection (Splunk Universal Forwarder)\n\n```conf\n# inputs.conf on Splunk Universal Forwarder\n[WinEventLog:\u002F\u002FSecurity]\ndisabled = 0\nindex = wineventlog\nsourcetype = WinEventLog:Security\nevt_resolve_ad_obj = 1\ncheckpointInterval = 5\n\n[WinEventLog:\u002F\u002FSystem]\ndisabled = 0\nindex = wineventlog\nsourcetype = WinEventLog:System\n\n[WinEventLog:\u002F\u002FMicrosoft-Windows-Sysmon\u002FOperational]\ndisabled = 0\nindex = wineventlog\nsourcetype = XmlWinEventLog:Microsoft-Windows-Sysmon\u002FOperational\nrenderXml = true\n\n[WinEventLog:\u002F\u002FMicrosoft-Windows-PowerShell\u002FOperational]\ndisabled = 0\nindex = wineventlog\nsourcetype = XmlWinEventLog:Microsoft-Windows-PowerShell\u002FOperational\n```\n\n#### Cloud Log Collection (AWS CloudTrail)\n\n```json\n{\n  \"AWSTemplateFormatVersion\": \"2010-09-09\",\n  \"Resources\": {\n    \"CloudTrailToSIEM\": {\n      \"Type\": \"AWS::CloudTrail::Trail\",\n      \"Properties\": {\n        \"TrailName\": \"siem-cloudtrail\",\n        \"S3BucketName\": \"company-cloudtrail-logs\",\n        \"IsLogging\": true,\n        \"IsMultiRegionTrail\": true,\n        \"IncludeGlobalServiceEvents\": true,\n        \"EnableLogFileValidation\": true,\n        \"EventSelectors\": [\n          {\n            \"ReadWriteType\": \"All\",\n            \"IncludeManagementEvents\": true,\n            \"DataResources\": [\n              {\n                \"Type\": \"AWS::S3::Object\",\n                \"Values\": [\"arn:aws:s3\"]\n              }\n            ]\n          }\n        ]\n      }\n    }\n  }\n}\n```\n\n### Step 3: Parse and Normalize\n\n#### Custom Parser Example (Splunk props.conf\u002Ftransforms.conf)\n\n```conf\n# props.conf\n[custom:firewall:logs]\nSHOULD_LINEMERGE = false\nLINE_BREAKER = ([\\r\\n]+)\nTIME_PREFIX = ^\nTIME_FORMAT = %Y-%m-%dT%H:%M:%S%z\nMAX_TIMESTAMP_LOOKAHEAD = 30\nTRANSFORMS-firewall = firewall_extract_fields\nFIELDALIAS-src = src_addr AS src_ip\nFIELDALIAS-dst = dst_addr AS dest_ip\nEVAL-action = case(fw_action==\"allow\", \"allowed\", fw_action==\"deny\", \"blocked\", true(), \"unknown\")\nEVAL-vendor_product = \"Custom Firewall\"\nLOOKUP-geo = geo_ip_lookup ip AS dest_ip OUTPUT country, city, latitude, longitude\n\n# transforms.conf\n[firewall_extract_fields]\nREGEX = ^(\\S+)\\s+(\\S+)\\s+action=(\\w+)\\s+src=(\\S+):(\\d+)\\s+dst=(\\S+):(\\d+)\\s+proto=(\\w+)\\s+bytes=(\\d+)\nFORMAT = timestamp::$1 hostname::$2 fw_action::$3 src_addr::$4 src_port::$5 dst_addr::$6 dst_port::$7 protocol::$8 bytes::$9\n```\n\n#### CIM Field Mapping\n\n| Raw Field | CIM Field | Data Model |\n|---|---|---|\n| src_addr | src_ip | Network_Traffic |\n| dst_addr | dest_ip | Network_Traffic |\n| dst_port | dest_port | Network_Traffic |\n| fw_action | action | Network_Traffic |\n| bytes_sent + bytes_recv | bytes | Network_Traffic |\n| user_name | user | Authentication |\n| login_result | action | Authentication |\n| process_path | process | Endpoint |\n\n### Step 4: Validate Data Quality\n\n```spl\n# Verify events are arriving\nindex=new_source earliest=-1h\n| stats count by sourcetype, host, source\n\n# Check field extraction quality\nindex=new_source earliest=-1h\n| stats count(src_ip) as has_src count(dest_ip) as has_dest count(action) as has_action count by sourcetype\n| eval src_coverage=round(has_src\u002Fcount*100,1)\n| eval dest_coverage=round(has_dest\u002Fcount*100,1)\n| eval action_coverage=round(has_action\u002Fcount*100,1)\n\n# Verify CIM compliance\n| datamodel Network_Traffic search\n| search sourcetype=new_sourcetype\n| stats count by source, sourcetype\n\n# Check for timestamp parsing issues\nindex=new_source earliest=-1h\n| eval time_diff=abs(_time - _indextime)\n| stats avg(time_diff) as avg_lag max(time_diff) as max_lag by host\n| where avg_lag > 300\n```\n\n### Step 5: Enable Detection Coverage\n\n```spl\n# Verify existing correlation searches work with new source\nindex=new_source sourcetype=new_sourcetype\n| tstats count from datamodel=Authentication by _time span=1h\n| timechart span=1h count\n\n# Create source-specific detection rule\n[New Source - Authentication Anomaly]\nsearch = index=new_source sourcetype=new_sourcetype action=failure \\\n| stats count by src_ip, user \\\n| where count > 10\n```\n\n## Onboarding Checklist\n\n- [ ] Log source assessed and approved\n- [ ] Network connectivity verified\n- [ ] Collection agent\u002Fmethod configured\n- [ ] Log forwarding confirmed\n- [ ] Parser\u002Ffield extraction configured\n- [ ] CIM compliance validated\n- [ ] Data model acceleration enabled\n- [ ] Volume within license budget\n- [ ] Retention policy configured\n- [ ] Detection rules enabled\u002Fcreated\n- [ ] Dashboard updated\n- [ ] Documentation completed\n- [ ] SOC team notified\n\n## References\n\n- [UK NCSC - Onboarding Systems and Log Sources](https:\u002F\u002Fwww.ncsc.gov.uk\u002Fcollection\u002Fbuilding-a-security-operations-centre\u002Fonboarding-systems-and-log-sources)\n- [Sumo Logic - Cloud SIEM Onboarding Checklist](https:\u002F\u002Fhelp.sumologic.com\u002Fdocs\u002Fcse\u002Fget-started-with-cloud-siem\u002Fonboarding-checklist-cse\u002F)\n- [SIEM Logging Best Practices - Coralogix](https:\u002F\u002Fcoralogix.com\u002Fguides\u002Fsiem\u002Fsiem-logging\u002F)\n- [Huntress - SIEM Implementation Guide](https:\u002F\u002Fwww.huntress.com\u002Fsiem-guide\u002Fsiem-implementation-guide)\n","# Performing Log Source Onboarding in SIEM\n\n## Overview\n\nLog source onboarding is the systematic process of integrating new data sources into a SIEM platform to enable security monitoring and detection. Proper onboarding requires planning data sources, configuring collection agents, building parsers, normalizing fields to a common schema, and validating data quality. According to the UK NCSC, onboarding should prioritize log sources that provide the highest security value relative to their ingestion cost.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing log source onboarding in siem\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- SIEM platform deployed (Splunk, Elastic, Sentinel, QRadar, or similar)\n- Network access from source systems to SIEM collectors\n- Administrative access on source systems for agent installation\n- Common Information Model (CIM) or equivalent schema documentation\n- Change management approval for production system modifications\n\n## Log Source Priority Framework\n\n### Tier 1 - Critical (Onboard First)\n\n| Source | Log Type | Security Value |\n|---|---|---|\n| Active Directory | Security Event Logs | Authentication, privilege escalation |\n| Firewalls | Traffic logs | Network access, C2 detection |\n| EDR\u002FAV | Endpoint alerts | Malware, process execution |\n| VPN\u002FRemote Access | Connection logs | Unauthorized access |\n| DNS Servers | Query logs | C2 beaconing, data exfiltration |\n| Email Gateway | Email security logs | Phishing, BEC |\n\n### Tier 2 - High Priority\n\n| Source | Log Type | Security Value |\n|---|---|---|\n| Web Proxy | HTTP\u002FHTTPS logs | Web-based attacks, data exfiltration |\n| Cloud platforms (AWS\u002FAzure\u002FGCP) | Audit logs | Cloud security posture |\n| Database servers | Audit\u002Fquery logs | Data access, SQL injection |\n| DHCP\u002FIPAM | Address allocation | Asset tracking |\n| File servers | Access logs | Data access monitoring |\n\n### Tier 3 - Standard\n\n| Source | Log Type | Security Value |\n|---|---|---|\n| Application servers | App logs | Application-level attacks |\n| Print servers | Print logs | Data loss prevention |\n| Badge\u002Fphysical access | Access logs | Physical security correlation |\n| Network devices (switches\u002Frouters) | Syslog | Network anomalies |\n\n## Onboarding Process\n\n### Step 1: Discovery and Assessment\n\n```\n1. Identify the log source:\n   - System type and version\n   - Log format (syslog, CEF, JSON, Windows Events, etc.)\n   - Log volume estimate (EPS - events per second)\n   - Network location and firewall requirements\n\n2. Assess security value:\n   - What threats can this source help detect?\n   - Which MITRE ATT&CK techniques does it cover?\n   - Is there an existing SIEM parser?\n\n3. Estimate ingestion cost:\n   - Daily volume in GB\n   - License impact (per-GB or per-EPS pricing)\n   - Storage retention requirements\n```\n\n### Step 2: Configure Log Collection\n\n#### Syslog-Based Collection (Firewalls, Network Devices)\n\n```conf\n# rsyslog configuration for receiving syslog\n# \u002Fetc\u002Frsyslog.d\u002F10-siem-collection.conf\n\n# UDP reception\nmodule(load=\"imudp\")\ninput(type=\"imudp\" port=\"514\" ruleset=\"siem_forwarding\")\n\n# TCP reception\nmodule(load=\"imtcp\")\ninput(type=\"imtcp\" port=\"514\" ruleset=\"siem_forwarding\")\n\n# TLS reception\nmodule(load=\"imtcp\" StreamDriver.AuthMode=\"x509\u002Fname\"\n       StreamDriver.Mode=\"1\" StreamDriver.Name=\"gtls\")\ninput(type=\"imtcp\" port=\"6514\" ruleset=\"siem_forwarding\")\n\nruleset(name=\"siem_forwarding\") {\n    # Forward to SIEM\n    action(type=\"omfwd\" target=\"siem.company.com\" port=\"9514\"\n           protocol=\"tcp\" queue.type=\"LinkedList\"\n           queue.filename=\"siem_fwd\" queue.maxdiskspace=\"1g\"\n           queue.saveonshutdown=\"on\" action.resumeRetryCount=\"-1\")\n}\n```\n\n#### Windows Event Log Collection (Splunk Universal Forwarder)\n\n```conf\n# inputs.conf on Splunk Universal Forwarder\n[WinEventLog:\u002F\u002FSecurity]\ndisabled = 0\nindex = wineventlog\nsourcetype = WinEventLog:Security\nevt_resolve_ad_obj = 1\ncheckpointInterval = 5\n\n[WinEventLog:\u002F\u002FSystem]\ndisabled = 0\nindex = wineventlog\nsourcetype = WinEventLog:System\n\n[WinEventLog:\u002F\u002FMicrosoft-Windows-Sysmon\u002FOperational]\ndisabled = 0\nindex = wineventlog\nsourcetype = XmlWinEventLog:Microsoft-Windows-Sysmon\u002FOperational\nrenderXml = true\n\n[WinEventLog:\u002F\u002FMicrosoft-Windows-PowerShell\u002FOperational]\ndisabled = 0\nindex = wineventlog\nsourcetype = XmlWinEventLog:Microsoft-Windows-PowerShell\u002FOperational\n```\n\n#### Cloud Log Collection (AWS CloudTrail)\n\n```json\n{\n  \"AWSTemplateFormatVersion\": \"2010-09-09\",\n  \"Resources\": {\n    \"CloudTrailToSIEM\": {\n      \"Type\": \"AWS::CloudTrail::Trail\",\n      \"Properties\": {\n        \"TrailName\": \"siem-cloudtrail\",\n        \"S3BucketName\": \"company-cloudtrail-logs\",\n        \"IsLogging\": true,\n        \"IsMultiRegionTrail\": true,\n        \"IncludeGlobalServiceEvents\": true,\n        \"EnableLogFileValidation\": true,\n        \"EventSelectors\": [\n          {\n            \"ReadWriteType\": \"All\",\n            \"IncludeManagementEvents\": true,\n            \"DataResources\": [\n              {\n                \"Type\": \"AWS::S3::Object\",\n                \"Values\": [\"arn:aws:s3\"]\n              }\n            ]\n          }\n        ]\n      }\n    }\n  }\n}\n```\n\n### Step 3: Parse and Normalize\n\n#### Custom Parser Example (Splunk props.conf\u002Ftransforms.conf)\n\n```conf\n# props.conf\n[custom:firewall:logs]\nSHOULD_LINEMERGE = false\nLINE_BREAKER = ([\\r\\n]+)\nTIME_PREFIX = ^\nTIME_FORMAT = %Y-%m-%dT%H:%M:%S%z\nMAX_TIMESTAMP_LOOKAHEAD = 30\nTRANSFORMS-firewall = firewall_extract_fields\nFIELDALIAS-src = src_addr AS src_ip\nFIELDALIAS-dst = dst_addr AS dest_ip\nEVAL-action = case(fw_action==\"allow\", \"allowed\", fw_action==\"deny\", \"blocked\", true(), \"unknown\")\nEVAL-vendor_product = \"Custom Firewall\"\nLOOKUP-geo = geo_ip_lookup ip AS dest_ip OUTPUT country, city, latitude, longitude\n\n# transforms.conf\n[firewall_extract_fields]\nREGEX = ^(\\S+)\\s+(\\S+)\\s+action=(\\w+)\\s+src=(\\S+):(\\d+)\\s+dst=(\\S+):(\\d+)\\s+proto=(\\w+)\\s+bytes=(\\d+)\nFORMAT = timestamp::$1 hostname::$2 fw_action::$3 src_addr::$4 src_port::$5 dst_addr::$6 dst_port::$7 protocol::$8 bytes::$9\n```\n\n#### CIM Field Mapping\n\n| Raw Field | CIM Field | Data Model |\n|---|---|---|\n| src_addr | src_ip | Network_Traffic |\n| dst_addr | dest_ip | Network_Traffic |\n| dst_port | dest_port | Network_Traffic |\n| fw_action | action | Network_Traffic |\n| bytes_sent + bytes_recv | bytes | Network_Traffic |\n| user_name | user | Authentication |\n| login_result | action | Authentication |\n| process_path | process | Endpoint |\n\n### Step 4: Validate Data Quality\n\n```spl\n# Verify events are arriving\nindex=new_source earliest=-1h\n| stats count by sourcetype, host, source\n\n# Check field extraction quality\nindex=new_source earliest=-1h\n| stats count(src_ip) as has_src count(dest_ip) as has_dest count(action) as has_action count by sourcetype\n| eval src_coverage=round(has_src\u002Fcount*100,1)\n| eval dest_coverage=round(has_dest\u002Fcount*100,1)\n| eval action_coverage=round(has_action\u002Fcount*100,1)\n\n# Verify CIM compliance\n| datamodel Network_Traffic search\n| search sourcetype=new_sourcetype\n| stats count by source, sourcetype\n\n# Check for timestamp parsing issues\nindex=new_source earliest=-1h\n| eval time_diff=abs(_time - _indextime)\n| stats avg(time_diff) as avg_lag max(time_diff) as max_lag by host\n| where avg_lag > 300\n```\n\n### Step 5: Enable Detection Coverage\n\n```spl\n# Verify existing correlation searches work with new source\nindex=new_source sourcetype=new_sourcetype\n| tstats count from datamodel=Authentication by _time span=1h\n| timechart span=1h count\n\n# Create source-specific detection rule\n[New Source - Authentication Anomaly]\nsearch = index=new_source sourcetype=new_sourcetype action=failure \\\n| stats count by src_ip, user \\\n| where count > 10\n```\n\n## Onboarding Checklist\n\n- [ ] Log source assessed and approved\n- [ ] Network connectivity verified\n- [ ] Collection agent\u002Fmethod configured\n- [ ] Log forwarding confirmed\n- [ ] Parser\u002Ffield extraction configured\n- [ ] CIM compliance validated\n- [ ] Data model acceleration enabled\n- [ ] Volume within license budget\n- [ ] Retention policy configured\n- [ ] Detection rules enabled\u002Fcreated\n- [ ] Dashboard updated\n- [ ] Documentation completed\n- [ ] SOC team notified\n\n## References\n\n- [UK NCSC - Onboarding Systems and Log Sources](https:\u002F\u002Fwww.ncsc.gov.uk\u002Fcollection\u002Fbuilding-a-security-operations-centre\u002Fonboarding-systems-and-log-sources)\n- [Sumo Logic - Cloud SIEM Onboarding Checklist](https:\u002F\u002Fhelp.sumologic.com\u002Fdocs\u002Fcse\u002Fget-started-with-cloud-siem\u002Fonboarding-checklist-cse\u002F)\n- [SIEM Logging Best Practices - Coralogix](https:\u002F\u002Fcoralogix.com\u002Fguides\u002Fsiem\u002Fsiem-logging\u002F)\n- [Huntress - SIEM Implementation Guide](https:\u002F\u002Fwww.huntress.com\u002Fsiem-guide\u002Fsiem-implementation-guide)\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42},[26,27,28,29,30,31,32],"siem","log-onboarding","log-management","data-ingestion","parsing","normalization","soc","mahipal","cybersecurity","1.0",[37,38,39,40],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations",[43,44,45,46],"T1078","T1685.002","T1685.005","T1566","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add NeelakshSaxena\u002FVayu --skill performing-log-source-onboarding-in-siem",{"tool":60,"command":61},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill performing-log-source-onboarding-in-siem",{"tool":63,"command":64},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill performing-log-source-onboarding-in-siem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002FSKILL.md",true,[68,74,78,84,88,92,98],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Ftemplate.md","ASSET","资产文件",1120,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fassets\u002Ftemplate.md",{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-reference.md","REFERENCE","参考文档",1593,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fapi-reference.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fstandards.md",1253,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fstandards.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fworkflows.md",1366,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fworkflows.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fagent.py","SCRIPT","脚本",7811,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fscripts\u002Fagent.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fprocess.py",8104,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fscripts\u002Fprocess.py",[103,110,117,124,131,138],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]