executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
blue-team-soc-operationsMaster methodologies for SIEM architecture, incident response, and threat hunting.
Independent GitHub snapshot · Automated classification · Original documentation governs
A resilient Security Operations Center (SOC) relies on a robust Security Information and Event Management (SIEM) architecture. The objective is holistic visibility across the enterprise telemetry plane, orchestrating log ingestion, normalization, correlation, and alerting. Data ontology must prioritize high-fidelity indicators over raw volume, enabling real-time detection engineering and proactive defense mechanisms.
The structural foundation of incident handling dictates a deterministic approach to anomaly resolution.
Proactive threat hunting transcends automated alerting. It requires the formulation of intelligence-driven hypotheses—assuming a state of compromise—to query historical telemetry for covert adversary behaviors, typically aligned with MITRE ATT&CK defensive mappings.
Conceptual log analysis demands parsing unstructured security events into actionable structured data. It involves correlating disparate timestamped entries across disparate systems (e.g., EDR, NDR, IAM) to reconstruct temporal attack vectors.
%%{init: {"theme": "default", "flowchart": {"useMaxWidth": true}}}%%
flowchart TD
A[Telemetry Sources] --> B[Log Aggregation]
B --> C[SIEM Correlation Engine]
C --> D{Alert Generation}
D -- True Positive --> E[Incident Identification]
D -- False Positive --> F[Detection Tuning]
E --> G[Containment Strategy]
G --> H[Eradication & Forensics]
H --> I[Recovery Operations]
I --> J[Post-Incident Review]
J --> C