Re: Different posture policy for different network access
Hi, When you create your Posture Policy, create 3 different rules and for each rule use "Other conditions" from there you can use different attributes to determine the source of the connection. E.g. If you use Network Device Groups to group Switches, WLC and VPN Firewalls use the "DEVICE Type EQUALS All Device Types#Firewalls" create another rule for switches and another for WLC, make sure the "Other Conditions" attribute uniquely identifies the different devices. Then apply the requirements for that network access connection type.
Hi All, A customer wants to authenticate Anyconnect VPN users from an ASA using the client installed certificate and then with AD. i.e. Is this a corporate device?Would we recommend authenticating the cert on the ASA then passing the AD check to ISE ...
Hello Team, we are getting alert in FMC stating policy deployment failed, we are running on 6.2.0 version and not sure which version is stable version to re mediate this issue, in one event i have seen restart will resolve this issue but is it perman...
Threat Hunting 101
In the latest Cisco Cybersecurity report, we explore all there is to know about threat hunting and provide a how-to guide for creating a threat hunting team.
Here are some of th...
What Is Cisco Identity Services Engine?
Cisco Identity Services Engine (ISE) is an all-in-one enterprise policy control product that enables comprehensive secure wired, wireless, and Virtual Private Networking (VPN) access.
Cisco ISE offers...
To participate in this event, please use the button to ask your questions
(This event was formerly know as Ask the Expert event)
This topic is a chance to discuss more about the best configuration and troubleshooting pr...