Hari 52: K8s Escape, Falco Blind, Banjir 1000 Alert Palsu
Simulasi red team: keluar dari container Kubernetes, baca kredensial node. Falco diam total. Saat diperbaiki, malah banjir alert palsu. Ini ceritanya.
Hari 48: Intelligent Alert Routing — Falco CRITICAL Alerts ke Slack
Falco CRITICAL alerts otomatis terkirim ke Slack #security-alerts via Python webhook receiver. DNS fix: host.k3d.internal → host.docker.internal. End-to-end test sukses.
Hari 45: Fase 3 Complete — K8s & Runtime Security
15 hari, 6 defense layers, 12 lessons. Fase 3 K8s & Runtime Security selesai! Kubesec 0→12, Checkov 20→0, Falco 29 rules, 6 alerts fired. Defense in depth proven. Retrospective complete.
Hari 44: AI Threat Modeling — 3 Attack Paths
AI (glm-5.2) analyzes K8s cluster config and identifies 3 attack paths: container escape (CVSS 9.8), lateral movement (CVSS 7.5), secret exfiltration (CVSS 8.6). Defense in depth validated — every attack path has multiple mitigations from Day 31-43.
Hari 43: External Secrets — AWS to K8s Sync
External Secrets Operator sync JWT_SECRET dari AWS Secrets Manager ke K8s Secret. Secret Reference Pattern: git cuma referensi, nilai di AWS. ESO SecretSynced dalam 20s. GitHub Push Protection block Checkov report yang contain AWS keys.
Hari 42: Webhook Alerting — Falco to Python Receiver
n8n Docker pull timed out → pivot ke Python webhook receiver. Falcosidekick webhook output enabled. End-to-end: attack → Falco → Falcosidekick → webhook → IF routing CRITICAL to Slack path. 3 alerts received.
Page 2 of 5 • 29 articles