Perform structured log source onboarding into SIEM platforms by configuring collectors, parsers, normalization, and validation for complete security visibility.
Perform structured log source onboarding into SIEM platforms by configuring collectors, parsers, normalization, and validation for complete security visibility.
Log 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.
When to Use
When conducting security assessments that involve performing log source onboarding in siem
When following incident response procedures for related security events
When performing scheduled security testing or auditing activities
When validating security controls through hands-on testing
Common Misconfigurations & Verification
Events arrive but fields are unparsed: the source ingests into the index yet props.confTRANSFORMS/REGEX doesn't match the real log lines, so src_ip, dest_ip, user, action are empty and every correlation search and CIM data model silently misses this source. Verify field-extraction coverage (the count(src_ip)/count query) is near 100%, not just that count by sourcetype is non-zero.
Timestamp parsing wrong: missing/incorrect TIME_FORMAT, no timezone (%z), or MAX_TIMESTAMP_LOOKAHEAD too short makes Splunk use index time or shift events hours off — alerts fire late, dashboards show gaps, and _time vs _indextime lag balloons. Confirm avg(time_diff) < 300s and that a known event lands at its real wall-clock time.
CIM tags missing: fields extracted but the sourcetype isn't tagged into the data model (eventtype/tags.conf), so tstats/datamodel searches return nothing. Validate with | datamodel Network_Traffic search | search sourcetype=<new> returning rows.
Wrong sourcetype/index or duplicate ingest: a default sourcetype (e.g. generic syslog) bypasses your parser, and a forwarder + syslog both shipping the same source double-counts volume and license.
Verify end to end before closing the ticket: confirm events present, field coverage high, timestamps accurate (), CIM compliance via /, volume within license budget, and that at least one detection rule actually fires on a replayed/known event from the new source.
_time≈_indextime
datamodel
tstats
Prerequisites
SIEM platform deployed (Splunk, Elastic, Sentinel, QRadar, or similar)
Network access from source systems to SIEM collectors
Administrative access on source systems for agent installation
Common Information Model (CIM) or equivalent schema documentation
Change management approval for production system modifications
Log Source Priority Framework
Tier 1 - Critical (Onboard First)
Source
Log Type
Security Value
Active Directory
Security Event Logs
Authentication, privilege escalation
Firewalls
Traffic logs
Network access, C2 detection
EDR/AV
Endpoint alerts
Malware, process execution
VPN/Remote Access
Connection logs
Unauthorized access
DNS Servers
Query logs
C2 beaconing, data exfiltration
Email Gateway
Email security logs
Phishing, BEC
Tier 2 - High Priority
Source
Log Type
Security Value
Web Proxy
HTTP/HTTPS logs
Web-based attacks, data exfiltration
Cloud platforms (AWS/Azure/GCP)
Audit logs
Cloud security posture
Database servers
Audit/query logs
Data access, SQL injection
DHCP/IPAM
Address allocation
Asset tracking
File servers
Access logs
Data access monitoring
Tier 3 - Standard
Source
Log Type
Security Value
Application servers
App logs
Application-level attacks
Print servers
Print logs
Data loss prevention
Badge/physical access
Access logs
Physical security correlation
Network devices (switches/routers)
Syslog
Network anomalies
Onboarding Process
Step 1: Discovery and Assessment
1. Identify the log source:
- System type and version
- Log format (syslog, CEF, JSON, Windows Events, etc.)
- Log volume estimate (EPS - events per second)
- Network location and firewall requirements
2. Assess security value:
- What threats can this source help detect?
- Which MITRE ATT&CK techniques does it cover?
- Is there an existing SIEM parser?
3. Estimate ingestion cost:
- Daily volume in GB
- License impact (per-GB or per-EPS pricing)
- Storage retention requirements