SOC ARCHITECTURE & SIEM PLATFORMS: TELEMETRY INGESTION, CORRELATION & DETECTION

Architect enterprise Security Operations Center (SOC) defense pipelines for B.Tech Computer Science & IT: Multi-tier SOC organizational staffing models (Tier 1 Triage to Tier 3 Threat Hunting); Security Information and Event Management (SIEM) data ingestion pipelines; telemetry normalization schemas (Elastic Common Schema vs. Open Cybersecurity Schema Framework); multi-event correlation rule engineering; detection-as-code using Sigma; log parsing with Logstash and Fluentbit; and Security Orchestration, Automation, and Response (SOAR) playbook integration.

πŸ›‘οΈ Centralized Security Monitoring, Real-Time Correlation & Telemetry Analytics

In modern enterprise environments, security events are generated at immense scale across thousands of distributed endpoints, network switches, identity providers, cloud services, and application microservices. A single organization can produce tens of billions of discrete audit logs daily. Without centralized operational visibility, security incidents remain hidden within isolated log silos until severe data compromise occurs. A Security Operations Center (SOC) is the centralized organizational command unit that continuously monitors, detects, analyzes, and responds to cybersecurity events using people, processes, and technology. The operational backbone of the modern SOC is the Security Information and Event Management (SIEM) platform. SIEM solutions ingest heterogeneous event streams, parse and normalize disparate data formats into unified data schemas (such as ECS or OCSF), apply multi-event Correlation Engines to isolate high-fidelity indicators of compromise, and trigger automated mitigation actions via Security Orchestration, Automation, and Response (SOAR) pipelines.

1. SOC Operational Tiers & Event Ingestion Pipeline Topography
Architectural schematic of enterprise SOC operations, detailing the end-to-end data pipeline from raw endpoint generation to multi-tier analyst triage and automated SOAR orchestration.
Enterprise SOC Hierarchy & SIEM Data Stream Topography
ENTERPRISE SOC ARCHITECTURE & TELEMETRY INGESTION PIPELINE:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ TELEMETRY GENERATION SOURCES:                                                                 β”‚
β”‚ β€’ Endpoints (Windows Sysmon / EDR)  β€’ Cloud Providers (AWS CloudTrail / Azure Activity)       β”‚
β”‚ β€’ Identity (Active Directory / Okta) β€’ Network (Palo Alto Firewalls, Zeek, Suricata, DNS)     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                                β”‚
                                                β–Ό (Syslog-ng / Beats / OpenTelemetry Agents)
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ INGESTION & MESSAGE QUEUE BUFFERING TIER:                                                     β”‚
β”‚ β€’ Apache Kafka / RabbitMQ: Distributed high-throughput message streaming buffer.              β”‚
β”‚ β€’ Protects downstream SIEM parsing engines from dropped events during volumetric spikes.      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                                β”‚
                                                β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ NORMALIZATION & ENRICHMENT ENGINE (Logstash / Vector / Fluentbit):                            β”‚
β”‚ β€’ Parsing (Grok / Regex): Dissects raw strings into structured JSON key-value pairs.          β”‚
β”‚ β€’ Schema Mapping: Aligns fields to Elastic Common Schema (ECS) or OCSF standards.             β”‚
β”‚ β€’ Enrichment: Appends GeoIP coordinates, ASN ownership, and Threat Intel reputation tags.     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                                β”‚
                                                β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SIEM CORRELATION & STORAGE CLUSTER (Splunk / Elastic SIEM / Microsoft Sentinel / QRadar):     β”‚
