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.
Two things that you could check are:
- If your configuration is from a Panorama device, the log connector needs to refer to the Panorama device, selecting the desired device group and serial number that applies
- If you have imported multiple times the same configuration from a firewall (the sources will have the time-stamp in its name), you need to recreate the log connector to make sure that it is using the correct config (even they may have the same config content, their internal IDs are different). This is something that we need to improve in Expedition, so the step is not required.
Thank you. Must have been the second thing. Or somethign else, because I upgraded tool to the 1.1.27 and Imported Device/Config and recreated Project from sratch.
The error is gone, but there is another thing: after RE analysis is complete - I am presented with 0 results. The table is empty.
Is there a Time Frame limitation of logs? Mine are about two months old (using custom Time Frame in Log Collector).
Edit> nope, still no Enrichment or ML data even with fresh logs.
There is no limitation software based.
The only limitations that we could face are:
- Bugs in the ML module
. The HW fails to process all the data while placing it in memory
- There is no disk space enouigh for hosting all the data while processing
I also have the problem with "no data to display" or "no rules selected for learning" in rule enrichment. I have tried everything suggested in this thread including upgrading to the latest version of Expedition, 1.1.35.
I have rules tagged for RE. I recreated the connector, I only have one device and no panorama. No dice.
I've deleted all the different imports, unset base config and deleted it.
I re-loaded the content from the device again -> OK
Re-configured the log-connector, I'm only having one PA-220, with one VSYS
I've selected 3 rules on wich I wanted to test the rule Enrichment.
I can do an "analysis" but now it's still not showing any output.
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!