where connect AIP - SSM 10 MODULE INTERFACE

Similar Questions

• ASA5510 and AIP-SSM-10 module in promiscuous mode

  Hello

  I have a 5510 ASA with the AIP-SSM-10 and want to use just like an ID in promicuous mode.

  ASA 5510: ASA version 7.0 (8)

  AIP-SSM-10: IPS version 5,0000 E2

  At this point, we would like to configure a single interface of ASA to send traffic to the agreement in principle for the inspection of IDS (and continue to use our firewalls third existing). Is this possible?

  The following discussion gives to think this isn't:

  https://supportforums.Cisco.com/message/957351

  22.1.100.2/28 I have it configured on the interface Eth0/0 (outside) and 10.5.100.3/24 on the AIP - SSM management interface and switchports (Cisco 6509) have been configured by SPAN.

  Thanks for your advice in advance.

  Kind regards

  Lay

  You are right. Unfortunately, module AIP on ASA firewall does not listen on traffic SPAN. If you want that SPAN ports, then you can use the IPS (IPS 4200 series appliance) appliance that supports the SPAN traffic to inspect.

  PIX is also a firewall, not a feature of IPS, which cannot be used as an IPS device.

• Block P2P software using the ASA-AIP-SSM-20 module

  Hello

  I have a question about blocking P2P traffic on ASA AIP module. I've searched the forums and all I could find were solutions using regex, port block, MPF, but no example of implementation of AIP.

  Could someone point me in the right direction please?

  Thank you very much

  Martin

  Hello

  You can find all the associated p2p signatures in:

  http://Tools.Cisco.com/Security/Center/home.x

  A search using Signatures, p2p, all. Then, you can set the respective signatures to your needs.

  SPSP

• IPS (AIP - SSM) ASA5520 module

  My ASA is 7.2 2 & ASDM is 5.2 (2).

  Fix version 5.0.2 of v6.1.1 IPS module.

  What version of ASA/AMPS should I fully support the IPS 6.1?

  Just go through this process.

  ASDM 6.0 (3)

  ASA 8.0 (3)

• Cisco ASA 5510 + license + AIP - SSM

  Hello.

  I have this box.

  I have a few questions about it.

  (1) I'll be able to update the firmware (from 8.2 to 8.3 or greater for example) without smarnet for ASA 5510? And what can not do without smartnet?

  (2) I have only AIP-SSM-10 module this ASA 5510. is there a smartnet, too? And when I buy only one module is it build in a subscription for 1 year for the signatures of the IPS?

  (3) if I have the Cisco ASA 5510 base license, my IPS on AIP-SSM-10 will work?

  (4) as I foresee in a purchase of the year a 5510 more with the same module and mount ther of failover. I really need license Security more than failover (active / standby)? For active/active, I know I need one, Yes?

  Please help me.

  (1) you must Smartnet in order to download the software from the download from cisco.com site.

  (2) Yes, there is also a smartnet for the AIP module. Module AIP does not come with one year subscription, but you can ask for a demo license.

  (3) Yes, the basic license is OK for the AIP module.

  (4) Yes, you would need license security more on the two ASA to be able to run any type of failover on ASA5510.

  Hope that answers your questions.

