Policy Routing for AnyConnect Clients based on Group
We have a lab pod configuration that forces traffic to specific pod routers via PBR on our core switch. When a user chooses a specific group when logging into AnyConnect, we apply a group-unique IP Pool, then enforce routing at the next hop.
While this is a functional configuration, it is cumbersome to maintain configuration at multiple hops on the routing path from user to lab pod. We are looking for a way to simplify this through PBR only on the ASA.
Specifically, since AnyConnect automatically generates an RRI entry in the ASA routing table, it would stand to reason that I should be able to apply a route tag to the RRI entry based on the group used to connect. So far, I can't find a way to do this.
The drawing below shows the basic idea where the firewall and pod routers are in the same network.
We are happy to share changes to the Cisco Threat Grid support experience! Our customers have spoken, and we have listened! You want a single, streamlined, easy to access tool to open, view, and update your cases across Cisco Services. That tool is Cisco’...
Where can I find out how to integrate my Cisco products with Threat Response?
There are quick start guides and instructional videos to help you get set up with your Cisco products and the Cisco Threat Response platform.
Inviting all Security & Networking professionals! We want you to tell us what devices you use to do your work and its screen resolution. Your response will help us improve network and security management tools.
Click here to take the 5-minute s...
This guide is intended to show some nifty and powerful use cases that a lot of customers either want or don’t know they want. There are tons of other content out there for specific knobs or capabilities, but this is looking to be a more complete...