- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2016 12:32 PM - edited 03-11-2019 12:16 AM
Hi,
Apart from MAR and EAP Chaining, what other methods/work arounds are there for ensuing employees access the network from domain joined computers only when using EAP-TLS?
Solved! Go to Solution.
- Labels:
-
AAA
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2016 05:21 PM
Hi there! Just to confirm: Is your requirement:
1. For dual factor authentication (User+machine)?
2. Prevent non-domain joined machines from accessing the network?
If it is #1, then I would suggest exploring a "chaining" method. One of those can be EAP-Chaining, however, to use that method you will also need to deploy and rely on the Cisco AnyConnect NAM module. Also, this method only works for Windows machines and it is not supported on MACs, Linux and Mobile. You can also do PEAP with CWA chaining. With this method, your first method of authentication is PEAP with machine authentication. After that authentication is successful the user would be redirected to the Web Portal in ISE where he/she would have to enter domain user based credentials before access to the network is given.
If it is #2, then I would suggest to simply use PEAP with machine based authentication. That way only domain joined machines would be allowed to successfully authenticate and authorize on the network. The main caveat here is to ensure that your AD environment is well secured as I think by default any domain user can join up to 10 machines to the domain. So, if AD is locked down properly then using PEAP with machine authentication is the way to go.
I hope this helps!
Thank you for rating helpful posts!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2016 05:21 PM
Hi there! Just to confirm: Is your requirement:
1. For dual factor authentication (User+machine)?
2. Prevent non-domain joined machines from accessing the network?
If it is #1, then I would suggest exploring a "chaining" method. One of those can be EAP-Chaining, however, to use that method you will also need to deploy and rely on the Cisco AnyConnect NAM module. Also, this method only works for Windows machines and it is not supported on MACs, Linux and Mobile. You can also do PEAP with CWA chaining. With this method, your first method of authentication is PEAP with machine authentication. After that authentication is successful the user would be redirected to the Web Portal in ISE where he/she would have to enter domain user based credentials before access to the network is given.
If it is #2, then I would suggest to simply use PEAP with machine based authentication. That way only domain joined machines would be allowed to successfully authenticate and authorize on the network. The main caveat here is to ensure that your AD environment is well secured as I think by default any domain user can join up to 10 machines to the domain. So, if AD is locked down properly then using PEAP with machine authentication is the way to go.
I hope this helps!
Thank you for rating helpful posts!
