Overview
Nothing crossed the perimeter, so the perimeter told you nothing. On Kubernetes, east-west traffic looks like an ephemeral IP talking to another ephemeral IP, and by the time you investigate, the pod is gone and the address reused.
The service graph resolves addresses to identity: which workload, which namespace, which app. A flow then reads as checkout talking to the payments database, not as two IPs.
When you see this
- A workload connects to a service it has never needed before.
- A conversation shows up that your NetworkPolicy does not describe.
Steps
- 01
Run the agent on every node
Deploy the agent as a DaemonSet so every node observes its own traffic. The synapse-stack chart installs the proxy by default and leaves the agent off, so turn it on in your values.
synapse-values.yaml agent: enabled: trueHelm helm upgrade --install synapse-stack gen0sec/synapse-stack \ -n synapse-os --create-namespace \ -f synapse-values.yaml - 02
Turn on the producers
The identity producer maps pod IP to workload, namespace and app; the edge producer compiles NetworkPolicy into the conversations you intended. Both need an API key with identity:write.
Chart values operator: identityProducer: enabled: true edgeProducer: enabled: true apiKeySecret: name: synapse-operator-api-keyDecisionIs the chart older than synapse-stack 0.6.0?Yes Its ClusterRole lacks pods, namespaces and networkpolicies, so both producers fail. Upgrade, or apply the workaround in the operator docs.
No The producers have the access they need.
- 03
Review undeclared conversations
A conversation nobody declared is the signal. It is not proof of compromise, but it is a short, reviewable list, which is more than a flow log gives you.
DecisionIs the conversation intended?Yes Declare it in NetworkPolicy, so it stops appearing.
No Treat the source as suspect: follow the contain a compromised host playbook.
- 04
Enforce it, if you want to
Detection does not stop anything. A smart firewall rule can name workloads rather than addresses: start with log, then switch to drop.
Smart firewall rule, log first identity.k8s.src_workload == "checkout" and identity.k8s.dst_workload == "payments-db"
Common mistakes
- Running more than one cluster without --cluster-id: they share one path and the last writer wins.
- Expecting detection without NetworkPolicy: with no declared edges there is nothing to compare against.
- Relying on workload names when labels are not meaningful.
Escalate when
- An undeclared conversation into a data store or a control plane.
Where this stops working
- This is detection, not prevention. Enforcement still happens in the kernel, through the firewall.
- The baseline is periodic: a pod that lives and dies inside a gap may not resolve.