Suite of skillets and playbooks to simplify configuration of Cortex Data Lake (CDL).
Summary information is provided below with more details capture in each skillet directory.
Skillets can be played using panHandler by importing this repository. The Ansible playbook can be played natively in Ansible, by using the python script, or in panHandler.
The following are required to activate and configure CDL for a PAN-OS NGFW:
- minimum software version 9.0.6
- activated logging-service subscription
- generate and copy onboarding preshared key via the Hub
- have the region associated to CDL in the app at the Hub
The global configuration playbook and skillets create a baseline with a working implementation of CDL. The validation skillets can be used to validate the NGFW system status.
Additonal configuration is then required to create CDL/EAL enabled log forwarding profiles or update existing log forwarding profiles. The last step is to ensure these profiles are being used within security policies to capture and forwarding logs such as traffic and threat.
Output set commands to screen to copy-paste into the CLI.
A combination of operation and configure commands to update licenses, fetch the CDL service certicate, enable CDL with enhanced application logging, and configure CDL logging for configuration and system logs.
This playbook is designed to enable CDL with Enhanced Application Logging and configure system and configuration log forwarding. Once the playbook completes, the NGFW will have CDL globally enabled.
This skillet uses the NGFW API to quickly configure CDL with EAL with the NGFW after the CDL service has been activated.
The Ansible playbook references this skillet as part of the configuration process for XML elements not currently supported in the panos collection.
Allows the user to enter a profile name and update existing log type rules with CDL while also enabling and adding log entries for EAL logs.
The code and templates in the repo are released under an as-is, best effort, support policy. These scripts should be seen as community supported and Palo Alto Networks will contribute our expertise as and when possible. We do not provide technical support or help in using or troubleshooting the components of the project through our normal support options such as Palo Alto Networks support teams, or ASC (Authorized Support Centers) partners and backline support options. The underlying product used (the VM-Series firewall) by the scripts or templates are still supported, but the support is only for the product functionality and not for help in deploying or using the template or script itself. Unless explicitly tagged, all projects or work posted in our GitHub repository (at https://github.com/PaloAltoNetworks) or sites other than our official Downloads page on https://support.paloaltonetworks.com are provided under the best effort policy.