• The AIP - SSM to unused ASA connection interface

  Hi people,

  Perhaps, someone has already raised this issue, but I was unable to find anything relevant. We have an ASA with an unused interface (gig0/3). The sensor of the AIP - SSM is physically connected to this interface with the following IP settings:

  Sensor (192.168.2.2/30,192.168.2.1)---interface ASA (192.168.2.1/30)

  It's basically point to point connectivity, and I can reach the ASA of the sensor and the other way around.

  This design is dictated by the lack of a free port on the switch.

  Technically, it should work without any problems, but I can't seem to be able to reach the sensor. There is a switch between my PC and the sensor and the switch has the corresponding static route added. I can reach the switch sensor.

  Is there a security feature hidden I don't know that prevent communication with the sensor.

  And ACL of the sensor allows the traffic to all networks (0.0.0.0/0)

  With the sensor acl set to 0.0.0.0/0, the sensor must be allowing connectivity.

  You can use the 'View of package' command on the sensor to look at packets on the interface command and control to see if the packets are what makes the sensor.

  You say that you have a static route on your switch for the switch reach your sensor. Do you know if your PC is configured to use the switch as the computer's default router. If the PC is to use a different default router, then the other router should also the static route.

  The other possibility is that the SAA itself can be deny traffic.

  Since this is an ASA connected to the MSS interface, the traffic must be routed through the ASA. Standard firewall rules apply to this traffic. The security level of the interfaces can prevent traffic, and an ACL may be necessary in order to allow the circulation of your PC be routed to the SSM.

  NOTE: If you don't want to have to worry about roads, the other alternative is to make the network between the ASA and SSM to be an isolated network that only 2 machines know.

  You can then use PAT static to map a port on the inside of the ASA interface with the address of the SSM 443 https port and map a second port of the SAA within the interfaces to the address of the SSM SSH port.

  How your home PC would simply plug the ASA IP using these specific ports and the ASA would do the translation of port and transmit on the MSS.

  The SSM address could also be dynamically PAT would have on the SAA within the address, so SSM could start the connection to other machines on the inside network.

  Another alternative if you have addresses available on your inside network IP is to use static NAT instead of PAT. And just go forward and has the ASA statically map an IP network on IP of the SSM on the network that only the ASA and the SSM inside could know.

  In both cases the network between the ASA and SSM would not routable at, and you wouldn't have to worry of reproducing static routes anywhere.

  SIDE NOTE: A separate network for the SSM you Becase you will also need to NAT or PAT address of the SSM for the ASA to outside interface. In this way the SSM will be able to connect to Internet to download cisco.com auto updates, and/or pull overall correlation of servers cisco information. It's probably the same configuration that you would already other internal addresses, and just to be sure, you cover the SSM since you have it on a separate subnet.

• Physical connectivity of ASA AIP - SSM

  How the physical connectivity of ASA AIP - SSM should be in the case of inline interface mode of inspection for all interfaces of the firewall. ?

  Rgds.

  Assuming that 'interface_policy' has "inline ips" in the policy, then yes your configuration is correct.

  Keep in mind that 'GigabitEthernet0/1' being assigned to vs0 is the background interface of basket of the MSS itself and should not be confused with the external interface GigabitEthernet0/1 of the SAA.

  As for using several virtual probes, it is a personal choice.

  When you use an ASA with just a single context, then usually a single virtual sensor is sufficient. It's only when you want to follow for traffic coming from firewall interfaces (or different classes of traffic) If you want to use several different virtual devices.

  However, when you use an ASA with multiple security contexts, then it is usually a good idea to go and use a virtual sensor separate from the context of the ASA.

  If you choose to use several virtual devices, you must understand that the background basket interface GigabitEthernet0/1 are only awarded to only 1 virtual sensors.

  Here is an explanation of how the other virtual sensors would get traffic:

  When packets are sent to DFS for monitoring ASA, ASA includes a special header in each packet. Special information such as the framework of the SAA whence the package, the real and NAT/PAT package addresses, and a few other things. An important field of this header is for the virtual sensor. He tells the SSM which virtual sensor must monitor this package.

  When the ASA is configured without using the names of virtual sensor, this is a virtual sensor in the package header field is blank. If the SSM sees a package with the field left blank it will check the DFS configuration to see which virtual sensor GigabitEthernet0/1 of the SSM has been assigned and that sends the packets to the virtual sensor.

  If ASA has been configured to send the packet to a specific virtual sensor (be it by adding the name of virtual sensor at the end of the "inline ips" entered configuration or by using the configuration entries "allocate ips" in the context of system configuration) then the ASA will include the virtual sensor in the header of the packet. The SSM will read in this area, and instead to send the virtual sensor where Gig0/1 is assigned, it will rather send to virtual sensor specified in the header of the packet.

  Indeed, it overrides the assignment Gig0/1 and will lead to what ever virtual sensor has been specified by the configuration of the SAA.

