Network Access Control (NAC) is a set of protocols that is used to enforce a security/authentication policy for devices attached to the network. The protocol consists of several pieces:

The picture above shows a typical architecture that NAC would be deployed in. The PAE or Port Authentication Entity is the Gatekeeper. The Gatekeeper blocks access to a port until a user has been authenticated. He awaits the authentication result from the Authenticator and possibly a policy to apply.
The switch contains the PAE and also enforces whatever policy the user ends up being assigned.
The Authenticator takes the credentials that were collected from either the user or the device and gives a pass/fail result back to the PAE. The Authenticator may or may not also be involved in defining policy for the user's connection. In some cases, it simply gives an authentication result, and it is up to the switch to decide on policy. Typical Authenticators are RADIUS, TACACS+, and DIAMETER.
The Policy Manager defines what policy to apply to the user based on the credentials offered, and the authentication result.
NAC is the mechanism on the switch that allows control over the security posture of the port, how and where to authenticate, and determines the source of the policy to be enforced on the port.
NAC, also referred to as network admission control, is a method of bolstering the security of a proprietary network by restricting the availability of network resources to endpoint devices that comply with a defined security policy.
A traditional network access server (NAS) performs authentication and authorization functions for potential users by verifying logon information. In addition to these functions, NAC restricts the data that each particular user can access, as well as implementing anti-threat applications such as firewalls, anti-virus software, and spyware-detection programs. NAC also regulates and restricts things individual subscribers can do once they are connected. NAC is ideal for universities, corporations and agencies where the user environment can be limited, while allowing the implementation of regulatory policies. For example, in colleges or universities, where there are multiple departments, and students use a variety of devices, (e.g., Xboxes, iPads, and laptops), the MAC Authentication Bypass (MAB) feature present in the NAC profile can be implemented along with 802.1x port authentication to maintain another level of security.

Many Enterprise and other secure installations use the 802.1x Port Authentication feature to control access to the Ethernet ports within a facility. The 802.1x protocol forces a user to authenticate using their credentials prior to gaining access to a port. The user is typically authenticated to some backend system such as RADIUS.
For many intelligent devices that support 802.1x this works well to secure the ports for use only by authorized parties. The problem is that there are simple devices such as printers and cameras that may not support 802.1x and backend authorization. In order to handle these use cases, the MAC Authentication Bypass, or MAB, uses the MAC address of the attached device to authenticate to the backend AAA server, typically RADIUS.
It should be noted that, due to the fact that MACs can be easily spoofed by most PCs and other devices, MAB is a weak authentication protocol and as such should be paired with ACLs, firewall rules, and other mechanisms to ensure that proper security is maintained within the network.
For many intelligent devices supported by protocol 802.1x, authentication works well to secure ports used by authorized parties. However, for devices not supported by the 802.1x protocol, MAC Authentication Bypass (MAB) uses the MAC address of the device attached to the back-end server as authentication.
Because the MAC Authentication Bypass is a basic authentication protocol, it should be paired with ACL or firewall rules to ensure that proper security is maintained within the network.

The following NAC profile attributes are available for user creation and editing.
| Note: Username and Password are only visible on EAP-MD5 (specify username/password option and are user-defined. |