Log forwarding profile in all security policies

[Javith_Ali]

Is there any other way to configure Log forwarding profile in all 300+ security policies in single shot.

currently there is no log forwarding profile in all 300+ policies.

So below method is not applicable:

Not through web interface but you can export config out.

It is one single xml file.

Device > Setup > Operations > Export configuration version

Pick latest one from dropdown and click ok.

Then open this xml in your favourite text editor.

Find area between:

<rule base>

<security>

<rules>

and

</rules>

</security>

 Everywhere you see "</entry>" and log-setting config does not precede:

Then replace this with:

<log-setting>Log-Forwarding-Policy</log-setting>

</entry>

[BPry]

@Javith_Ali,

Is there a specific reason why you can't export the XML and modify it manually? That would be a fairly logical conclussion for what you are looking to do, and would honestly take the least amount of time. This is something you could script, but you would need to collect all of the security policy names to actually write that script. 

[vsys_remo · Accepted solution]

Other possibilities:

• Script that first gets all existing rules and you then set the log forwarding profile with a foreach-loop in all existing rules
• Issue the cli command "set cli config-output-format set", go into config mode, show the security rulebase and include match statement like source zone. This will show you a list with your rules which you can copy to a text editor to replace all source zone parts with "log-setting LOGFORWADRINGPROFILENAME". And finally paste all these commands into the cli and commit

@Javith_Ali it's now up to you which way to go...

[Raido_Rattameister]

This link might give you some hints.

In your case you need to get list of rules like @vsys_remo menioned and go from there.

https://live.paloaltonetworks.com/t5/General-Topics/Changing-Profiles-assigned-to-security-Rule/m-p/...

[SteveKrall]

Another option would be to dump config in "set format" to see the actual cli command. I suggest adding the log forward option to at least 1 policy so you have a reference cli command. Then you can sve this as a csv file. Then sort the relevant data and delete everything else. Then add the missing syntax. Then convert the csv back to text and paste as cli. But PAN script mode gets flaky if you paste more than 50 lines at a time. I wish they would fix that. This is why they like to merge portions of the xml file because script mode is unreliable for large pastes.

[cramman]

Haven't seen this answer yet so needed to reply..

Migration Tool!!!    (or Expedition as it's called now) 

This is one of the best things about the tool - batch rule changes.

Setting Security Profiles on all rules, Log Forwarding, etc

Connect the FW (or Panorama) to the Migration Tool, ingest policies, multi-rule edit, then API push the rules back to Firewall.

Validate policies.

Commit!

c

[p768]

the pan-c tool will also allow you to do this.

https://github.com/cpainchaud/pan-configurator

Use the rules-edit function to update all your rules with the new log profile.

[CHammock]

FYI, if you name the profile "default" all new security rules will apply the profile automatically.  Same goes for security profile groups

[ian_johnston]

For big pastes to CLI, use a terminal emmulator, like Secure CRT, that allows you to add a 'pause' between lines. I've used a pause of 50ms to paste several hundred lines at a time.