feat(integrations): OCSF -> SIEM/data-lake pipeline (Vector) - #299
Merged
Conversation
Tier-1 "ready now" data integration. AegisBPF already emits schema-valid OCSF 1.1.0 (File Activity 1001 / Network Activity 4001), so this ships a Vector pipeline that enriches and routes it — no agent code change. - integrations/vector/aegisbpf-ocsf.yaml: journald/k8s source -> remap transforms (add cloud/region, k8s pod/ns/node via Downward API, OCSF observables[], process-lineage correlation_uid) -> env-gated sinks for AWS Security Lake (S3/OCSF), Splunk HEC, and Microsoft Sentinel / generic OCSF-OTLP-HTTP. - integrations/vector/sample-ocsf-event.json: a live-captured (kernel 6.17) File Activity deny event; verifies all OCSF/Security-Lake required fields are present and AegisBPF forensics ride under OCSF `unmapped`. - integrations/vector/README.md: the pipeline guide + per-target setup (Security Lake custom source incl. the JSON->Parquet note, Splunk, Sentinel) + a validation checklist. - Linked from docs/SIEM_INTEGRATION.md and the docs index. Config YAML + sample JSON validated locally; run `vector validate` before deploy. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ErenAri
force-pushed
the
feat/tier1-siem-pipeline
branch
from
August 11, 2026 11:26
c6f4af6 to
5433ab1
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tier-1 "ready now" data integration. AegisBPF already emits schema-valid OCSF 1.1.0, so this ships a Vector pipeline that enriches and routes it to any OCSF consumer — no agent code change.
What's here
integrations/vector/aegisbpf-ocsf.yaml— journald (systemd) /kubernetes_logs(DaemonSet) source →remaptransforms that add cloud/region, k8s pod/ns/node (Downward API), OCSFobservables[], and a process-lineagecorrelation_uid→ env-gated sinks: AWS Security Lake (S3/OCSF), Splunk HEC, Microsoft Sentinel / generic OCSF-OTLP-HTTP.integrations/vector/sample-ocsf-event.json— a live-captured File Activity (1001) deny event (kernel 6.17). Verified: all OCSF/Security-Lake required fields present; AegisBPF forensics (inode/dev/cgroup/exec-lineage) ride under OCSFunmapped.integrations/vector/README.md— pipeline guide, per-target setup (Security Lake custom source incl. the JSON→Parquet note, Splunk, Sentinel, Datadog/Chronicle/CrowdStrike), and a validation checklist.docs/SIEM_INTEGRATION.md+ the docs index; CHANGELOG entry added.Verification
Captured a real OCSF event from
aegisbpf run --event-format=ocsfon this hardware to ground the design (the sample fixture). Config YAML + sample JSON validated locally;vector validateshould be run before deploy (Vector not installed in this env).🤖 Generated with Claude Code