performing-log-source-onboarding-in-siem

Configure collectors, parsers, and CIM normalization to onboard log sources into SIEM platforms.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill performing-log-source-onboarding-in-siem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-log-source-onboarding-in-siem
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/soc-operations/performing-log-source-onboarding-in-siem
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-log-source-onboarding-in-siem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New log sources often arrive in a SIEM with unparsed fields, broken timestamps, or missing data model tags, leaving detection rules blind. This Skill provides a structured onboarding workflow so sources are collected, parsed, normalized, and validated before they are trusted for security monitoring.

Core Features & Use Cases

  • Tiered Source Prioritization: Ranks log sources (Active Directory, firewalls, EDR, DNS, cloud audit logs) by security value versus ingestion cost.
  • Collection Configuration: Provides ready-to-adapt configurations for rsyslog, Splunk Universal Forwarder, and AWS CloudTrail ingestion.
  • Parsing and CIM Normalization: Includes props.conf/transforms.conf examples and raw-to-CIM field mapping tables for Network_Traffic, Authentication, and Endpoint data models.
  • Validation Queries: Supplies Splunk SPL checks for field coverage, timestamp lag, CIM compliance, and detection rule firing.
  • Use Case: A SOC engineer onboarding a new firewall into Splunk follows the five-step process to configure syslog forwarding, build field extractions, map fields to the Network_Traffic data model, and verify that a correlation search fires on a replayed event.

Quick Start

Ask the AI to walk you through onboarding a new firewall log source into Splunk, including parser configuration, CIM mapping, and validation queries.

Frequently Asked Questions about performing-log-source-onboarding-in-siem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard a new log source into Splunk?

Onboard a log source by assessing its security value and volume, configuring collection via syslog or a Universal Forwarder, building field extractions in props.conf and transforms.conf, mapping fields to CIM data models, and validating with SPL queries before enabling detections.

Which log sources should be onboarded into a SIEM first?

Prioritize Tier 1 sources with the highest security value: Active Directory security event logs, firewall traffic logs, EDR alerts, VPN connection logs, DNS query logs, and email gateway logs. These cover authentication, network access, and malware detection use cases.

Why are my SIEM events ingested but fields are empty?

Empty fields usually mean the parser regex or TRANSFORMS in props.conf does not match the actual log format, so src_ip, dest_ip, user, and action are never extracted. Verify field extraction coverage with a count(src_ip)/count query rather than just checking that events arrive.

How do I fix wrong timestamps in Splunk log ingestion?

Wrong timestamps come from missing or incorrect TIME_FORMAT, absent timezone (%z), or a MAX_TIMESTAMP_LOOKAHEAD that is too short. Confirm accuracy by comparing _time to _indextime and checking that average lag stays under 300 seconds.

Does this onboarding process work with Elastic or Sentinel?

The five-step process of discovery, collection, parsing, normalization, and validation applies to Splunk, Elastic, Sentinel, and QRadar. The concrete configuration examples use rsyslog, Splunk forwarders, and AWS CloudTrail, but the methodology is platform-agnostic.