Home > Articles > Cisco Network Technology > General Networking > Cisco ASA Basic Internet Protocol Inspection

Cisco ASA Basic Internet Protocol Inspection

  • Article is provided courtesy of Cisco Press.
  • Date: Jun 27, 2013.

Article Description

In this article, Sean Wilkins covers some of the common Internet protocol inspection features that can be enabled (or are enabled by default) on the Cisco ASA.


When many people think of protocol inspection, they think of a process that reads the data of a packet and inspects it for some amount of wrongdoing. In reality, the packet inspection feature of the Adaptive Security Appliance (ASA) is typically used to help make the protocol work better. This article covers some of the common Internet protocol inspection features that can be enabled (or are enabled by default) on the ASA.

What Exactly Is Internet Protocol Inspection?

For many protocols, protocol inspection is used only as a security technique because the protocol itself only uses a single commonly known port. However, what about those protocols that do not just use common ports; these protocols can be quite interesting to work with when configuring a firewall or Network Address Translation (NAT) device. This is because many of these protocols embed these dynamic port assignments within the user data portion of the traffic or open new secondary channels altogether. In these situations, for the protocol to be able to be used as expected, some amount of packet inspection is required so that the ASA can keep track of which ports are allowed through the firewall because they are attached to a primary data channel that is permitted.

Internet protocol inspection also enables the ASA administrator to control traffic based on a number of different parameters that exist within the Internet traffic, including the information contained within the data portion of the traffic. This article, because of its limited scope, cannot covers all the various possible combinations.

DNS Inspection

DNS inspection on the ASA is enabled by default and performs a number of different functions that many people might not even recognize. When enabled, DNS inspection makes the life of the ASA administrator much easier and keeps the relationship with the DNS administrators and the internal user base much happier. Functions that it provides include the following:

  • Translates DNS record information based on the configuration of the NAT commands alias, static, and nat; this is referred to often as DNS rewrite. This translation affects only DNS A records and does not affect DNS PTR records.
  • Enforces a maximum DNS message length. (The default is 512 bytes.)
  • Enforces the domain name length of 255 bytes.

DNS inspection can also be used to control the behavior of the ASA based on a number of different traffic-matching criteria.

FTP Inspection

Like DNS inspection, FTP inspection is also enabled by default and provides a number of different functions. FTP can be a little bit interesting to work with when dealing with firewalls or NAT; this is because it can use different ports for control and data traffic and can use dynamic/well-known ports. The FTP inspection engine performs four main duties:

  • Prepares dynamic secondary data connections
  • Tracks the FTP command-response sequence
  • Generates an audit trail
  • Translates the embedded IP address

FTP inspection can also be used to control the behavior of the ASA based on a number of different traffic-matching criteria.

IP Options Inspection

The Options field within the IP header, commonly referred to as IP Options, provides some additional control of traffic. IP Options inspection is enabled by default. Although this field is typically not needed for most “normal” communications, in some situations the information is required (including for Integrated Services [IntServ]). The IP Options inspection engine enables you to check three different IP options in the packet:

  • The End of Options List (EOOL): This marks the end of the IP options list.
  • The No Operation (NOP): This is used to provide internal padding to align with the 32-bit IP header boundary.
  • The Router Alert (RTRALT): This option is used to notify transit providers to inspect the contents of the packet even when the packet is not destined for that router. This is important when implementing protocols that require complex processing along the delivery path (This includes Resource Reservation Protocol [RSVP], which is used by IntServ implementations.)

HTTP Inspection

HTTP inspection is not enabled by default, but if any HTTP traffic is passing through the ASA it can be an important addition to the configuration. The HTTP inspection engine performs the following functions:

  • Enhanced HTTP inspection
  • URL screening through N2H2 or Websense
  • Java and ActiveX filtering

The HTTP inspection engine can (like both the DNS and FTP inspection engines) control the behavior of the ASA based on different traffic-matching criteria. For the HTTP inspection engine, these criteria include conformance checks against published Request For Comments (RFC) and control based on most of the fields contained within the HTTP portion of the traffic (for example, HTTP header, body, method, URI).

ICMP Inspection

ICMP inspection is not enabled by default. Without being enabled, ICMP traffic is automatically not permitted through the ASA at all without additional security policy configuration. Permitting ICMP through the ASA via access policy is not recommended by Cisco. The ICMP inspection engine creates “sessions” out of ICMP traffic and inspects it like TCP or UDP. The ICMP inspection engine ensures that ICMP cannot be used to attack the internal network. The ICMP inspection engine also alters the way that the ASA treats ICMP error messages. These alterations include the following:

  • The mapped IP is changed to the real IP, and the IP checksum is modified (in the IP header).
  • The ICMP checksum is modified because of the changes in the ICMP packet (in the ICMP header).
  • The original packet mapped IP is changed to the real IP (in the payload).
  • The original packet mapped port is changed to the real port (in the payload).
  • The original packet IP checksum is recalculated (in the payload).


Although this is certainly not an exhaustive list of the available inspection engines on the ASA platform, it does cover some of the most commonly used ones. Other than the ones covered here, a few other inspection engines are enabled by default, including H.323 H.225 and RAS, NetBIOS Name Server over IP, RSH, SIP, SKINNY (SCCP), SMTP (ESMTP), SQL*Net, Sun RPC over UDP and TCP, and XDCMP. When configuring an ASA, it is important to understand what is enabled by default and how those things will affect the configuration and the behavior of the device. This article provided a basis for this understanding.

Cisco Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Cisco Press and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@ciscopress.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020