[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78TSYG5GTPJ6DC38948Y5AD":3,"skill-same:01M78TSYG5GTPJ6DC38948Y5AD":94},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M78TSYG5GTPJ6DC38948Y5AD","performing-log-source-onboarding-in-siem",null,"Perform structured log source onboarding into SIEM platforms by configuring collectors, parsers, normalization, and validation for complete security visibility.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\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 by configuring collectors, parsers, normalization, and validation for complete security visibility.\ndomain: cybersecurity\nsubdomain: soc-operations\ntags: [siem, log-onboarding, log-management, data-ingestion, parsing, normalization, soc]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\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,"subdomain":36,"description":7},[26,27,28,29,30,31,32],"siem","log-onboarding","log-management","data-ingestion","parsing","normalization","soc","mahipal","cybersecurity","1.0","soc-operations","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fperforming-log-source-onboarding-in-siem",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill performing-log-source-onboarding-in-siem",{"tool":52,"command":53},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill performing-log-source-onboarding-in-siem",{"tool":55,"command":56},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill performing-log-source-onboarding-in-siem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002FSKILL.md",true,[60,66,70,76,80,84,90],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Ftemplate.md","ASSET","资产文件",1120,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fassets\u002Ftemplate.md",{"path":67,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fapi-reference.md","REFERENCE","参考文档",1593,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fapi-reference.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fstandards.md",1253,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fstandards.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fworkflows.md",1366,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fworkflows.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fagent.py","SCRIPT","脚本",7811,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fscripts\u002Fagent.py",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fprocess.py",8104,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fscripts\u002Fprocess.py",[95,103,110,117,124,132],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"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":99,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\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":99,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\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":99,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\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":99,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]