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.