Fortinet NSE5_FSW_AD-7.6: FortiSwitch NAC with FortiGate
Network access control on a FortiSwitch deployment combines endpoint identity, port state and the policies enforced by the network. FortiGate-managed FortiSwitches can participate in access control arrangements, but the exact capabilities depend on FortiOS, FortiSwitchOS, authentication services and deployment mode. “NAC enabled” is not enough to prove that the right device has the right access. The practical objective is to make identity, authorization, fallback behavior and evidence observable across a wired connection.
On this page
Identify the device and its required access
Classify managed workstations, unmanaged devices, contractors, phones, printers and infrastructure equipment. Each class should have a documented owner and least-privilege network path. A general-purpose user port should not grant infrastructure management access merely because the client has a valid IP address. If a user device and a phone share an edge port, document the supported access model and its failure behavior rather than assuming one set of settings protects both.
Understand authentication and authorization boundaries
Where supported, 802.1X uses a supplicant, authenticator and authentication server to determine network admission. MAC-based mechanisms may be needed for devices that cannot run a supplicant, but a MAC address is not strong proof of identity. Map the result to an appropriate VLAN, role or policy and verify how FortiGate applies routing and security enforcement. Protect the management path separately from endpoint admission decisions.
Design safe failures and exceptions
Decide what happens if the authentication server, directory or switch-management service is unavailable. A fail-open policy can keep operations moving at the cost of exposure; a fail-closed policy can interrupt critical services. For necessary exceptions, set an accountable owner, expiry, compensating restrictions and monitoring. Do not silently exempt devices because a deployment test failed. Every fallback should be tested in an authorized lab before production rollout.
Troubleshoot admission without bypassing controls
For a rejected client, trace physical link, supplicant state, certificate or credential validity, RADIUS reachability, server decision, switch authorization and resulting network policy. Correlate logs and timestamps instead of repeatedly cycling the port or disabling access controls. If a client authenticates but still cannot reach an application, follow the assigned VLAN and firewall path. Separate an admission failure from downstream DNS, DHCP and routing failures.
Demonstrate policy effectiveness
Maintain test cases for an approved employee endpoint, unauthorized device, guest, phone and expired exception. Confirm not only that intended access works, but that prohibited access fails and the reason is recorded. Review account lifecycle and certificates with identity owners. See Fortinet’s exam page for supported product/version context; this article should not be used as a substitute for configuration guides or security approval.