(ASA) AIP - SSM 10 Inline; Supreme events?

A 5520 ASA with SSM-10 GOAL is set to inline mode, but the events of the show for 2 hours (sensor > HS event past 02:00) of the Interior of the sensor shows and "promicuous mode", "left promicuous mode'."

This AIP SSM - 10 has only one gig0/0 and gig0/1 where o/o is taken out of service and a value default virtual sensor (vs0) is assigned to gig0/1. I see the statistics (sensor > sh SEO-engine of analysis) to gig0/1 so I collect statistics.

If the configuration of the ASA 5520 has the following policy of inline and events log shows that enter and exit in promiscuous mode so how do I check if I am inspection/recovery in inline mode?

(ASA > sh run access-list IPS)

IPS list extended access permitted ip DMZ 255.255.255.0 26.26.1.0 255.255.255.0

(ASA > sh run | b class-map)

class-map IPS

corresponds to the IP access list

class-map inspection_default

match default-inspection-traffic

!

!

type of policy-card inspect dns preset_dns_map

parameters

message-length maximum 512

Policy-map global_policy

class inspection_default

inspect the preset_dns_map dns

inspect the ftp

inspect h323 h225

inspect the h323 ras

inspect the netbios

inspect the rsh

inspect the rtsp

inspect the skinny

inspect esmtp

inspect sqlnet

inspect sunrpc

inspect the tftp

inspect the sip

inspect xdmcp

inspect the waas

inspect the icmp

class IPS

IPS inline help

!

global service-policy global_policy

(sensor > sh interfaces)

...

Statistics interface GigabitEthernet0/1 MAC

Function of interface = interface detection

Description =

Support type = backplane

By default Vlan = 0

Inline = unpaired mode

Pair of status = n/a

Circumvention of Capable hardware = no.

Twin derivation material = n/a

Link status = upwards

Link speed = Auto_1000

Link Duplex = Auto_Full

Lack of Packet percentage = 0

Total packets received = 95044

Total number of bytes received = 8715230

Total multicast packets received = 0

Total of broadcast packets received = 0

Total fat packets received = 0

Total sousdimensionnés packets received = 0

Receive the total errors = 0

Receive FIFO overruns total = 0

Total packets transmitted = 95044

Total number of bytes sent = 9047702

Total multicast packets sent = 0

Total broadcast packets sent = 0

Total fat transmitted packets = 0

Total packets transmitted sousdimensionnés = 0

Total transmit errors = 0

Total transmit FIFO overruns = 0

sensor > sh events last 02:00

evStatus: eventId = 1203360411830836145 = Cisco vendor

Author:

login host: ASA2_IPS

appName: kernel

appInstanceId:

time: 2008-02-20 19:01:46 2008/02/20 19:01:46 UTC

syslogMessage:

Description: device ge0_1 entered promiscuous mode

evStatus: eventId = 1203360411830836146 = Cisco vendor

Author:

login host: ASA2_IPS

appName: kernel

appInstanceId:

time: 2008-02-20 19:01:53 2008/02/20 19:01:53 UTC

syslogMessage:

Description: the promiscuous mode device ge0_1 left

The left State events and entered promiscuous mode are usually generated when you do a 'package of display' or 'the capture of packets' command on the CLI of the sensor.

Track order of the package is promiscuity but is independent of promiscuity or inline followed by analysis of the probe engine.

If you have inline monitoring using the probe analysis engine.

And still make command package to the cli for your own monitoring promiscuity of those same packets. Here are 2 independent monitors of the same packages.

If I remember right inline monitored packets always get returned to the ASA (unless expressly denied), which is not promiscuous packets. So check sensors gig0/1 interface statistics and the number of packets for transmission. If receive and transmit accounts are quite close, then packets are monitored by the analytical engine InLine. If the number of transmission is nil or very low then the packets are likely promiscuous monitored.

With the configuration of your ASA you are correctly configured for online tracking.

So I don't think that you are investigating inline, and status messages are specific to your start and stop of the command 'package' on the CLI for your own independent viewing packages promiscuity.

Tags: Cisco Security