β”‚ β€’ Hot/Warm/Cold Tier Storage: Fast NVMe search indices transitioning to object storage (S3).  β”‚
β”‚ β€’ Real-Time Rule Engine: Evaluates stateful correlations, threshold gates, and Sigma rules.   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                                β”‚
                                                β–Ό (Alert Generation Trigger)
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SOC ANALYST TRIAGE HIERARCHY & AUTOMATION:                                                    β”‚
β”‚                                                                                               β”‚
β”‚ β”œβ”€β”€ TIER 1 (TRIAGE ANALYST)      : Validates alerts, filters false positives, escalates true  β”‚
β”‚ β”‚                                  positives within strict SLA (e.g., < 15 minutes).          β”‚
β”‚ β”œβ”€β”€ TIER 2 (INCIDENT RESPONDER)  : Deep-dive host/network investigation, containment dispatch.β”‚
β”‚ β”œβ”€β”€ TIER 3 (THREAT HUNTER / SME) : Proactive hypothesis hunting, rootkit & malware reverse engβ”‚
β”‚ └── SOAR AUTOMATION ENGINE       : Executes automated playbooks: host isolation, token revoke.β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Architectural Standard: Modern SOCs deploy message queuing tiers (such as Apache Kafka) upstream of SIEM parsers. This decouples event collection from indexing, guaranteeing zero packet or log loss during network-wide incidents when hosts simultaneously generate flood volumes of security telemetry.
Real-Time Example 1: Telemetry Normalization: Elastic Common Schema (ECS) & OCSF
Analysis of log schema normalization. Contrasts unstructured vendor log formats with standardized models: Elastic Common Schema (ECS) and the Open Cybersecurity Schema Framework (OCSF), demonstrating field normalization across heterogeneous sources.
Raw Syslog vs. Normalized Elastic Common Schema (ECS) Mapping
THE SCHEMA NORMALIZATION DILEMMA:

Unnormalized Reality: Three distinct vendors log a source IP address using different keys:
  β€’ Palo Alto Firewall  : src=198.51.100.25
  β€’ Windows Security Log: SourceNetworkAddress = 198.51.100.25
  β€’ Apache Web Server   : ClientIP: 198.51.100.25
Result: Analysts would have to write 3 distinct queries to hunt for a single malicious IP address!

THE SOLUTION: ELASTIC COMMON SCHEMA (ECS) / OCSF NORMALIZATION:

1. RAW UNSTRUCTURED SYSLOG EVENT (Palo Alto Traffic Log):
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Nov 04 16:20:10 pa-fw01 1,2026/11/04 16:20:10,0018C103334,TRAFFIC,drop,1,2026/11/04 16:20:10, β”‚
β”‚ 198.51.100.25,10.0.0.5,0.0.0.0,0.0.0.0,Rule-Block-SSH,,,ssh,vsys1,untrust,trust,ethernet1/1,  β”‚
β”‚ ethernet1/2,Log-Forward,2026/11/04 16:20:10,0,1,54122,22,0,0,0x0,tcp,deny,64,64,0,1           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                                β”‚
                                                β–Ό (Logstash Grok Parsing & ECS Mapping)
2. NORMALIZED JSON DOCUMENT (Adheres to ECS Specification):
{
  "@timestamp": "2026-11-04T16:20:10.000Z",
  "ecs": { "version": "8.11.0" },
  "event": {
    "action": "network_traffic_denied",
    "category": "network",
    "type": ["connection", "denied"],
    "outcome": "failure",
    "dataset": "paloalto.firewall"
  },
  "source": {
    "ip": "198.51.100.25",
    "port": 54122,
    "geo": { "country_iso_code": "US" }
  },
  "destination": {
    "ip": "10.0.0.5",
    "port": 22
  },
  "network": {
    "transport": "tcp",
    "protocol": "ssh",
    "direction": "inbound"
  },
  "rule": {
    "name": "Rule-Block-SSH"
  },
  "observer": {
    "hostname": "pa-fw01",
    "type": "firewall",
    "vendor": "Palo Alto Networks"
  }
}
Operational Impact: Once logs are mapped to a standardized schema, a single hunting queryβ€”such as 'source.ip: 198.51.100.25'β€”simultaneously searches firewall drops, VPN authentications, web proxy connections, and endpoint process interactions without requiring vendor-specific syntax adjustments.
Real-Time Example 2: Parsing & Extraction: Logstash Grok Pipelines for Security Logs
Building data processing and transformation pipelines in Logstash. Demonstrates constructing regular-expression Grok patterns to parse custom authentication logs, extract IP addresses and usernames, and apply conditional drop filters.
Logstash Configuration Pipeline (/etc/logstash/conf.d/auth_pipeline.conf)
# ==============================================================================
# LOGSTASH PARSING & NORMALIZATION PIPELINE FOR SSH AUTHENTICATION LOGS
# Input: Reads raw Syslog stream from Linux bastion hosts on TCP 5044
# ==============================================================================

