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.

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.

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.

OT Integrator Access Needs An Expiry Date

Separate retained engineering knowledge from live access, then prove you can disconnect one supplier

The September 2026 FBI/CISA ICS integrator guidance raises two different containment problems: engineering data outside the plant and remote access into it. A practical microsegmentation pattern for supplier-specific access, project closure, and independent revocation.