parsing
Breaking a raw log line into named fields, such as time, user and source address, that rules and searches can use.
In more detail
Parse each line once, at ingest, so rules never read raw text. Parsers break silently when a log format changes, so count unparsed lines and alert when that count rises. Always keep the raw event as well, so nothing is lost when a parser is wrong.
Related terms
- normalisation — Renaming fields from different log sources onto one agreed set of names, so one query works across all of them.
- raw event — The log line exactly as the source wrote it, before any parsing or renaming.
- regular expression — A pattern language for matching text, where characters such as ., *, ^ and $ have special meanings.
- ingestion pipeline — The chain of steps that takes a raw log line from its source to a searchable event: collect, buffer, parse, enrich, index and store.
Taught in
- SIEM Architecture: Ingestion Pipelines & Indexing — Security Operations & Threat Hunting (SOC)
- Event Correlation Rules, Thresholds & Anomaly Pipelines — Security Operations & Threat Hunting (SOC)
- Log Parsing, Schema Normalization (OCSF/ECS) & Extraction — Security Operations & Threat Hunting (SOC)
- Windows Event Logs, Sysmon & Linux Auditd Telemetry — Security Operations & Threat Hunting (SOC)
- Adversary Tactics, Techniques & Procedures (TTP) Mapping — Security Operations & Threat Hunting (SOC)
- Indicator of Compromise Extraction & Threat Hunting Feeds — Security Operations & Threat Hunting (SOC)
- Detecting Persistence: Tasks, Registry & Services — Security Operations & Threat Hunting (SOC)
- Disk Forensics: MFT, UsnJrnl & Prefetch — Security Operations & Threat Hunting (SOC)
- Malware Triage: Hashes, Strings & Sandboxing — Security Operations & Threat Hunting (SOC)