input {
  beats {
    port => 5044
  }
}

filter {
  # Match SSH failed authentication lines
  # Sample: "Failed password for invalid user sdet from 198.51.100.25 port 49152 ssh2"
  if [message] =~ "Failed password" {
    grok {
      match => {
        "message" => "Failed password for %{DATA:auth_user_status} %{USER:user.name} from %{IP:source.ip} port %{POSINT:source.port:int} ssh2"
      }
      add_tag => [ "ssh_failed_login", "security_alert" ]
    }

    # Normalize event metadata into Elastic Common Schema
    mutate {
      add_field => {
        "[event][kind]" => "event"
        "[event][category]" => "authentication"
        "[event][type]" => "start"
        "[event][outcome]" => "failure"
        "[network][protocol]" => "ssh"
        "[destination][port]" => 22
      }
    }

    # Geolocation Enrichment: Map IP to physical coordinates and country
    geoip {
      source => "[source][ip]"
      target => "[source][geo]"
    }
  }

  # Drop informational non-security debug noise to conserve SIEM storage
  if [message] =~ "session closed for user" {
    drop { }
  }
}

output {
  elasticsearch {
    hosts => [ "https://siem-cluster.internal:9200" ]
    index => "soc-auth-events-%{+YYYY.MM.dd}"
    ssl_certificate_verification => true
    user => "logstash_internal"
    password => "SecretVaultPass123"
  }
}
Pipeline Processing Telemetry: Input Raw Message: "Failed password for invalid user sdet from 198.51.100.25 port 49152 ssh2" Extracted Fields: β”œβ”€β”€ [user][name] : "sdet" β”œβ”€β”€ [source][ip] : "198.51.100.25" β”œβ”€β”€ [event][outcome] : "failure" β”œβ”€β”€ [source][geo][city] : "Ashburn" └── Tags : ["ssh_failed_login", "security_alert"] Filtered Noise: 42,000 informational "session closed" logs dropped per hour, reducing Elasticsearch ingest indexing overhead by 34%.
Real-Time Example 3: Detection Engineering: Multi-Event Correlation Rules in SIEM
Analysis of stateful SIEM correlation rules. Explains temporal event grouping, sliding-window thresholds, and illustrates detecting a Brute-Force Authentication attack followed by a Successful Login within a 5-minute window.
Splunk SPL & Elastic EQL (Brute-Force Followed by Successful Login)
MULTI-EVENT CORRELATION LOGIC & QUERY IMPLEMENTATION:

THREAT SCENARIO:
Adversary runs automated hydra password spray against public portal.
Event Phase 1: Generates > 5 Failed Login attempts within 5 minutes.
Event Phase 2: Generates 1 Successful Login from the SAME source IP within 1 minute of failures!

1. SPLUNK SEARCH PROCESSING LANGUAGE (SPL) CORRELATION RULE:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ index=authentication sourcetype=auth_logs (event.outcome=failure OR event.outcome=success)    β”‚
β”‚ | bin _time span=5m                                                                           β”‚
β”‚ | stats                                                                                       β”‚
β”‚     count(eval(event.outcome="failure")) as failure_count,                                    β”‚
β”‚     count(eval(event.outcome="success")) as success_count,                                    β”‚
β”‚     values(user.name) as attempted_users,                                                     β”‚
β”‚     latest(_time) as last_seen                                                                β”‚
β”‚   by source.ip, destination.ip                                                                β”‚
β”‚ | where failure_count >= 5 AND success_count >= 1                                             β”‚
β”‚ | eval alert_description = "CRITICAL: Multiple login failures followed by immediate successfulβ”‚
β”‚   authentication from single source IP!"                                                      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