• silly question on module aip - ssm

  When the aip ssm module is in inline mode. fact the package first analyzed by the aip ssm module or it is first checked by the firewall rules if it is allowed and then sent to the aip ssm module.

  can someone throw some light on this.

  concerning

  Sushil

  All firewall rules are applied prior to sending the packets of the SSM.

  So if the package will be deleted by a firewall rule, the package will not be sent to the SSM.

  If the package will be changed by a firewall rule, then the change will be before being sent to the SSM.

  There are two exceptions, and this is the encryption and final release of the package.

  Encryption occurs after they are sent to the SSM, so SSM always sees a unencrypted traffic (where the ASA is encryption tunnel endpoint).

  And of course send the package by the SAA through external sound interfafes happens after the sending of the SSM.

  In the case of promiscuity, followed by the SSM, encryption and pass arrive just after that a copy is sent to the SSM.

  In the case of the line followed by the SSM, encryption and transmit occur only after that the SSM has completed the analysis and the package was not refused by the SSM.

• Module AIP - SSM hung

  Hello

  I recently confgured my module AIP-SSM-40 in my firewall that is configured in HA(Active/Standby). It was working fine. Then, I upgraded the version of the image to IPS, 2.0000 E3.

  It worked fine for a week. Then I found that the secondary firewall was in a State of secondary failure. My AIP - SSM in the secondary firewall fails.

  I couldn't connect the AIP - SSM with command session 1. Display the order watch module

  Model serial number of map mod
  --- -------------------------------------------- ------------------ -----------
  0 ASA 5520 Adaptive Security Appliance, ASA5520

  1. ASA 5500 Series Security Services Module-40 ASA-SSM-40

  MAC mod Fw Sw Version Version Version Hw address range
  --- --------------------------------- ------------ ------------ ---------------
  0 0021.a09a.d1bb for 0021.a09a.d1bf 2.0 1.0 (11) 5 8.0 (4)
  1 0023.5e15.f6c8 to 0023.5e15.f6c8 1.0 1.0 (14) 5

  The Application name of the SSM status Version of the Application of SSM mod
  --- ------------------------------ ---------------- --------------------------

  Data on the State of mod aircraft compatibility status
  --- ------------------ --------------------- -------------
  0 to Sys does not apply
  1 does not not Applicable

  at the end of the failover see command shows

  Slot 1: ASA-SSM-40 rev hw/sw (1.0 /) status (does not/high)

  I suspect module SSM is having the problem. Is it possible to recover.

  Try to stop and reset the module using this command from the ASA:

  HW-module module 1 reset

• Question on the CSC - ssm modules and aip - ssm in the ASA5500

  Is it true that the CSC - ssm and aip - ssm modules cannot coexist in the device of ASA5500 at the same time?

  Another issue is the site of cisco using the command keyword intra-interface involving NO IPSEC TRAFFIC, there are example of config/example

  It is true that the CSC - ssm and aip - ssm modules cannot coexist in the device of ASA5500 at the same time.

  It is not a sample configuration partitions on the spot yet. However, outside the control of the same security, you must the ordinary rule of translation to pass traffic. Also, because of the dynamic nature, it allows only one-way traffic. For example:

  NAT (inside) 10 192.168.1.0 255.255.255.0

  Global interface (10 Interior)

  Global (ouotside) 10 interface (is not required however)

  Sincerely,

  ~ AJ

• Interface of the AIP - SSM

  What is the configuration of the AIP - SSM interface indicates?

  If this indicates that trafficking of this interface will be done, then what is the purpose to divert the traffic of asa good political order.

  Thanks, hope that I have answered your questions.

