In a large campus network, you need to control which users can access which resources.
Traditional ACLs work, but they create a major scalability problem when your network grows.The IP-Based Segmentation Problem
Your network uses ACLs to control which devices can talk to which resources.
But traditional ACLs are based on IP addresses. When a device moves, gets a new IP, or when your network grows, you have to update every ACL on every switch.Imagine your campus network has three groups of users: Employees, Contractors, and Guests.
You want Employees to access the server VLAN, Contractors to reach only specific resources, and Guests to access only the Internet.With traditional ACLs, you write rules based on source and destination IP addresses.

Figure 1 – IP-based ACLs work
This works as long as every user stays on the same subnet.
But what happens when an Employee moves to a different floor and gets a new IP address?
Figure 2 – Employee moved, ACL broken
Your ACLs no longer match. You have to update the rules manually.
This approach does not scale. In a large campus with hundreds of switches and thousands of users, maintaining IP-based ACLs across every device becomes unmanageable.Answer the question below
Traditional ACLs use which type of address to filter traffic?
TrustSec at a Glance
Cisco TrustSec takes a different approach.
Instead of filtering by IP address, TrustSec classifies users and devices by identity, not IP addresses.
Figure 3 – SGT follows user identity
When a user connects to the network, your switch assigns a Security Group Tag (SGT) to their traffic.
This tag stays with the traffic as it crosses the network. It does not matter which port, VLAN, or subnet the user is on.Policies are then enforced based on the SGT, not the IP address.
If an Employee moves to a different floor, their SGT stays the same. No ACL changes needed.Answer the question below
Does TrustSec classify traffic based on IP addresses or identity?
You've seen the problem TrustSec solves. Now let's break down exactly how it works.
TrustSec operates in two main steps: first, your network assigns an SGT to each user based on their identity. Then, your network enforces security policies using these tags.Step 1: SGT Assignment
When a user authenticates to the network (typically through 802.1X), the RADIUS server (like Cisco ISE) returns an SGT value along with the authentication response.
Your access switch then tags every frame from that user with the assigned Security Group Tag.
For example, Cisco ISE assigns:
SGT 10 to Employees
SGT 20 to Contractors
SGT 30 to Guests

Figure 4 – SGT assigned via 802.1X authentication
The SGT travels with the user's traffic across the network. This means that no matter which switch the user connects to, their identity and permissions follow them automatically.
Answer the question below
What is the name of the tag that TrustSec assigns to classify traffic?
Step 2: SGACL Enforcement
Now that every user's traffic carries an SGT, how does your network actually use it to enforce security policies?
The enforcement happens at the point where traffic needs to be controlled, typically on switches or routers closer to the destination.
These devices apply a Security Group ACL (SGACL).An SGACL does not use IP addresses. Instead, it uses SGT values.
The logic is simple: source SGT → destination SGT → permit or deny.

Figure 5 – SGACL enforcement by SGT
For example, with your server tagged as SGT 100:
Employees (SGT 10) → Servers (SGT 100) = permit (full access)
Contractors (SGT 20) → Servers (SGT 100) = permit TCP 443 only (HTTPS)
Guests (SGT 30) → Servers (SGT 100) = deny (blocked)
These policies are defined centrally on Cisco ISE and pushed to your switches automatically.
You never have to manually write ACLs on individual switches. When a new group is created or a policy changes, ISE updates every enforcement point in your network automatically.
Answer the question below
What type of ACL uses SGT values instead of IP addresses?
You understand how TrustSec assigns SGTs and enforces policies. Let's now verify that everything is working correctly on your switches.
Checking SGT Assignments
Run
show cts role-based sgt-map allto see which IP addresses have been assigned an SGT:L3Switch# show cts role-based sgt-map all Active IPv4-SGT Bindings Information IP Address SGT Source ============================================ 192.168.1.11 10 INTERNAL 192.168.1.12 20 INTERNAL 192.168.1.13 30 INTERNAL IP-SGT Active Bindings Summary ============================================ Total number of INTERNAL bindings = 3 Total number of active bindings = 3The output confirms each user has been tagged:
192.168.1.11 → SGT 10 (Employee)
192.168.1.12 → SGT 20 (Contractor)
192.168.1.13 → SGT 30 (Guest)
Checking SGACL Policies
Now run
show cts role-based permissionsto see the enforcement policies:L3Switch# show cts role-based permissions IPv4 Role-based permissions default: Permit IP-00 IPv4 Role-based permissions from group 10:Employees to group 100:Servers: SGACL name Permit SGACL IP version permission: permit ip IPv4 Role-based permissions from group 20:Contractors to group 100:Servers: SGACL name Limited_Access SGACL IP version permission: permit tcp dst eq 443 deny ip IPv4 Role-based permissions from group 30:Guests to group 100:Servers: SGACL name Deny_All SGACL IP version permission: deny ipEmployees (SGT 10) have full access to Servers (SGT 100).
Contractors (SGT 20) can only reach Servers on HTTPS (port 443).
Guests (SGT 30) are completely denied.
All of these policies were pushed automatically by Cisco ISE.
No manual ACL was written on this switch. The enforcement is based entirely on source SGT and destination SGT.Answer the question below
In a TrustSec policy, what two values determine whether traffic is permitted or denied?
Answer the question below
A contractor opens SSH (TCP 22) to a server in group 100:Servers: which SGACL drops it?
Answer the question below
With no Guests-to-Printers rule, which policy decides Guest (SGT 30) traffic to the printers?