The configuration that you are using for the RE needs to come from the device.
I mean, do not directly upload the XML configuration into a project, but attach a device into the project and use the device as the source for importing the configuration.
This may be the reason that provoked that you would get no results.
QUESTION: Why can't I bring the XML manually into the project via the Palo Alto Networks import field?
ANSWER: When doing Rule Enrichment or Machine Learning processes, we will have to go into the information we learnt from logs. We do need a way to map the security rules to logs that the firewall has generated. We do have a map between logs and devices, as the logs provide the serial number of the device, and we do need to have a mapping between the device and the configuration. This mapping is done by importing the configuration from the device itself.
QUESTION: Does this mean that we need to have connectivity to the firewall to download the config?
ANSWER: Until version 1.1.12, the answer was YES. In 1.1.12 we have provided a functionality to upload the XML config into the device (I refer to the device within Expedition), so you won't need to provide API Keys to do HTTPS connections to the FW and retrieve the XML config.
Device imported. Running configuration imported.
All Policies are there. All Policies are tagged for ML and RE (Monitor>All Rules). But trying to use ML or RE (Analyze Data) gives the same error: "No rules selected for learning".
What I want to do is - grab seen Source and Destination addresses and Apps in the Traffic logs.
App ID Adoption > Retrieve Apps (Fast or Slow) is working - so Log Collector Plugin is functioning.
What mystery is this?
v. 1.1.23. All internal checks pass.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!