2. ELASTIC EVENT QUERY LANGUAGE (EQL) SEQUENCE CORRELATION RULE:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ sequence by source.ip with maxspan = 5m                                                       β”‚
β”‚   /* Step 1: Minimum 5 failed authentication attempts from same IP */                         β”‚
β”‚   [authentication where event.outcome == "failure"] with runs = 5                             β”‚
β”‚   /* Step 2: Followed immediately by successful authentication from that exact IP */          β”‚
β”‚   [authentication where event.outcome == "success"]                                           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Correlation Rule Analytics: Why not alert on failed logins alone? Alerting on a single failed login generates thousands of daily false positives from legitimate users forgetting passwords. Correlating high-frequency failures (>=5) followed by an immediate success from the identical source IP specifically isolates compromised accounts resulting from brute-force attempts.
Real-Time Example 4: Detection-as-Code: Universal Rule Engineering with Sigma
Authoring standardized Detection-as-Code signatures using Sigma. Demonstrates writing a vendor-agnostic YAML detection rule to detect suspicious Windows Process Hollowing and dumping via PowerShell, compiling rules to Splunk, Sentinel, and Elasticsearch.
Sigma Detection Rule Specification (/rules/proc_creation_win_lsass_dump.yml)
title: LSASS Memory Dump via Native Windows Utilities
id: a234b678-c112-4e90-89bc-991284759283
status: production
description: Detects command-line invocation of native utilities (comsvcs.dll, procdump) used to dump LSASS process memory.
references:
    - https://attack.mitre.org/techniques/T1003/001/
author: Nikita Infotech Detection Engineering
date: 2026-11-04
tags:
    - attack.credential_access
    - attack.t1003.001
logsource:
    category: process_creation
    product: windows
detection:
    selection_rundll:
        Image|endswith: '\rundll32.exe'
        CommandLine|contains|all:
            - 'comsvcs.dll'
            - 'MiniDump'
    selection_procdump:
        Image|endswith:
            - '\procdump.exe'
            - '\procdump64.exe'
        CommandLine|contains: 'lsass'
    condition: selection_rundll or selection_procdump
falsepositives:
    - Rare administrative memory diagnostics authorized by IT Operations.
level: high

# ==============================================================================
# COMPILING SIGMA RULES TO TARGET SIEM ENGINES VIA SIGMAC / PYCYBOXL:
# ==============================================================================
# 1. Compile to Splunk SPL:
# $ sigma convert -t splunk -p sysmon proc_creation_win_lsass_dump.yml
# Output:
# (Image="*\\rundll32.exe" CommandLine="*comsvcs.dll*" CommandLine="*MiniDump*") OR
# (Image IN ("*\\procdump.exe", "*\\procdump64.exe") CommandLine="*lsass*")

# 2. Compile to Microsoft Sentinel KQL (Kusto Query Language):
# $ sigma convert -t kql -p sysmon proc_creation_win_lsass_dump.yml
# Output:
# SecurityEvent | where (EventID == 4688 and (CommandLine has "comsvcs.dll" and ...))
Detection-as-Code Principle: Sigma abstracts detection logic away from vendor lock-in. Security teams store detection rules in centralized Git repositories (GitLab/GitHub) as YAML files, test them through CI/CD pipelines, and compile them automatically to whatever SIEM backend is deployed across cloud or on-prem environments.
Real-Time Example 5: Endpoint Telemetry: Windows Sysmon Logging Architecture
Analysis of Microsoft System Monitor (Sysmon). Examines the Windows event stream, key event IDs for threat detection (Process Create, Network Connect, Driver Load, Image Load), and authoring hardened XML configuration filters.
XML (Hardened Sysmon Event Filtering Configuration: sysmonconfig.xml)
<Sysmon schemaversion="4.90">
  <!-- Hash algorithms to calculate on all loaded binaries -->
  <HashAlgorithms>SHA256,MD5</HashAlgorithms>
  <EventFiltering>

    <!-- EVENT ID 1: PROCESS CREATION (CRITICAL HUNTING ARTIFACT) -->
    <RuleGroup name="Process_Creation" groupRelation="or">
      <ProcessCreate onmatch="include">
        <!-- Catch Lolbins and scripting engines -->
        <Image condition="image">powershell.exe</Image>
        <Image condition="image">cmd.exe</Image>
        <Image condition="image">wmic.exe</Image>
        <Image condition="image">certutil.exe</Image>
        <Image condition="image">mshta.exe</Image>
      </ProcessCreate>
    </RuleGroup>

    <!-- EVENT ID 3: NETWORK CONNECTIONS (CORRELATING C2) -->
    <RuleGroup name="Network_Connect" groupRelation="or">
      <NetworkConnect onmatch="include">
        <!-- Log all outbound network connections made by scripting binaries -->
        <Image condition="image">powershell.exe</Image>
        <Image condition="image">certutil.exe</Image>
        <DestinationPort condition="is">4444</DestinationPort>
        <DestinationPort condition="is">1337</DestinationPort>
      </NetworkConnect>
      <NetworkConnect onmatch="exclude">
        <!-- Drop noisy browser traffic to trusted domains -->
        <DestinationHostname condition="endswith">.microsoft.com</DestinationHostname>
      </NetworkConnect>
    </RuleGroup>

    <!-- EVENT ID 8: CREATEREMOTETHREAD (INJECTION / PROCESS HOLLOWING) -->
    <RuleGroup name="Thread_Injection" groupRelation="or">
      <CreateRemoteThread onmatch="include">
        <!-- Target process being injected into -->
        <TargetImage condition="image">lsass.exe</TargetImage>
        <TargetImage condition="image">explorer.exe</TargetImage>
        <TargetImage condition="image">svchost.exe</TargetImage>
      </CreateRemoteThread>
    </RuleGroup>

  </EventFiltering>
