
π Cybersecurity Β· Data Flow
How security logs from across an organisation reach the SIEM: collection, parsing, enrichment, detection rules and alerts for the SOC.
Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.
Drawing diagramβ¦
Data flow for a SIEM pipeline: endpoint EDR, firewalls, identity provider, cloud audit logs and application logs are collected by agents and syslog forwarders into a log pipeline, parsed into a common schema, enriched with asset inventory, user directory and threat intelligence (IP/domain reputation), stored in hot and cold storage, evaluated by detection rules and UEBA, and alerts create cases for SOC analysts in the SOAR platform. Number the processes and label every flow.
flowchart LR
subgraph EXT ["External entities"]
edr["Endpoint EDR"]
fw["Firewalls"]
idp["Identity Provider"]
cloud_log["Cloud Audit Logs"]
app_log["Application Logs"]
asset_inv["Asset Inventory System"]
user_dir["User Directory"]
threat_intel["Threat Intelligence Feed"]
soar["SOAR Platform"]
end
subgraph PROC ["Processes"]
p1("1.0 Collect raw logs")
p2("2.0 Parse logs to common schema")
p3("3.0 Enrich log events")
p4("4.0 Index and store log data")
p5("5.0 Evaluate detection rules and UEBA")
p6("6.0 Generate and manage SOC cases")
end
subgraph STORE ["Data stores"]
d1[("D1 Hot Storage")]
d2[("D2 Cold Storage")]
end
edr -->|"Raw EDR telemetry"| p1
fw -->|"Syslog firewall events"| p1
idp -->|"Authentication logs"| p1
cloud_log -->|"Audit trail events"| p1
app_log -->|"Raw application logs"| p1
p1 -->|"Aggregated raw log data"| p2
p2 -->|"Normalized event records"| p3
asset_inv -->|"Asset metadata"| p3
user_dir -->|"User profile data"| p3
threat_intel -->|"IP and domain reputation data"| p3
p3 -->|"Enriched log events"| p4
p4 -->|"Hot log data"| d1
p4 -->|"Archival log data"| d2
d1 -->|"Indexed event data"| p5
p5 -->|"Detection alerts and anomalies"| p6
p6 -->|"Case details"| soarA data flow diagram with 15 processes and outside parties, 2 data stores and 16 data flows.
Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.
A zero trust access model: every request to an internal app is checked for user identity, device health and policy, whether it comes from the office or home.
A security incident response process based on the NIST lifecycle: detect, triage, contain, eradicate, recover and learn.
How SAML single sign-on works when an employee opens a SaaS app: redirect to the company identity provider, MFA and a signed assertion.
A classic secure network layout: internet-facing services in a DMZ between two firewalls, with internal systems and databases never exposed directly.
A STRIDE threat model for a web application, listing example threats in each category with the main mitigations.
The life of a vulnerability finding: discovered by a scanner, triaged, assigned, fixed, verified and closed, or accepted as risk.