Source: https://joinfinn.com/integrations/palo-alto-networks-pan-os

# Palo Alto Networks PAN-OS

## Palo Alto Networks PAN-OS + Finn.

Palo Alto Networks PAN-OS integration with Finn. PAN-OS runs Palo Alto Networks firewalls and exposes network security configuration and system information.

Business function: IT and identity.

## What you can do with Palo Alto Networks PAN-OS.

PAN-OS runs Palo Alto Networks firewalls and exposes network security configuration and system information.

### Fulfill a firewall connectivity request

Finn carries an accepted application connectivity request through the firewall change and verifies the requested connection.

**Typically handled by:** Network security administrator

**Starts when:** An application owner requests a specific connection through the firewall.

#### What Finn handles

1. Read the source, destination, application, purpose, and required duration from the ServiceNow request.
2. Inspect the existing PAN-OS configuration and obtain the network security owner's decision on the precise rule change.
3. Apply the accepted candidate change, validate it, and commit it during the accepted change window.
4. Read the commit result and connection evidence, then complete the request with the rule and verification details.

**The result:** The accepted connection is available and its firewall change has a documented decision and result.

### Apply a confirmed incident containment change

Finn carries out the security team's selected firewall block and records whether the targeted traffic is contained.

**Typically handled by:** Network incident responder

**Starts when:** The security team confirms a threat and accepts a specific network containment action.

#### What Finn handles

1. Read the incident evidence and the exact address, application, or traffic scope selected for containment.
2. Inspect the current firewall policy and record the security owner's containment decision.
3. Apply and commit the accepted rule or object change, then read the completed job result.
4. Inspect the resulting traffic evidence and update the connected incident record with the action and observed effect.

**The result:** The incident records the completed firewall containment and its observed traffic result.

### Update firewall objects after a service move

Finn updates the accepted network addresses for a moved service and verifies that the intended connections still work.

**Typically handled by:** Network change engineer

**Starts when:** Infrastructure records an accepted server or service address change.

#### What Finn handles

1. Read the old and new service addresses and the owning change record.
2. Locate the PAN-OS address objects and policy references affected by the move.
3. Get the network owner's change approval, update the selected objects, and complete the configuration commit.
4. Check the service's connection evidence and attach the results to the infrastructure change record.

**The result:** The firewall reflects the accepted service move and the dependent connectivity has been checked.

### Retire temporary firewall access

Finn follows an expiring access request through its owner decision and completes the selected policy cleanup.

**Typically handled by:** Firewall policy administrator

**Starts when:** A temporary firewall rule reaches its recorded review or expiry date.

#### What Finn handles

1. Read the original request, rule scope, expiry date, and available usage evidence.
2. Ask the application and security owners whether the access should end or receive an accepted extension.
3. Remove or update the selected rule according to that decision and complete the configuration commit.
4. Inspect the final rule state and update the access request with the decision, commit result, and any required follow-up.

**The result:** Temporary access has an explicit disposition and the firewall policy matches the owner's decision.

### Replace an expiring firewall certificate

Finn coordinates the accepted certificate replacement and completes its installation and verification on the firewall.

**Typically handled by:** Network certificate administrator

**Starts when:** A firewall certificate approaches the organization's replacement date.

#### What Finn handles

1. Read the certificate's purpose, affected service, expiry, and replacement requirements.
2. Obtain the replacement through the organization's certificate owner and get the service change approval.
3. Import the accepted certificate, update the intended certificate reference, and commit the configuration change.
4. Check the affected service's certificate and connection result, then finish the change record without copying private keys into it.

**The result:** The affected service uses the accepted replacement certificate and the change records its verified result.

### Complete a firewall configuration record

Finn collects the requested firewall configuration and operational context and files the finished record for the authorized operations team.

**Typically handled by:** Network operations documentation specialist

**Starts when:** A change review or operations handover requires a current configuration record.

#### What Finn handles

1. Read the requested firewall scope, document audience, and the change or handover purpose.
2. Retrieve the current PAN-OS configuration and the specific operational details needed for that purpose.
3. Write the configuration summary and store the requested export in the team's restricted document location.
4. Attach the record to connected ServiceNow and send the authorized owners its location and collection time.

**The result:** The operations team has a current configuration record linked to the change or handover it supports.

### Finish post-change network verification

Finn performs the accepted checks after a firewall change and closes the change record with the network's observed result.

**Typically handled by:** Network change coordinator

**Starts when:** A firewall change's commit has completed.

#### What Finn handles

1. Read the accepted change scope, expected connections, and verification steps.
2. Check the commit job result, active configuration, and traffic evidence for the changed scope.
3. Run the designated application connectivity checks through the connected test system and compare the results with the acceptance criteria.
4. Complete the ServiceNow change when the criteria pass, or execute the owner's accepted rollback procedure and record its outcome.

**The result:** The change has a verified completion or rollback result backed by configuration and connection evidence.

## Connection setup

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Palo Alto Networks PAN-OS.

## Explore Finn

- [Agents](https://joinfinn.com/agents): Help customers. Work with your team. Finish the job.
- [Systems](https://joinfinn.com/systems): Business apps for the work behind the conversation.
- [AI Gateway](https://joinfinn.com/ai-gateway): Control connected AI apps, models, access, and spending.

[All integrations](https://joinfinn.com/integrations)

[Discuss this integration](https://joinfinn.com/contact)

[Discuss your workflow](https://joinfinn.com/contact) · [How it works](https://joinfinn.com/demo/app/#/w/borough/overview) · [Get started](https://joinfinn.com/app/#/signup)