Users, not IPs: identity-based policies and admin access
▶ Start the interactive lesson
Finance moves desks every quarter, and laptops roam between Wi-Fi and docks. Rules based on IP addresses keep breaking. "Write rules for people and groups," Maya says, "and let the firewall learn which IP each person is using right now."
Key points
- Identity rules need an IP-to-user map. Ways to build it: passive (read Windows domain-controller logon events, RADIUS accounting from Wi-Fi/802.1X, syslog from other systems, or an identity platform such as a NAC) and active (a captive portal or authentication prompt for unknown users).
- Group membership comes from the directory (LDAP / Active Directory, or a cloud directory). Rules reference groups, not usernames.
- Authentication sources: local users, LDAP, RADIUS, SAML single sign-on and MFA. Watch for stale mappings (a user logs off but the IP still maps to them) and shared devices.
- Admin access is identity too: separate admin accounts, role-based access (read-only for the service desk, full for engineers), MFA, trusted management hosts, and logging of every change.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →