Skip to main content

Jira Change Management

This Playbook is part of the Change Management Pack.#

Supported versions

Supported Cortex XSOAR versions: 6.1.0 and later.

If you are using PAN-OS/Panorama firewall and Jira as a ticketing system, this playbook will be a perfect match for your change management for firewall process. This playbook is triggered by fetch from Jira and will help you manage and automate your change management process.


This playbook uses the following sub-playbooks, integrations, and scripts.


  • PAN-OS create or edit policy
  • Panorama Query Logs


This playbook does not use any integrations.




  • jira-issue-upload-file
  • panorama-create-rule
  • setIncident
  • closeInvestigation
  • jira-edit-issue
  • jira-issue-add-comment

Playbook Inputs#

NameDescriptionDefault ValueRequired
TicketSummaryProvide a summary for your firewall request.incident.detailsOptional
SecurityTeamEmailThe email of the security team that approves the firewall requests.Optional
log_typeLog type to query. Can be: traffic, threat, wildfire, url or data-filtering.trafficOptional
queryThe query string by which to match criteria for the logs. This is similar to the query provided in the web interface under the Monitor tab when viewing the logs.Optional
addr-srcSource address.incident.sourceipsOptional
addr-dstDestination address.incident.destinationipsOptional
port-dstDestination port.incident.dstportsOptional
TestConfigurationsBy providing YES to this input, the requested firewall rule will be tested in your test environment.NoOptional
zone-srcFirewall source zone.incident.sourcenetworksOptional
zone-dstFirewall destination zone.incident.destinationnetworksOptional
TestInstanceThe instance name of the firewall in the DEV environment for testing the new rule.Optional
ActionThe action for the change requestincident.policyactionsOptional
ProtocolThe IP protocol.incident.protocolOptional
Log_forwardingLog forwarding profile.Optional
Profile_settingA profile setting group.Optional
ServiceA comma-separated list of service object names for the rule.incident.protocolnamesOptional
ApplicationA comma-separated list of application object names for the rule to create.Optional
RulenameName of the rule to create.Optional
DescriptionSet the description of the ticket.incident.descriptionOptional
Time-generatedThe time the log was generated from the timestamp and prior to it. For example: "2019/08/11 01:10:44".Optional
Rule_positionPre rule or Post rule (Panorama instances).
Possible options:
- post-rulebase
- pre-rulebase
Closing_status_rejectedThe closing status in Jira is changing in the project templates. Please provide the relevant closing status if the issue was rejected.Optional
Closing_status_approvedThe closing status in Jira is changing in the project templates. Please provide the relevant closing status if the issue was approved.Optional
TargetTarget number of the firewall. Use only for a Panorama instance.Optional
VsysTarget vsys of the firewall. Use only for a Panorama instance.Optional
LimitMax number of API requests that the
PanoramaSecurityPolicyMatchWrapper script will send.
The default is 500.

Playbook Outputs#

There are no outputs for this playbook.

Playbook Image#

Jira Change Management