Need information about ASA/PIX/FWSM

[hardyB]

Somebody here with knowledge or experience in these principles have a quantity of advice or recommendation for someone who has not fingered or touched them up till now? I will be included in on a modify more than from a PIX to an ASA at one of my clients house and I would like to go into it sensation or feeling quite confident that I am not misplaced. There are many books or articles are there like it would wrap the material I require, but I am a bit tentative to drop 30-50 bucks on a volume if it is going to be totally Indian to me. Any ideas or any help related these topics?

[Big Fish]

I have some information for you related to your topic. ASA/PIX/FWSM: Packet Capturing using Example of CLI and ASDM Configuration. May you like this or you must take interest in this. This is about how to arrange and configure the Cisco 5500 Series Adaptive Security Appliance (ASA) to imprison the preferred packets using the Adaptive Security Device Manager (ASDM) or CLI. The ASDM brings superlative security management and monitoring through an instinctive, accessible Web-based management interface. The ASA is entirely operational and configured to permit the Cisco ASDM or CLI to make configuration changes. Refer to permitting HTTPS Access for ASDM or PIX/ASA 7.x: SSH on the Inside and Outside boundary. Configuration Example to let the device to be distantly configured by the ASDM or Secure Shell (SSH).

[Shen]

I heard about this and then I read this: ASA/PIX/FWSM: Handling ICMP Pings and Trace route. I think you are talking about this, m I right? So how much I know about this I must give you the full knowledge. Each Internet Control Message Protocol (ICMP) pings plus trace route on the PIX Firewall are managed in a different way based on the version of PIX and ASA code. Inbound ICMP all the way through the PIX/ASA is denied by default. Outbound ICMP is allowable, but the incoming respond is denied by default. ASA/PIX maintain ICMP redirects. ICMP redirects are not supported in ASA editions prior to 8.2(1) because these editions do not maintain asymmetric routing.

[Steve123]

I have some points about how you can originally configure an ASA SSM. While you insert an AIP or CSC SSM to an ASA framework, you necessitate arranging the ASA with a number of necessary features so you can converse with the SSM. After this, the SSM needs its own configuration or design to manage how it examines transfer and how it responds to malicious or unwanted activity. Every SSM has two communication paths:

• A backplane connection to the ASA CPU.
• A 10/100 TX RJ-45 organization Ethernet port.

All SSM configurations are completed through the management port. The SSM can be configured through ASDM or through a command-line interface (CLI), or even through the Cisco Security Manager (CSM) request. In several case, the CLI and Adaptive Security Device Manager (ASDM) interfaces passes configuration information through the SSM's management port. This is significant because administrative right of entry is reserved wholly separate from the transfer check or manage path.