[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DCKZPQS4BP1D7XVSFXQBX9":3,"skill-same:01M7DCKZPQS4BP1D7XVSFXQBX9":104},{"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":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M7DCKZPQS4BP1D7XVSFXQBX9","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.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\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","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill performing-log-source-onboarding-in-siem",{"tool":62,"command":63},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill performing-log-source-onboarding-in-siem",{"tool":65,"command":66},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill performing-log-source-onboarding-in-siem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002FSKILL.md",true,[70,76,80,86,90,94,100],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002Ftemplate.md","ASSET","资产文件",1120,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fassets\u002Ftemplate.md",{"path":77,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi-reference.md","REFERENCE","参考文档",1593,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fapi-reference.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fstandards.md",1253,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fstandards.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fworkflows.md",1366,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Freferences\u002Fworkflows.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fagent.py","SCRIPT","脚本",7811,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fscripts\u002Fagent.py",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fprocess.py",8104,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-log-source-onboarding-in-siem\u002Fscripts\u002Fprocess.py",[105,113,121,130,137,144],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"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":125,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]