</Sysmon>
High-Value Sysmon Event IDs: β€’ Event ID 1: Process Creation (CommandLine, ParentImage, ParentCommandLine, Hashes). β€’ Event ID 3: Network Connection (Source/Dest IP, Port, Initiating Process Image). β€’ Event ID 7: Image Loaded (DLLs loaded into running processes; catches DLL Side-Loading). β€’ Event ID 8: CreateRemoteThread (Detects cross-process injection and process hollowing). β€’ Event ID 11: FileCreate (Captures dropper writes and ransom note generation).
Real-Time Example 6: Alert Fatigue Reduction: Deduplication & Risk-Based Alerting (RBA)
Engineering strategies to combat SOC alert fatigue. Compares traditional brittle point-in-time threshold alerts against Risk-Based Alerting (RBA) frameworks that aggregate risk scores across entities (User, System) over 24-hour windows.
Traditional Alerting vs. Risk-Based Alerting (RBA) Entity Scoring
THE SOC ALERT FATIGUE CHALLENGE:
A Tier-1 analyst receives 1,200 alerts daily. 98% are benign noise:
  β€’ Alert 1: "User downloaded file with rare extension" (Risk score: 10)
  β€’ Alert 2: "User logged in after business hours"     (Risk score: 15)
  β€’ Alert 3: "PowerShell executed with Base64 param"   (Risk score: 25)
  β€’ Alert 4: "Outbound connection to non-standard port"(Risk score: 30)

Traditional Point-in-Time Approach:
Triggers 4 separate tickets! Analyst spends hours triaging each individually, suffers fatigue,
and marks all as false positives.

THE RISK-BASED ALERTING (RBA) FRAMEWORK (Splunk RBA / Elastic Risk Engine):
Instead of generating tickets on low-fidelity events, the SIEM writes to a Risk Index:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ ENTITY TRACKER: HOST = WIN-PROD-44 | USER = sdet_aarav                                        β”‚
β”‚                                                                                               β”‚
β”‚ 14:02 IST : Alert 1 fires ──► Appends +10 Risk Points to Entity (Total: 10 - NO TICKET)       β”‚
β”‚ 18:30 IST : Alert 2 fires ──► Appends +15 Risk Points to Entity (Total: 25 - NO TICKET)       β”‚
β”‚ 18:35 IST : Alert 3 fires ──► Appends +25 Risk Points to Entity (Total: 50 - NO TICKET)       β”‚
β”‚ 18:36 IST : Alert 4 fires ──► Appends +30 Risk Points to Entity (Total: 80 βž” EXCEEDS 75!)    β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                                β”‚
                                                β–Ό (Aggregated Incident Creation)
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ SINGLE HIGH-FIDELITY COMPOSITE INCIDENT CREATED (RISK SCORE: 80 / 100):                       β”‚
β”‚ Title: Composite Entity Risk Threshold Exceeded for User: sdet_aarav                          β”‚
β”‚ Context: 4 discrete low-severity events occurred on the same entity within a 5-hour window!   β”‚
β”‚ Tier-1 Analyst receives ONE correlated, actionable, high-probability intrusion package!       β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
SOC Metrics Impact: Deploying Risk-Based Alerting (RBA) routinely reduces raw alert ticket volume by 70% to 80% while increasing true positive detection rates, directly lowering Mean Time to Acknowledge (MTTA) and preventing critical intrusions from being lost in alert queues.
Real-Time Example 7: Python SIEM Alert Ingestion & Triage Engine
Building an automated alert ingestion and enrichment processor in Python. Ingests normalized event logs, correlates failed-to-successful authentication sequences, extracts threat scores, and generates formatted alert packages.
Python (Automated SIEM Alert Correlation Engine: siem_correlator.py)
import json
import time
from collections import defaultdict
from typing import List, Dict

