Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Is there a way to modify the ASDM launcher or related files to display the ASDM security banner prior to a user logging on? Or does Cisco have plans to modify or allow to change when the ASDM security banner is displayed? This is currently a requir...
I am having difficulty with AAA setup on my recently upgraded ASA 5520. I upgraded from 8.3(1) to 8.4(4) and my AAA no longer works. If I use Kerberos I receive time skew errors (works fine on my remaining 8.3(1) ASAs) and when I setup LDAP I get "...
I am trying think of a better way to provide redundancy on some internally protected networks. We maintain our own WAN/backbone between our primary site and backup site. Is it possible to have two Cisco ASA 5550s in setup for failover at completely...
I have several Cisco ASA 5505s with the ASA-SSC-AIP-5 IPS modules installed. Some of the IPS sensors are responsive, but others are quite stubborn and unresponsive. I can reach all of them via the session 1 from the host ASAs SSH terminal or consol...
I am using an ASA5550 for a complex secure network that has at least six "outside" networks. Each "outside" network is assigned to a specific port each set at level "0". I also have a DMZ, set to level "50". I am having difficulty with passing tra...
Yes, I was able to get it taken care of this morning. By default the L-ASA5545-TAMC comes with the Control license, it was an oversight on Cisco's part and it was never sent. The TAC engineer I worked with this morning corrected the oversight. I r...
I have L-ASA5545-TAMC= : Cisco ASA5545 FirePOWER IPS, Apps, AMP and URL Licenses, which should be Protect, Control, URL and Malware, but license files received from Cisco only contain Malware and URL.
As long as you have implemented a strong password policy and the related items such as max attempts, etc on the Windows side you should be ok. We just added a rule on our SIEM to notify us on any RDP hosts that have repeated failed attempts. Just ...
