Skip to content
View log-parsing's full-sized avatar

Block or report log-parsing

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
log-parsing/README.md

LogParsing.com — SOC log parsing and alert correlation automation

LogParsing.com

Production engineering patterns for SOC log parsing, alert correlation, and response automation.

🌐 Visit the site → www.logparsing.com


What this is

LogParsing.com is a deep, code-backed knowledge base for the engineers who keep a Security Operations Center running: SOC analysts, security engineers, Python automation developers, and platform/DevOps teams. It treats ingestion, parsing, normalization, correlation, and response as a layered engineering discipline — not a set of vendor knobs — so detection coverage scales with telemetry volume instead of collapsing under it.

Every guide pairs architectural reasoning with runnable, fully-typed, async Python you can copy into a real pipeline. Diagrams are hand-authored, structured data is first-class, and each page maps its patterns to the compliance frameworks (NIST, ISO/IEC 27001, PCI-DSS) and MITRE ATT&CK techniques a production team is actually assessed against.

Why read it

  • Real implementations, not pseudocode. Bounded-queue ingestion, schema-validated normalization, stateful correlation windows, idempotent SOAR actions — each as a self-contained, production-grade Python module.
  • Failure-mode first. Every technique documents its error-code taxonomy, dead-letter routing, and back-pressure behavior, because the interesting part of a SOC pipeline is what happens when things break.
  • Grounded in standards. Elastic Common Schema (ECS) and OSSEM field mapping, RFC 5424 syslog, STIX 2.1, MITRE ATT&CK, and the NIST/ISO/PCI controls that govern log management and incident response.
  • Built for depth. 50+ interlinked guides organized so you can start at an overview and drill straight into the exact edge case you're fighting.

The four areas

Area What it covers
Log Ingestion & Parsing Workflows Stage-gate pipelines for Syslog/JSON/CSV, schema validation, async batching, rate limiting, and error categorization.
SOC Log Architecture & Taxonomy Deterministic taxonomies, syslog RFC discipline, JSON normalization, ECS/OSSEM mapping, and threat-intel feed mapping.
Alert Correlation & Rule Engines Cross-source event linking, temporal correlation windows, MITRE ATT&CK integration, dynamic severity scoring, and false-positive reduction.
SOAR Playbook & Response Automation Durable playbook orchestration, severity-aware alert routing, idempotent automated ticketing, and fail-open case enrichment.

A few guides to start with

How the site is built

A static site generated with Eleventy, authored in Markdown with hand-written inline SVG diagrams and JSON-LD structured data, and deployed to Cloudflare Pages.

npm install       # install dependencies
npm run build     # build the static site into _site/
npm run serve     # local dev server with live reload
npm run deploy    # build and deploy to Cloudflare Pages

Contributing & feedback

Spotted an error, an outdated technique, or a gap in coverage? Open an issue on GitHub. Suggestions for new guides and edge cases are welcome.


Explore the full library at www.logparsing.com →
Maintained by Log Parsing

Popular repositories Loading

  1. log-parsing log-parsing Public

    Production engineering patterns for SOC log parsing, alert correlation, and SOAR response automation — the guides behind logparsing.com.

    CSS