PDF(657.4 KB) View with Adobe Reader on a variety of devices
ePub(694.0 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(478.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:February 5, 2020
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to compare different Network Analysis Policies (NAP) for firepower devices managed by Firepower Management Centre (FMC).
Cisco recommends that you have knowledge of these topics:
Knowledge of open-source Snort
Firepower Management Center (FMC)
Firepower Threat Defense (FTD)
The information in this document is based on these software and hardware versions:
This article is applicable to all Firepower platforms
Cisco Firepower Threat Defense (FTD) which runs software version 6.4.0
Firepower Management Center Virtual (FMC) which runs software version 6.4.0
The Snort uses pattern matching techniques to find and prevent exploits in network packets. In order to do this, the Snort engine needs network packets to be prepared in such a way that this comparison can be done. This process is done with the help of NAP and can undergo the following three stages:
A network analysis policy processes packet in phases: first the system decodes packets through the first three TCP/IP layers, then continues with normalizing, pre-processing, and detecting protocol anomalies.
Pre-processors provide two main functionality:
Traffic Normalization for further inspection
Identify protocol anomalies
Note: Some Intrusion Policy rules require certain pre-processor options in order to perform detection
To create or edit firepower NAP policies, navigate to FMCPolicies > Access Control > Intrusion, thereafter click Network Analysis Policy option in the top right corner, as shown in the image:
Verifying the default Network Analysis Policy
Check the default Network Analysis (NAP) policy applied on the Access Control Policy (ACP)
Navigate to Policies > Access Control and edit the ACP that you want to verify. Click Advanced tab and scroll down to Network Analysis and Intrusion Policies section.
The Default Network Analysis Policy associated with the ACP is Balanced Security and Connectivity, as shown in the image:
Note: Do not confuse the Balanced Security and Connectivity for Intrusion Policies and the Balanced Security and Connectivity for Network Analysis. The former one is for Snort rules while the latter is for pre-processing and decoding.
Compare Network Analysis Policy (NAP)
The NAP policies can be compared for changes done and this feature could help in identifying and troubleshooting the issues. In addition, NAP comparison reports could also be generated and exported at the same time.
Navigate to Policies > Access Control > Intrusion. Then, click Network Analysis Policy option in the top right. Under the NAP policy page you can see Compare Policies tab on the top right side, as shown in the image:
Network Analysis Policy comparison is available in two variants:
Between two different NAP policies
Between two different revisions of same NAP policy
The comparison window provides a comparative line by line comparison between two selected NAP policies and the same can be exported as a report from the comparison report tab on the top right, as shown in the image:
For comparison between two versions of the same NAP policy, the revision option can be opted to select the required revisionid, as shown in the image: