> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contain Lateral Movement Through Identity-Based Segmentation

> How Aviatrix limits the blast radius of a compromise with identity-based segmentation and inline inspection, covering the business case and key components.

Most cloud networks trust traffic between workloads by default, so one
compromised workload can spread across your whole estate. Aviatrix limits the
blast radius by enforcing policy between workloads, not only at the internet
edge, and by introducing that policy in monitor mode before you enforce it.

## Business Challenge

Flat or loosely segmented networks let an attacker move from an initial foothold
to databases, identity systems, and management planes. Host-agent
microsegmentation does not cover every workload type, because serverless
functions, managed services, and AI agents cannot run an agent. Native security
groups are scoped to one VPC or VNet and one cloud, so they cannot express a
policy that spans accounts and clouds.

## The Business Case for East-West Segmentation

### Risk Mitigation

* **A bounded blast radius.** A compromise in one segment cannot reach another
  unless a rule explicitly permits it.
* **Zero trust by default.** A deny rule at the end of the policy blocks every
  flow that you have not permitted.
* **Environment separation.** Production, development, and shared services stay
  apart at the routing layer as well as in firewall rules.
* **Protection without a host agent.** Workloads that cannot run an agent still
  fall under the same policy when their traffic crosses a gateway.
* **Inspection for known attacks.** Intrusion prevention drops traffic between
  workloads that matches attack signatures.

### Operational Efficiency

* **Identity-based policy, not IP-based policy.** Rules reference groups of
  workloads, so they follow workloads as addresses change.
* **One policy across accounts and clouds.** Teams stop maintaining a separate
  rule set for each VPC, VNet, and cloud.
* **Safe rollout.** Teams observe real traffic in monitor mode, then enforce,
  and can back out a rule without redesigning the network.

### Governance

* **A documented baseline.** Default deny gives you a written statement of what
  each segment is allowed to reach.
* **A change history.** You can see who changed which rule and when as policy
  tightens.
* **Evidence for auditors.** Enforced segmentation is a control that you can
  demonstrate rather than describe.
* **Early warning.** Anomaly detection highlights unusual traffic patterns, so
  teams can spot lateral movement while an attacker is still probing.

## How Aviatrix Addresses Lateral Movement

Aviatrix Distributed Cloud Firewall (DCF) applies stateful rules between
SmartGroups at the gateways that already carry your traffic. Because enforcement
sits in the network path rather than on the host, the same policy covers virtual
machines and other workloads whose traffic crosses an Aviatrix gateway, within
one cloud or across clouds. Traffic that stays inside a VPC or VNet, or that
reaches a managed service over a private endpoint, does not cross a gateway, so
apply native controls there.