class SiemCorrelationEngine:
    """
    Simulates an in-memory SIEM correlation stream processor:
      1. Ingests normalized JSON security events.
      2. Tracks sliding temporal windows per source IP.
      3. Correlates authentication failures followed by successes.
      4. Dispatches actionable alerts when correlation criteria match.
    """
    def __init__(self, failure_threshold: int = 3, time_window_seconds: int = 300):
        self.threshold = failure_threshold
        self.window = time_window_seconds
        # Structure: source_ip -> list of failure timestamps
        self.failure_tracker = defaultdict(list)

    def process_event(self, event: dict) -> dict:
        now = event.get("timestamp_epoch", time.time())
        src_ip = event.get("source", {}).get("ip")
        outcome = event.get("event", {}).get("outcome")
        username = event.get("user", {}).get("name", "unknown")

        if not src_ip:
            return {"alert": False}

        # Clean failure timestamps older than sliding window
        self.failure_tracker[src_ip] = [t for t in self.failure_tracker[src_ip] if now - t <= self.window]

        if outcome == "failure":
            self.failure_tracker[src_ip].append(now)
            return {"alert": False, "status": f"Recorded failure #{len(self.failure_tracker[src_ip])} for {src_ip}"}

        elif outcome == "success":
            prior_failures = len(self.failure_tracker[src_ip])
            if prior_failures >= self.threshold:
                # CORRELATION MATCH: Threshold failures followed by success!
                alert = {
                    "alert": True,
                    "rule_name": "CORR_BRUTEFORCE_SUCCESS",
                    "severity": "CRITICAL",
                    "source_ip": src_ip,
                    "target_user": username,
                    "prior_failures_detected": prior_failures,
                    "window_seconds": self.window,
                    "description": f"Potential Brute-Force Success: {prior_failures} failures followed by valid login!"
                }
                # Reset tracking for this IP post alert
                self.failure_tracker[src_ip] = []
                return alert

        return {"alert": False}

if __name__ == "__main__":
    correlator = SiemCorrelationEngine(failure_threshold=3, time_window_seconds=60)

    print("==========================================================================")
    print("      SIEM STREAMING CORRELATION & ALERT ENGINE")
    print("==========================================================================")

    # Simulated incoming event stream from single attacker IP: 198.51.100.25
    test_stream = [
        {"timestamp_epoch": 1000, "source": {"ip": "198.51.100.25"}, "user": {"name": "admin"}, "event": {"outcome": "failure"}},
        {"timestamp_epoch": 1010, "source": {"ip": "198.51.100.25"}, "user": {"name": "root"}, "event": {"outcome": "failure"}},
        {"timestamp_epoch": 1020, "source": {"ip": "198.51.100.25"}, "user": {"name": "sdet"}, "event": {"outcome": "failure"}},
        {"timestamp_epoch": 1030, "source": {"ip": "198.51.100.25"}, "user": {"name": "sdet"}, "event": {"outcome": "success"}}
    ]

    for idx, raw_evt in enumerate(test_stream, 1):
        res = correlator.process_event(raw_evt)
        if res.get("alert"):
            print(f"\n[!] HIGH-PRIORITY SIEM CORRELATION ALERT TRIGGERED (Event #{idx}):")
            print(f"    Rule Name      : {res['rule_name']}")
            print(f"    Severity       : {res['severity']}")
            print(f"    Source IP      : {res['source_ip']}")
            print(f"    Compromised ID : {res['target_user']}")
            print(f"    Failure Count  : {res['prior_failures_detected']} attempts")
        else:
            print(f"[*] Event #{idx} Processed: {res.get('status', 'Nominal')}")
