Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 48
  • Last Modified:

ASA 5510 CSC-SSM 10 Module

i have one cisco ASA 5510 firewall with CSC-SSM 10 Module, which i use for filtering, its working good, i am sending all the the traffic to CSC-SSM module for scanning,  i do not want to send some destination traffic to CSC-SSM 10 module for scanning, those destinations are two ip addresses, if traffic is going to these two ip addresses, i do not want ASA to send that traffic to CSC-SSM module.
0
Ajeet Kumar
Asked:
Ajeet Kumar
  • 2
1 Solution
 
Ken BooneNetwork ConsultantCommented:
So in your config you should have something like this:

access-list IPS permit ip any any

class-map my_ips_class
 match access-list IPS
 class-map all_traffic
  match access-list all_traffic
 class-map inspection_default
  match default-inspection-traffic
 !
 !
 policy-map my-ids-policy
  class my-ips-class
   ips promiscuous fail-close
 !
 service-policy my-ids-policy global


BTW.. this sample was taken from : http://www.cisco.com/c/en/us/td/docs/security/ips/6-0/configuration/guide/cli/cliguide/cliSSM.html#wp1030972

So what you need to do is change your IPS access-list.
Instead of  just this:

access-list IPS permit ip any any

do this
access-list IPS deny ip any host x.x.x.x
access-list IPS deny ip host x.x.xx any
access-list IPS deny ip any host y.y.y.y
access-list IPS deny ip host y.y.y.y any
access-list IPS permit ip any any

x.x.x.x and y.y.y.y are the two destination or sources you do not want to scan.  Make sure the ACL is in that order with the permit ip any any at the bottom.
0
 
Ken BooneNetwork ConsultantCommented:
I provided a valid solution in my comments.  I gave an example with detailed instructions.
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now