Hi @Anon1 Depending on the amount of rules you have it might be worth to spend some time with learning - learning about the XML API and XPATH. If you're alrrady familiar with these topics: Great, then this should be easy for you. Some basics you can find here: https://live.paloaltonetworks.com/t5/Community-Blog/Export-the-security-rulebase-using-XML-API/ba-p/207981 The most important API request in this case for you is: https://{FIREWALL-IP}/api/?type=config&action=show&key={APIKEY}&xpath={XPATH} With XPATH you should be able to get only the rules without a log forwarding profile configured. This XPATH will show you all the existing rules: /config/devices/entry/vsys/entry/rulebase/security If you now add a NOT statement to this XPATH to exclude all the rule with a log forwarding profile: [not(rules/entry/log-setting)] Combined this will give you this API request: https://{FIREWALL-IP}/api/?type=config&action=show&key={APIKEY}&xpath=/config/devices/entry/vsys/entry/rulebase/security[not(rules/entry/log-setting)] With this final request, I am actually not 100% sure if this really works but you can test this easily (copy&paste - done). @reaper: Do you know if the XML API has FULL support for XPATH queries? If this does not work, you need to do it in two steps with the help of a scripting language, where you first do the rulebase query and then to the additional XPATH query to reduce the output to the rules without log-forwarding profile. (If it does not work and you're interested in this solution I can post a short example with powershell). Regards, Remo
... View more