The ATT&CK Segmentation Layer Is Now Updated to v19.1

Fri, 10 Jul 2026 00:00:00 +0000

The microsegment.io ATT&CK Navigator layer for Network Segmentation is now refreshed to MITRE ATT&CK v19.1.

This is not a dramatic update in the sense of new colors, new scoring, or a long list of new techniques. The useful part is more boring, and probably more important: the mapping stayed stable. MITRE’s current Enterprise ATT&CK data still maps M1030 Network Segmentation to 44 technique and tactic entries across 37 unique technique IDs.

That stability is worth paying attention to. It means the original point from the 2019 ATT&CK segmentation article still holds in 2026: segmentation keeps appearing across the attack lifecycle because attackers need reachability. They need paths to remote services, identity infrastructure, management systems, deployment tooling, configuration stores, command-and-control channels, and exfiltration routes. If those paths are broad, implicit, or poorly governed, the attacker gets options. If those paths are narrow, explicit, and enforced close to the systems that matter, the attacker has fewer moves available.

What Good L3/L4 Policy Can Actually Do

Thu, 09 Jul 2026 00:00:00 +0000

In 2019 I published a short article about MITRE ATT&CK and segmentation.

The point was simple: when ATT&CK maps adversary techniques to mitigations, network segmentation shows up in more places than many people expect. It is not only a perimeter control. It appears across the attack lifecycle because attackers need reach.

That old point still holds.

But it deserves a 2026 reassessment.

The original post was written in a world where many segmentation conversations still meant VLANs, firewall zones, and large network boundaries. Today the conversation is broader. We have cloud security groups, Kubernetes network policies, host firewalls, software-defined segmentation, identity-aware access paths, workload labels, service maps, and microsegmentation platforms.

Network-Segmentation on microsegment.io

The ATT&CK Segmentation Layer Is Now Updated to v19.1

What Good L3/L4 Policy Can Actually Do