![East-west containment architecture: a compromised workload in one segment sends traffic toward other workloads through Aviatrix gateways running Distributed Cloud Firewall, which permits flows explicitly allowed between SmartGroups, denies and logs lateral movement to other segments, and keeps network domains separate at the routing layer.](https://mintcdn.com/aviatrix-14b37c43/fGohijthCmM99wVL/images/solutions/contain-lateral-movement/east-west-containment-architecture.png?fit=max\&auto=format\&n=fGohijthCmM99wVL\&q=85\&s=d2f78c14c9d61d3debce679563b9248e)

*Gateways permit only the flows that rules allow between segments, and block and
log the rest.*

### Segment by Identity, Then Enforce Gradually

You group workloads into SmartGroups, for example by tag, resource attribute, or
CIDR, and write rules between those groups. Rules start in watch mode so that
you see which flows are in use, and move to enforcement after you review the
results.

### Separate Network Domains

Transit Network Segmentation places Spoke attachments in network domains and
connects domains only through connection policies. It complements identity-based
rules with separation at the routing layer.

### Protect East-West Traffic in the Fabric

East-west traffic between Spokes, VPCs, and VNets passes through Aviatrix
gateways, where DCF can inspect and enforce it. For AWS Transit Gateway
environments, you can add transparent protection without replacing the existing
Transit Gateway. Where an organization requires third-party next-generation
firewalls, Transit FireNet inserts them into the transit path, and DCF handles
the rest of the policy.

### Inspect and Detect

DCF intrusion prevention (IPS) inspects traffic against signature profiles and
supports custom rulesets. You attach an IPS profile to the rules that need it,
so inspection applies only to the traffic that you select. IPS signatures need
visibility into encrypted traffic, so a rule can enable TLS decryption for only
the flows that need it. CoPilot Network Behavior Analytics identifies unusual
network behavior in your VPCs and VNets that could represent threats, and can
alert you when it detects an anomaly.

> [!NOTE]
>
> DCF intrusion prevention is generally available in Controller 9.0 and later.
> In Controller 8.2, it is a Preview feature.

## Key Components

> [card] [Distributed Cloud Firewall](https://docs.aviatrix.com/docs/enterprise/9.0/concepts-architectures/components/dcf/dcf-overview.md)
>
> Stateful, identity-based rules between SmartGroups with a default deny.

> [card] [SmartGroups](https://docs.aviatrix.com/docs/enterprise/9.0/concepts-architectures/components/dcf/smartgroups-about.md)
>
> Groups of workloads by tag, resource attribute, or CIDR so that policy
> follows the workload.

> [card] [Transit Segmentation](https://docs.aviatrix.com/docs/enterprise/9.0/concepts-architectures/components/security/transit-segmentation-faq.md)
>
> Network domains and connection policies that isolate groups of Spokes at the
> routing layer.

> [card] [East-West Protection](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/east-west/east-west-overview.md)
>
> Enforcement for traffic between Spokes, VPCs, and VNets, including
> transparent protection for AWS Transit Gateway.

> [card] [Intrusion Prevention](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/dcf/ips.md)
>
> Signature-based inspection that you attach to DCF rules.

> [card] [Network Anomalies](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/network-anomalies.md)
>
> CoPilot detection of unusual network behavior.

## Related Documentation

Use these documents to plan and implement segmentation.

### Configuration Guides

* [Enabling Distributed Cloud Firewall](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/dcf/dcf-enable-feature.md)
  — turn on DCF and its default behavior.
* [Creating SmartGroups](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/dcf/dcf-create-groups.md)
  — define the workload identities that your rules reference.
* [Auditing DCF Policy Changes](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/dcf/policy-audit.md)
  — review who changed which rule and when.
* [Network Segmentation](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/network-segmentation-secured.md)
  — configure network domains and connection policies.
* [Transparent DCF Protection for AWS Transit Gateway](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/east-west/transparent-dcf-protection-aws-tgw.md)
  — add east-west enforcement to an existing AWS Transit Gateway design.
* [Intrusion Prevention](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/dcf/ips.md)
  — enable IPS and attach profiles to DCF rules. IPS is generally available in
  Controller 9.0 and later, and is a Preview feature in Controller 8.2.
* [Network Anomalies](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/network-anomalies.md)
  — review and tune anomaly detection in CoPilot.
* [Distributed Cloud Firewall Settings](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/dcf/dcf-settings.md)
  — configure global DCF behavior, including decryption and IPS settings.
* [Transit FireNet](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/firenet/transit-firenet-overview.md)
  — insert third-party firewalls in the transit path.

### Reference

* [Multicloud Design Patterns](https://docs.aviatrix.com/docs/enterprise/9.0/concepts-architectures/architecture/connectivity/multi-cloud-design-patterns.md)
  — reference topologies for Transit and Spoke.

* [East-West Overview](https://docs.aviatrix.com/docs/enterprise/9.0/guides/security/east-west/east-west-overview.md)
  — supported east-west deployment patterns and Controller versions.

* [Distributed Cloud Firewall Capabilities](https://docs.aviatrix.com/docs/enterprise/9.0/reference/dcf/dcf-capabilities.md)
  — supported capabilities by Controller version.

* [Terraform Provider](https://docs.aviatrix.com/docs/enterprise/9.0/reference/terraform/provider.md)
  — declare SmartGroups and DCF rules as code.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.