• New deployment with the ASA and AIP - SSM module

  Hi guys and girls,

  I think to deploy an ASA with IPS module AIP - SSM to my perimeter. I'm going to use / * Style Definitions * / table. MsoNormalTable {mso-style-name : « Table Normal » ; mso-tstyle-rowband-taille : 0 ; mso-tstyle-colband-taille : 0 ; mso-style-noshow:yes ; mso-style-priorité : 99 ; mso-style-qformat:yes ; mso-style-parent : » « ;" mso-rembourrage-alt : 0 à 5.4pt 0 à 5.4pt ; mso-para-margin : 0 ; mso-para-marge-bottom : .0001pt ; mso-pagination : widow-orphelin ; police-taille : 11.0pt ; famille de police : « Calibri », « sans-serif » ; mso-ascii-font-family : Calibri ; mso-ascii-theme-font : minor-latin ; mso-fareast-font-family : « Times New Roman » ; mso-fareast-theme-font : minor-fareast ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ; mso-bidi-font-family : « Times New Roman » ; mso-bidi-theme-font : minor-bidi ;} Cisco IPS Manager Express (IME) to monitor the IP addresses to monitor the ASA. I have no plans on deploying a device IDS.

  Question: The IME is designed to send notices to the subject of threats? What are some of the configurations in your network? (Just prick with the last question.)

  THX...

  IME is designed only for IPS monitor (whether it be IPS appliance, module AIP - SSM on ASA or other module IPS). IME is not able on the control of ASA.

  EMI can provide advice by email about events which are fires on the IPS, while the IPS itself cannot. EMI may also keep all the events triggered by the IPS, while SPI buffer is small enough, that so if you have huge demonstrations, the buffer gets replaced pretty quickly.

  Here is more information about IME, if you are interested:

  http://www.Cisco.com/en/us/products/ps9610/index.html

• Licensing Module AIP SSM issue

  Hello

  If I put 2 AIP SSM Modeules in to a Cisco ASA 2 which are grouped, need me a new license for the firewall?  In the ASDM she complains without a valid license installed even if the firewall collects the cards and allows me to configure in CLI.

  Help please

  Yes, you do.

  AIP SSM module is independent of the SAA. Each AIP SSM module would need their own license as it relates to the AIP SSM module number.

• Do I need two AIP - SSM modules if I'm failover configuration?

  Is it possible to use a single module AIP - SSM in two ASA that is configured in active / standby?

  I would like to configure the module in the first ASA with the relief setting.  Then, if the ASA first fails, I could physically remove the module AIP - SSM and place it in the second ASA.

  Would there be problems, configure it in this way?

  Would be the active / standby ASA complaining that there is that one module AIP - SSM?

  Thanks in advance.

  Hello

  You must have an AIP - SSM on two SAA in order to be able to run the failover, without it failover will not come to the top (because of incompatibility of hardware)

  Kind regards

  Julio

• AIP SSM-10

  Hi EXP.

  1st time for me to work with AIP-SSM-10, I ASA5510 and AIP-SSM-10,.

  Firewall (5510):

  inside the 192.168.55.252

  87.191.101.1 outside

  DMZ 172.16.0.1

  where to plug the AIP SSM-10 what ip address I have to give him and how can I be savvy to ensure that is to have such as ping or traceroute ip connectivity. what I'm missing, it is the ip address.

  I gave an ip address to the management interface and I left ping but I couldn't ping the AIP SSM-10 between the firewall.

  Please help,

  (1) of the SAA, you would session in the module, and you must configure the ip address on this module with the command "setup."

  (2) what you just set up the ip address is assigned to the interface on this module.

  (3) this interface on the module must be physically connected to your network. You can configure a unique ip address in the same subnet as your ASA inside the interface.

  Here's a diagram of the module with the port interface / hardware:

  http://www.Cisco.com/en/us/docs/security/IPS/7.0/installation/guide/hw_installing_ssm.html

  Here's how to run the command "setup":

  http://www.Cisco.com/en/us/docs/security/IPS/7.0/installation/guide/hw_initializing.html