microsegment.io

segment all the things

Kubernetes Nodes Need Their Own Containment Policy

A namespace boundary is not a host boundary

A practical containment review for Kubernetes nodes and host-network workloads: separate enforcement, restrict exceptions, and test lateral paths.

A DNS Allowlist Is Not a Workload Containment Policy

Control name resolution, then prove which connections remain possible

How to combine protective DNS with microsegmentation: separate resolver access, workload authorization, and quarantine acceptance tests.

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.

Remote Support Must Not Become Server Access

A desktop support session should not inherit a route into server administration

A practical microsegmentation design for separating remote desktop support from server administration, informed by Microsoft's reporting on helpdesk impersonation and RMM abuse.

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.