I have inherited a very old and very ugly ASA firewall policy. I'm more of a Checkpoint firewall engineer but do have some basic Cisco knowledge and have been muddling through on the CLI as best I can until we can get this site to our corporate standards.
That said, we have recently deployed a proxy server/content filter for internet browsing and due to the positioning of this, we have had to implement a rather large nat0 ACL so that browser traffic gets sent (via WCCP managed on the internet router, one step beyond the ASA outbound), it is not NAT'd. While this works fine in most cases, its obviously problematic in a few situations (such as any service other than http/https still needing a public NAT for traversing the internet. Currently this is handled via overload addresses on the Internet router).
My critical/immediate issue right now is that I've got an entry in the nat0 ACL for a /24 internal network, but I need to essentially override that for a single IP within that /24 network range so that this one particular source IP gets a specific public NAT when traversing the internet.
I guess what I'm looking for is some kind of ACL I can write for a specific host which would be 'more specific' and therefore take precedent over the nat0 ACL for the /24 network? Or does the nat0 ACL 'trump all other ACLs' ?
Any help is appreciated. Note that upgrading this ASA code is kind of out of the question at this time.
Listen: https://smarturl.it/CCRS8E47 Follow us: twitter.com/ciscochampions
Ransomware, fileless malware, and zero-day attacks continue to target organizations around the world. In response, organizations have resorted to deploying a variety of d...
This is a general information page for Cisco Threat Centric (TC-NAC) with ISE
Threat Centric Network Access Control (TC-NAC) feature enables you to create authorization policies based on the threat and vulnerability attributes received from the th...
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast today. For more information, including category details, the process, past winners and FAQs, check out: https://www.cisco.com/c/en/us/t...
Cisco Secure Endpoint (formerly AMP for Endpoints) will decommission legacy cloud servers, which results in Legacy Windows Connector Versions 3.x/4.x and Mac Connector Version 1.0.x ceasing to ...
IntroductionRequirementsWhat problem does CSDAC solve?CSDAC ComponentsConfiguration CSDAC Login Connector AdaptersCSDAC WorkflowFMC Policy Configuration with Dynamic ObjectsUse Case: Blocking IP address using dynamic object without a policy push