Similar Questions

  • 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.

  • The ACE IPS Cisco and Cisco ASA AIP - SSM (IPS)

    Is there a difference between the features offered by the Cisco ACE IPS and Cisco ASA AIP - SSM (IPS) devices?

    Can we do without Cisco ASA AIP - SSM (IPS) of 'only' configuration/implementation Cisco ACE IPS.

    Cisco AVS/ACE emphasis on commissioning and to secure web-based applications. IP addresses do not focus on just the web applications and trying to get the multiple layers of the OSI stack. Consider the IPS as a general practitioner and the ACE/AVS as an eye surgeon, or something :)

    Here is the response from Cisco itself:

    http://www.Cisco.com/en/us/prod/collateral/modules/ps2706/ps6906/prod_qas0900aecd8045867c_ps6492_Products_Q_and_A_Item.html

    Q: how is Cisco AVS Firewall application differs from an intrusion prevention system (IPS)?

    A. IPSs are solid solutions of protection against targeted attacks of known vulnerabilities in major platforms such as Windows, Solaris, Apache or Microsoft Internet Information Services (IIS). Cisco AVS excels to protect against targeted attacks Web sites or enterprise applications. These applications can be built custom internal applications or software vendor. Signatures and security patches are generally not available for these types of applications, and building these security levels in each application, it would be almost impossible.

    Q: how is Cisco AVS Firewall application differs by a network firewall?

    A. The Cisco AVS 3120 and Firewall network such as the Firewall of Cisco PIX® and Cisco ASA 5500 Series Adaptive Security appliances are complementary products. The application Cisco AVS Firewall secures Web applications; excellent network in the network security firewall. and the Cisco AVS provides defense in depth for Web applications.

    Firewall network apply policy networks, IP addresses and ports; they have a wide range of application for many different protocols layer features. The firewall can and will be deployed in many locations, including the edge, edge of the enterprise network, branch, etc. Cisco AVS imposed the policy on data HTTP as URL, headers and parameters. Cisco AVS is deployed in the data center in front of Web applications

    Concerning

    Farrukh

  • do not get traffic of ASA AIP-SSM-20.

    Hello

    We have Cisco ASA 5510, and we recently added Cisco AIP - SSM. We have configured the sensor and did as well as ASA also but we don't get newspapers in ADM please help me on this.

    Please find attached Sersor Configuration and version of the IPS and ASA module.

    Kind regards

    Nathalie. M

    On the SAA, you need

    access-list aip-acl extended deny ip any any
    class-map aip-class
    match access-list aip-acl
    policy-map global_policy
    class aip-class
      ips inline fail-open
    service-policy global_policy global

    so that it sends traffic to the agreement in principle for inspection.

    I hope it helps.

    PK

  • Replication of configuration ASA AIP - SSM

    People,

    The AIP - SSM replicates another AIP - SSM ASA/standby configuration?

    I mean, when I change the configuration on the AIP/SSM assets, will change bring replicated to the other AIP - SSM?

    Thank you

    Yes, unfortunately all the IP addresses are the same. Configuration duplicate automatically 1 unit to another.

    Please kindly marks the message as answered if you have any other question. Thank you...

  • Rules of politics on the ASA AIP - SSM services

    Salvation of the forumers

    I have an ASA with AIP - SSM. I want to protect the LAN private outside the internet attack.

    I would check the meaning of the ACL on ASDM firewall > policy of Service rule

    1. am I right to set the source: external interface, destination: 172.16.0.2

    or 2. destination value: 10.10.0.0 / 16

    Thank you

    Noel

    To respond to your request in simple just do your Service policy with the IP address that is seen by the firewall. If the IP address 10.10.0.0/16 are natted on the router with 172.16.0.2, then all IP addresses, hit on the firewall will be 172.16.0.2 so make your destination with 172.16.0.2 else if the natting is on the firewall for 10.10.0.0/16 then point the destination to 10.10.0.0/16.

  • 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

  • ASA - AIP - SSM design review

    Hello

    If anyone can offer you please, you will enjoy

    We have 2 ASA 5520 with SSM modules in. behind ASA is a CSS load balancer. This load balancer have ssl and ssl certificate installed module. communication from the internet to the VIP loadbalancer is SSL, the SSM module configured to control communication is limited because everythng is encrypted.

    communication between the LB farm and the server is not encryted, but there is no IPS inbetween. can you suggest if someone used the design below

    int 1 (public) - ASA1 - LB 1 interface (dmz) - inside (inside) ASA1 interface where all the web server resides

    Therefore, the traffic is on port 443 to the virtual IP address. Static on ASA 1forwards traffic to its dmz interface where 1 LB, then clear the 1 LB traffic goes to the inside interface where all the serverfarm web resides. by doing so, we can configure the SSM module to monitor the traffic of LB to webserverfarm since its between 2 interfaces of ASA. and also we can have access - list on ASA to allow traffic only between LB and Web servers

    This will be a concern on the performance of the ASA?

    What is a recommended design

    Thank you

    It is a valid design and it should work.

    The ASA will see traffic twice and the interface that is in front of the LB will see traffic entering the lb twice so I'm not sure that it is effective. Please check the amount of traffic will see interfaces to see if the ASAs can manage it.

    Since the LB will be the one actually pulling pages and to talk to your servers, why did you not pass by the ASA, but external users from do not by it, when speaking of LB?

    If you are worried about BACK against LB and you do not have another firewall to use so I assume that it is valid.

    I hope it helps.

    PK

  • Cisco ASA aip - ssm signature update

    Hello

    Is it possible to dynamically update the signatures directly from Cisco IPS? I can only find configuration guides where the IPS module queries an internal server...?

    Thank you

    Ash

    Yes, you can update IPS signature directly from cisco.com if you run IPS version 6.1 and higher.

    This is the configuration for your reference doc:

    http://www.Cisco.com/en/us/docs/security/IPS/6.1/Configuration/Guide/IDM/idm_sensor_management.html#wp2182927

  • AIP - SSM in cluster

    Hello

    We have a failover cluster ASA, with 2 IPS, each in an ASA AIP - SSM. There is a way of module config mode cluster as ASA IPS, or have a configuration that is mirrored between them?

    Thank you very much.
    Better with respect to Antonello.

    Antonello;

    Configuration mirroring between the AIP-SSMs is not currently available.  You can emulate this process by copying the current configuration of the AIP - SSM active to a FTP server, change the configuration to remove the specific details of the host (IP address, etc) and then copy this configuration on the stand by AIP - SSM.

    Another option would be to invest in Cisco Security Manager (CSM) and create a shared strategy that is applied to the two AIP - SSM.

    Scott

  • Newspapers of AIP - SSM

    Hi all

    Can we get the logs generated by the IPS module. My client is underway for verification and so he wants to logs generated by the AIP - SSM. Kindly let me know how to do it.

    Thank you & best regards

    R.MADHANKUMAR

    When you say newspapers, I'll assume you're talking about the Signature events generated by your AIP - SSM.

    These events are available on the sensor in a circular buffer. You can see them in the CLI with the "alert events past hh: mm ' command, but once the buffer wraps the new events will be overwritten. Export events off the sensor is allowed only through a protocol called CETS. Only a few devices speak this Protocol. If you run a copy of the IPS Manager Express (IME, it's free for some devices) to manage your sensors, you can export HTML or CSV events in case control tab, select other > "Save as HTML or CSV.

    -Bob

  • 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

  • Updated AIP-SSM-10 on ASA 5510

    Hello

    I want to upgrade the IPS module in an ASA 5510, and I have a few questions. The AIP - SSM is running E3 479.0 1.0000 and I have a valid account of the ORC etc for this.

    1. What is the version of the software on the question of the ASA?
    2. When I look in the software downloads< ips="" there="" are="" .pkg="" and="" .img="" files.="" i="" want="" to="" upgrade="" to="" 6.3(3)e4.="" do="" i="" have="" to="" re-image="" the="" ips="">
    3. AFAIK redefinition to wipe the device so I just reload the config after, right?
    4. I guess I can apply any update after going to E4?
    5. Can you give me links for this upgrade?

    see you soon

    Let me give some clarification on a few points:

    2. There is no need to recreate the image on the device using the .img file.  You can improve the mechanism of maintenance of your existing configuration using the .pkg file.  It is the recommended method for upgrading to Cisco IPS devices/modules.  The .img file to recreate the image should only be used to restore the default device.

    5 here are links for the upgrade of the probe using a .pkg file.  For updates through the IDM user interface:

    http://www.Cisco.com/en/us/docs/security/IPS/6.2/configuration/guide/IDM/idm_sensor_management.html#wp2126670

    For upgrades via the CLI:

    http://www.Cisco.com/en/us/docs/security/IPS/6.2/configuration/guide/CLI/cli_system_images.html#wp1142504

    Another point of clarification; current releases of IPS software supported on the AIP-SSM-10 are (taking into account you are currently running 6.2 (1) E3):

    6.2 (3) E4

    7.0 (4) E4

    You can go directly to each output.

    Scott

  • 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.

  • Automatic update AIP-SSM-10 and ASA 5510 (Beginner)

    I see that it is possible to automate the updates of the ASA 5510 and AIP SSM via FTP on my own server. Is it possible to automate the download directly from Cisco.com?

    Thank you!

    Jeremy

    Jeremy, the answer to your question is correct, as far as the Cisco products are concerned. So I wrote a PERL app that does exactly that, and I published an article about it in the June 2007 issue of Sys Admin magazine. Here's the article online: http://www.samag.com/documents/s=10128/sam0706a/0706a.htm

    And it is also on my site, with a tar of scripts to:

    http://www.LHB-consulting.com/pages/apps/index.html

    Good luck.

    -Lisa

Maybe you are looking for