Mobile endpoints utilizing random MAC address is nothing new. But the way it is utilized has changed since it was first introduced. In the beginning, the randomization of MAC was used to probe for known wireless networks by the devices. By randomizing the MAC address used in the probe request frame, devices were able to hide real MAC address thus providing some level of privacy. Fast forward few years, now devices started using random MAC addresses for the association to the wireless networks. This causes issue on the network elements which relies on MAC addresses to uniquely identify the endpoint or the user behind it. The implementations of MAC randomization are different depending on the vendor but here are few examples of the behavior:
Windows 10
Can setup randomization both globally for all wireless connections or per network profile (SSID).
Randomization is disabled by default out-of-the-box
On the network profile, user can also configure Windows 10 to generate different random MAC every day
Once random MAC is used for a given network profile, it will keep using it as long as user doesn't delete the network profile
If user deletes the network profile, next time a different random MAC will be used
Android 10
Can setup randomization per network profile (SSID).
Randomization is enabled by default out-of-the-box
Once random MAC is used for a given network profile, it will keep using it even after user deletes the network profile and recreates it
Although this document is focused on ISE, it should be noted that the impact doesn’t stop with ISE. As MAC address as a unique identifier is hard-coded into products and solutions throughout Cisco and 3rd party, which includes MDM/EMM, wireless performance monitoring, and device profiling systems. ISE or wireless authentication system is in a unique position in the network to control the use of random MAC address for the rest of the network. The good news is that generation of random MAC follows rules set by IEEE. As noted in the diagram below, locally significant address 2’s bit of first byte is set to one. Any MAC address that has locally significant bit set as one and is also a unicast address can be considered a random MAC address.
So based on the rule, all of the numbers below would qualify as a random MAC address. For a simple rule, any MAC address’ first octet that ends 2,6,A,E would be a random MAC address.
With this, ISE policy rule can be created using a regular expression match against the RADIUS Calling-Station-ID attribute within the RADIUS Access-Request which includes the client MAC on virtually all Cisco devices: ^.[26AEae].*
Now that ISE can detect the random MAC, here are few options to consider:
User experience
Note
1. Deny Access
User will not be able to connect to the wireless network
Bad experience as there could be many other reasons that user cannot connect to the network
2. Deny Access + Instructions
User will be able to connect, but will be redirected to a help page instructing user to disable random MAC feature for this network
Best option, if you do not want random MAC to enter the network.
3. Permit Access + Short session timeout
User will be able to connect, but after the device goes to sleep and awakes, user will be asked to login again
4. Permit Access + Short purge cycle
User will be able to connect, but user will be asked to login after X # of days
5. Permit Access + Consent
User will be prompted but can bypass and gain same level of access as unique MAC
6. Permit Access
User will be able to connect and there are no difference between random MAC and unique MAC
Note: Option 3-6 can be augmented with additional permission to restrict bandwidth, ACL, VLAN, etc. if needed.
The following devices have been confirmed to match the random MAC policy rule:
Windows 10 Home Build 19041 with Intel Wireless Adapter AC 9560
Android 10 on Pixel 3
Android 10 on Samsung S20 Plus
Android 10 on Samsung S10 Plus
... View more
.jpg "VIP Advocate"){kind=icon}
