distinguishing between certs for anyconnect VPN access
How can I distinguish between certificates for authorizing anyconnect VPN access?
Our certificates are being generated by microsoft with auto-enrollment.
It appears as though you can apply different connection profiles based on the fields in the subject of the certificate..and then ultimately apply a group profile based on the connection profile....but the fields in the subject are being autopopulated by data from AD.
For example, we have certificate A which has a keylen of 1024...generate new certs with keylen of 2048. We need to 1024 certs for another application so we cannot revoke/remove them...how can I ensure VPN users can only authenticate with a 2048 Cert?
Or another use case...I install one cert on a notebook computer, and another one on a desktop. I want to distinguish between the types of access I grant to a desktop Vs. a laptop...is there a way to have anyconnect identify some unique parameter of the certificate so that authentication with one yields different results from authentication with the other? Another possible use case for this could be trying to distinguish between a personally owned iphone and a corporate owned iphone....or a high security ipad used for specific applications only vs an end user BYOD ipad.
For all versions of the Email Security Appliance (ESA) and Security Management Appliance (SMA), some Secure Sockets Link (SSL) certificates issued from the QuoVadis root certificate authority (CA) trust chain before 2021-03-31 cannot b...
Automation and programmability for networking and security are increasingly important topics. Every release since ISE 1.2 has included new REST API capabilities to better automate and integrate ISE with the rest of your network, appli...
The latest iteration (v2.3.4) of the Cisco Secure Firewall Migration Tool adds public beta support for S2S VPN migrations from ASA:
Policy-based (crypto map) Pre-Shared key authentication type VPN configuration to Firepower Management Center
Cisco Defense Orchestrator (CDO) is a cloud-based, multi-device manager that manages security products like Adaptive Security Appliance (ASA), Firepower Threat Defense next-generation firewall, and Meraki devices, to name a few.
We make improvement...
This document presents the ISE data limiting best practices that can dramatically improve the system performance on ISE.
Your deployment may be impacted if the alarms tab on ISE shows High load average, high CPU or high memoy usage alarm...