Firewall Rule Activity
This report provides a six month view of firewall rule usage to help identify unneeded, outdated, or incorrect rules. This report ensures that all rules allow only authorized services and ports that match business justifications. Compliance managers might run this report more frequently to avoid unnecessary risks and avoid opening potential security holes.
Relevant data sources
Relevant data resources include firewalls that produce rule ID information.
How to configure this report
- Index the firewall activity data that includes a rule ID in Splunk platform.
- Map the data to the following Common Information Model fields:
action, dvc, rule, transport, src, dest. CIM-compliant add-ons for these data sources perform this step for you.
- Tag the data with "
network" and "
CIM-compliant add-ons for these data sources perform this step for you.
The data in the Firewall Rule Activity report is populated by the
Network - Communication Rule Tracker - Lookup Gen, a lookup that runs against the
communication_rule_tracker CSV file. This file is created by the
Network - Communication Rule Tracker - Lookup Gen lookup. Review the lookup generating search to learn more about the search schedule and time range.
Useful searches for troubleshooting
|Verify that...||Search/Action||Expected Result|
|Firewall data has been indexed in Splunk platform.||tag=network tag=communicate
|Returns data from your network device(s).|
|The data fields are normalized to the CIM.||`communicate` | table _time,host,sourcetype,action,dvc,
|Each field contains the correct, expected data.|
|The communication rule tracker is populated.||| inputlookup append=t communication_rule_tracker
or | `communication_rule_tracker`
|Returns data in communication_rule_tracker.|
The communication rule tracker file is located at
Reports in the Splunk App for PCI Compliance
Network Traffic Activity
This documentation applies to the following versions of Splunk® App for PCI Compliance: 5.0.1, 5.0.2, 5.1.0
Feedback submitted, thanks!