Login
- Table of Contents
-
- 03-Policies
- 01-Security policy
- 02-Attack defense
- 03-Connection limit
- 04-uRPF
- 05-NAT
- 06-AFT
- 07-Application audit
- 08-Bandwidth management
- 09-Load balancing common configuration
- 10-Server load balancing
- 11-Outbound link load balancing
- 12-Inbound link load balancing
- 13-Transparent DNS proxy
- 14-Application proxy
- 15-NetShare control
- 16-Security policy hit analysis
- 17-Security policy redundancy analysis
- 18-Global load balancing
- 19-IP reputation
- 20-NAT66
- 21-Server connection detection
- 22-Security policy optimization
- 23-Server load balancing
- 24-Load balancing common configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 16-Security policy hit analysis | 22.51 KB |
Security policy hit analysis
This help contains the following topics:
Introduction
The Policy Hit Analysis page displays security policies that have not matched any packets in the policy creation order. Policies created first come first in the list.
A security policy is not hit if either of the following conditions exists:
· No packets match the filtering criteria specified for the policy.
· The policy is redundant because another security policy with less strict filtering criteria were created earlier than the policy.
Restrictions and guidelines
Match counting or statistics collection must be enabled for security policies for the system to perform policy hit analysis.
Perform policy hit analysis
1. Click Policies > Security Policies > Policy Hit Analysis.
2. View, modify, or delete security policies that have not matched any packets.
Table 1 Policy hit analysis configuration items
|
Item |
Description |
|
Time range |
Select a time range for the analysis from the menu at the top right corner. Options include: · Today. · Last 3 days. · Last 7 days. · Last 30 days. · Last 3 months. · Last 6 months. · Last 12 months. · Last 3 years. |
|
Edit |
To modify a security policy, click the Edit icon for the policy. |
|
Delete |
To delete a security policy, select the policy and then click Delete. |
3. After policy modification or deletion, click Activate to have the security policy configurations take effect immediately.