Correlation Output: ========================================================================== SIEM STREAMING CORRELATION & ALERT ENGINE ========================================================================== [*] Event #1 Processed: Recorded failure #1 for 198.51.100.25 [*] Event #2 Processed: Recorded failure #2 for 198.51.100.25 [*] Event #3 Processed: Recorded failure #3 for 198.51.100.25 [!] HIGH-PRIORITY SIEM CORRELATION ALERT TRIGGERED (Event #4): Rule Name : CORR_BRUTEFORCE_SUCCESS Severity : CRITICAL Source IP : 198.51.100.25 Compromised ID : sdet Failure Count : 3 attempts Detection Logic: The engine ignored the single failures as isolated events. When Event #4 arrived as an authenticated success from the same source within 30 seconds of 3 failures, the stateful correlation rule evaluated true and fired a critical alert.
Real-Time Example 8: Debugging SIEM Telemetry Drops & Parser Failures
Troubleshooting common SOC engineering defects: Grok regex parsing mismatches throwing _grokparsefailure, time-drift anomalies corrupting event indexes, and Syslog UDP packet drops under high saturation.
SIEM Pipeline Failures & Engineering Remediations
SIEM DATA PIPELINE FAILURE MODES & TRIAGE:

// ==============================================================================
// PITFALL 1: THE _grokparsefailure TAG (SCHEMA SILENT INGESTION DEATH)
// SYMPTOM: Logs arrive in Elasticsearch/Splunk, but all extracted fields are empty!
// Documents contain tag "_grokparsefailure".
// CAUSE: Vendor updated their software firmware (e.g. Cisco ASA or NGINX), altering
// the date format or adding an extra space in the Syslog header.
// The strict Grok regex pattern failed to match, storing the entire log as raw text!
// REMEDIATION:
// 1. Configure fallback dissect filters: Dissect is faster than regex and handles simple
//    delimiter-separated logs without failing on minor spacing anomalies.
// 2. Set up automated dead-letter queues (DLQ) in Logstash to capture failed documents
//    and alert detection engineers immediately when parsing rates drop.
// ==============================================================================

// ==============================================================================
// PITFALL 2: CLOCK DRIFT & FUTURE-DATED LOG INDEXING
// SYMPTOM: Real-time correlation searches miss active attacks happening right now!
// CAUSE: A domain controller or firewall has a broken NTP daemon; its system clock is
// set 4 hours in the FUTURE.
// The SIEM indexes incoming events under tomorrow's date! Real-time searches looking at
// 'now-15m' evaluate ZERO events because the logs are stored with future timestamps!
// REMEDIATION:
// In Logstash/Fluentbit, enforce timestamp ingestion overrides:
// Store the device reported timestamp in 'event.original_time', but set '@timestamp'
// to the exact time the SIEM collector RECEIVED the packet via Logstash 'ruby { ... }'!
// ==============================================================================

