logging-architecture
Skill0 starsChanged 12 days agoMITView on GitHub
Design security logging architecture — what each system must log, collection tiers (agents, syslog, cloud-native exports, APIs), pipeline/routing (Cribl, Vector, Kafka), SIEM vs. data lake storage (OCSF, Security Lake), retention tiers, integrity, access control and cost management. Use when designing or modernizing SIEM/data platforms, setting application logging standards, or estimating log costs.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cvsz/zomegatheir own version, first seen Sep 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- cvsz/zomega★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository273 other files it gives its agents.
- ad-attack-path-analysisSkill
- adcs-security-reviewSkill
- ad-privileged-access-reviewSkill
- dcsync-detectionSkill
- gpo-security-reviewSkill
- kerberos-attack-detectionSkill
- agent-tool-permission-reviewSkill
- ai-incident-responseSkill
- llm-gateway-controlsSkill
- llm-security-evaluationSkill
- mcp-server-security-reviewSkill
- model-artifact-securitySkill
- prompt-injection-reviewSkill
- rag-security-reviewSkill
- api-abuse-detectionSkill
- api-authorization-testingSkill
- api-inventorySkill
- api-schema-securitySkill
- dast-baselineSkill
- sast-triageSkill
- sca-dependency-riskSkill
- secure-code-reviewSkill
- security-requirementsSkill
- threat-modelingSkill
- asset-criticality-tieringSkill
- asset-inventory-reconciliationSkill
- external-attack-surface-reviewSkill
- shadow-it-discoverySkill
- aws-credential-compromiseSkill
- aws-iam-reviewSkill
- aws-org-guardrailsSkill
- cloudtrail-investigationSkill
- guardduty-triageSkill
- s3-exposure-reviewSkill
- azure-activity-investigationSkill
- azure-rbac-reviewSkill
- conditional-access-reviewSkill
- entra-audit-investigationSkill
- entra-signin-investigationSkill
- backup-assuranceSkill
- critical-service-mappingSkill
- ransomware-recoverySkill
- recovery-exerciseSkill
- cloud-exposure-reviewSkill
- cloud-incident-responseSkill
- cloud-logging-baselineSkill
- cloud-posture-assessmentSkill
- audit-evidence-packageSkill
- continuous-control-monitoringSkill
- control-mappingSkill
- control-testing-samplingSkill
- container-incidentSkill
- dockerfile-hardeningSkill
- image-scanningSkill
- runtime-detection-falcoSkill
- db-audit-loggingSkill
- db-exfiltration-investigationSkill
- db-hardeningSkill
- db-privilege-reviewSkill
- data-classificationSkill
- The first 60 shown.
The file
Files
Security Logging Architecture
Layers
- Sources: identity (IdP, AD), endpoints (EDR, Sysmon, auditd), network (firewall, proxy, DNS, NDR/Zeek), cloud control/data plane, SaaS, applications, databases.
- Collection: agents (Elastic Agent, Splunk UF, Azure Monitor Agent, Fluent Bit), syslog over TLS (RFC 5425), cloud exports (S3/Event Hub/Pub/Sub), API pollers.
- Pipeline: parse, normalize (OCSF/ECS/ASIM), enrich (asset, identity, geo), filter/reduce noise, redact (
telemetry-minimization), route by value: SIEM hot tier for detections, data lake (S3/ADLS/GCS + Athena/BigQuery, Amazon Security Lake in OCSF) for bulk/long retention. - Storage & analytics: SIEM for real-time detection; lake for hunting/forensics with search-on-demand.
- Consumers: SOC, IR, hunting, compliance, ML.
Application logging standard (minimum)
Authentication events (success/failure, MFA), authorization failures, admin actions, data export/bulk access, input validation failures at boundaries, configuration changes, security-relevant errors — with timestamp (UTC, ISO-8601), user/principal ID, tenant, source IP, request ID/trace ID, action, object, outcome. JSON structured; no secrets/PII payloads.
Design checks
- Buffering/backpressure so outages don't lose logs (persistent queues).
- Time sync (NTP) everywhere; ingest time vs. event time recorded.
- Integrity: write-once storage for archives, separate admin domain for log platform.
- Access: role-based, audit of searches on sensitive indexes.
- Cost: price per GB per tier; reduce verbose sources (filter debug, sample flow logs for non-critical VPCs) rather than dropping security-critical events.
- Health monitoring (
log-pipeline-health).
Output
Architecture diagram + Source | Events | Collector | Pipeline transforms | Destination tier | Retention | Owner | Cost/GB/day
Related skills
log-source-onboarding, cloud-logging-baseline, field-normalization, telemetry-minimization
References
- NSA/CISA Best Practices for Event Logging and Threat Detection: https://www.cisa.gov/resources-tools/resources/best-practices-event-logging-and-threat-detection
- OWASP Logging Cheat Sheet: https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html
- Amazon Security Lake (OCSF): https://docs.aws.amazon.com/security-lake/latest/userguide/what-is-security-lake.html
- OCSF: https://schema.ocsf.io/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.