microsegment.io

segment all the things

IPv6 Must Not Bypass Your Containment Policy

One application boundary needs the same outcome over both address families

A practical dual-stack microsegmentation review: map IPv6 reachability, verify Kubernetes enforcement, and test containment separately over IPv4 and IPv6.

Quarantine Must Stop Existing Connections

Blocking the next connection is not the same as stopping the one already carrying traffic

A practical microsegmentation quarantine drill for established sessions, with AWS security group and Kubernetes NetworkPolicy behavior, timing evidence, and scoped response controls.

GPU Monitoring Needs Its Own Containment Boundary

The collector needs access to telemetry. The rest of the network does not.

Recent NVIDIA DCGM Exporter research illustrates why GPU telemetry needs explicit microsegmentation, separate profiling access, and tests from unauthorized workloads.

mTLS Is Not A Containment Policy

A trusted workload identity still needs a narrow list of permitted destinations and operations

Mutual TLS authenticates service connections. Breach containment also needs explicit authorization, network boundaries, and tests using valid but unauthorized workload identities.

The AI Agent Was New. The Trust Failures Were Not.

A 17,600-action intrusion turned one dataset worker into a path toward cluster, cloud, mesh VPN, and source-control access

The July 2026 OpenAI and Hugging Face incident was powered by an autonomous AI agent, but its blast radius came from familiar trust failures. This analysis shows where microsegmentation and workload isolation could have broken the chain.