// ==============================================================================
// PITFALL 3: UDP SYSLOG DROPS UNDER NETWORK SATURATION
// SYMPTOM: During an active DDoS or brute-force attack, SIEM shows ZERO logs, exactly
// when visibility is needed most!
// CAUSE: Legacy firewalls configured to transmit Syslog over UDP Port 514.
// Under heavy network load, UDP packets are dropped by switches without retransmission.
// REMEDIATION: Mandate RELIABLE SYSLOG:
// Migrate all log forwarding to TCP with TLS encryption (TCP Port 6514) using RFC 5424,
// or deploy local Filebeat agents with local disk-backed spooling queues.
// ==============================================================================
Triage Summary: - Parser Failures: Deployed Dead-Letter Queues (DLQ) and transitioned brittle regex grok patterns to resilient dissect parsers. - Timestamp Discrepancies: Enforced collector-receipt timestamp binding (@timestamp) to protect searches against host clock skew. - Ingestion Packet Loss: Replaced legacy unencrypted UDP port 514 forwarding with TLS-encrypted TCP with local disk buffering.
Real-Time Example 9: SOC Architecture & SIEM Platforms Reference Matrix
A comprehensive reference summary pairing SOC operational components, SIEM platforms, data pipelines, detection standards, and academic exam keywords for B.Tech engineering students.
SOC & SIEM Engineering Specification Reference Matrix
SOC ARCHITECTURE & SIEM SPECIFICATION MATRIX:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ COMPONENT / PLATFORM    β”‚ ARCHITECTURAL ROLE           β”‚ STANDARDS / TECH β”‚ CORE OPERATIONAL FUNCTION     β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Tier-1 Triage           β”‚ Front-line alert queue       β”‚ MTTA < 15 min    β”‚ Validates alerts, filters     β”‚
β”‚ Analyst                 β”‚ monitoring and triage        β”‚ Shift-based      β”‚ false positives, escalates    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Tier-2 Incident         β”‚ Deep forensic investigation  β”‚ Root-cause scope β”‚ Host isolation, memory dump,  β”‚
β”‚ Responder               β”‚ and containment dispatch     β”‚ MITRE ATT&CK     β”‚ firewall access-list updates  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Tier-3 Threat Hunter    β”‚ Proactive anomaly hunting,   β”‚ Hypothesis-based β”‚ Uncovers fileless malware,    β”‚
β”‚ & Detection Engineer    β”‚ custom detection authoring   β”‚ Sigma / YARA     β”‚ advanced APTs, zero-days      β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Apache Kafka            β”‚ Distributed Streaming Buffer β”‚ Event Queue      β”‚ Prevents SIEM ingest drop     β”‚
β”‚                         β”‚ Ingestion Broker             β”‚ Partitioned      β”‚ during volumetric alert spikesβ”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Elastic Common Schema   β”‚ Standardized Data Schema     β”‚ ECS / OCSF       β”‚ Normalizes multi-vendor data  β”‚
β”‚ (ECS) / OCSF            β”‚ JSON Key-Value Hierarchy     β”‚ Vendor-neutral   β”‚ fields into universal format  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Sigma Standard          β”‚ Detection-as-Code Rule       β”‚ YAML Schema      β”‚ Vendor-agnostic detection;    β”‚
β”‚                         β”‚ Authoring Framework          β”‚ Git Versioned    β”‚ compiles to Splunk, Sentinel  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Windows Sysmon          β”‚ Endpoint Behavioral Telemetryβ”‚ Sysmon XML       β”‚ Logs ProcessCreate, Network,  β”‚
β”‚                         β”‚ Driver (Microsoft Internals) β”‚ Event IDs 1-29   β”‚ CreateRemoteThread injections β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Risk-Based Alerting     β”‚ Entity-Centric Scoring       β”‚ Cumulative Risk  β”‚ Aggregates low-risk alerts to β”‚
β”‚ (RBA Framework)         β”‚ Threshold Engine             β”‚ Score Threshold  β”‚ eliminate SOC alert fatigue   β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ TOP 5 SOC & SIEM ARCHITECTURAL COMMANDMENTS:                                                              β”‚
β”‚ 1. Normalize at Ingestion: Map disparate vendor logs to ECS or OCSF before indexing into storage.         β”‚
β”‚ 2. Buffer High-Velocity Streams: Deploy Kafka or queue brokers upstream of SIEM parsers.                  β”‚
β”‚ 3. Treat Detections as Code: Version control detection rules in Git using vendor-agnostic Sigma.          β”‚
β”‚ 4. Shift to Risk-Based Alerting: Aggregate entity anomalies over time to eliminate alert fatigue.         β”‚
β”‚ 5. Enforce Reliable Log Transport: Mandate TLS-encrypted TCP (RFC 5424) over legacy UDP Syslog.           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Academic & Professional Standard: A Security Operations Center is the command hub of modern enterprise cyber defense. Mastering multi-tier SOC staffing models, telemetry normalization schemas (ECS/OCSF), Sigma detection-as-code engineering, and SIEM correlation engines equips B.Tech students to design scalable security architectures, eliminate operational blind spots, and orchestrate automated defense responses.