Palo Alto Expedition in 2026: End of Support and Safe Migration

Palo Alto Networks ended support for Expedition in January 2025. This guide covers how to contain the migration tool, verify converted rules and cut over safely before year-end.

By the Total 360 Security team7 min read
Network engineer's desk at dusk with a laptop and a printed Palo Alto Expedition firewall rule export

Expedition is Palo Alto Networks’ migration tool for converting firewall configurations to PAN-OS. Palo Alto Networks stopped supporting it in January 2025, across both its Expedition1 and Expedition2 branches. Treat it as a one-time firewall configuration conversion helper, not the foundation of an ongoing security program. If you still use it, isolate the migration host, verify every converted rule, and retire the utility when the project closes.

For a year-end migration, the deadline is your approved change window. Unexplained Any-Any rules need evidence and an accountable owner before they can be narrowed. A successful import does not prove that the new policy will support your business.

What Out of Support Means for This Migration

Palo Alto Networks’ developer documentation says support ended in January 2025 and that core functionality is moving into new products. That notice does not establish which replacement fits your environment. Confirm the current migration path with the vendor before committing to a tool.

Expedition 2.0 also does not support migrating an Expedition 1 instance into it. Moving to that branch is not a supported upgrade path for an existing deployment. If you retain Expedition for a conversion project, document the controls and the date you will remove it.

Start This Month by Locking Down the Migration Machine

Secure the tool before loading firewall configurations. CVE-2024-5910, patched in July 2024, allowed unauthorized administrator credential resets on vulnerable Expedition servers. Chained with the command-injection flaw CVE-2024-9464, it could allow unauthenticated command execution. CISA lists CVE-2024-5910 in its Known Exploited Vulnerabilities catalog.

  1. Remove internet access to every Expedition instance.
  2. Restrict access to authorized administrators on a trusted network. CISA recommends this restriction where patching cannot be applied immediately.
  3. Verify the applicable security fixes before using the tool. Installing an old fix does not restore vendor support.
  4. Rotate credentials processed through Expedition, including API keys, as Palo Alto Networks advised after updating.
  5. Use a dedicated migration host, not a machine running unrelated services.

If these controls cannot be established before conversion, escalate that exposure to the executive accepting the migration risk.

Before Any Rule Moves, Name the Approver and the Accepted Risk

Before conversion, name the approver for each rule you plan to retire. For a rule nobody can explain, record why it remains and who accepts the exposure. Auditors need a decision record, not a statement that the import succeeded.

The person who understands a rule may sit outside IT. A facilities manager may know why a building system needs remote access; a business owner may know why a supplier connects overnight. Assign ownership by business function, not just by firewall administration rights.

Find Ghost Rules and Any-Any Rules Before the Freeze Starts

Start observation early enough to capture the jobs your business actually runs. October logs cannot prove that a rule is unnecessary for a December year-end process. Where the observation window is incomplete, keep the rule under review rather than treating silence as evidence.

What Counts as a Ghost Rule

A ghost rule has not matched traffic over an observation window covering its relevant business cycles, including infrequent annual jobs. Zero hits over a few weeks justify investigation, not deletion.

Check counters against retained logs and application schedules. Have the owner confirm retirement in writing. If the next scheduled use falls outside your migration window, document that exception and retain the required access until it can be tested.

Narrowing Any-Any Rules Without Guessing

An Any-Any rule hides its actual purpose behind broad permission. Enable logging, observe the flows through a relevant business cycle, and have the owner confirm which access is required.

Then narrow the rule to those confirmed flows. Nobody remembering its purpose is not evidence that it is unused. If you cannot establish its full purpose before cutover, record the remaining exposure and assign a review date.

Merge Duplicate Objects and Check NAT Before You Trust an Import

Merge Duplicate Objects and Check NAT Before You Trust an Import, Total 360 Security

A matching object name does not prove a matching address. Compare values and device-group context before merging objects. Otherwise, cleanup can silently change where a rule sends or permits traffic.

  1. Keep the original configurations before conversion. Expedition’s temporary parser database is cleared after migration.
  2. Compare object values before accepting a merge, including objects with identical names in different device groups.
  3. Check each converted NAT rule against the original translation. A plausible-looking rule can still translate to the wrong address.
  4. Test each NAT pair with a known flow and record the result.
  5. Manually verify translations where source-vendor syntax leaves the parser’s interpretation uncertain.

Keep a short decision log for every merge and NAT change, with the original value, the new value and the person who approved it. When a translation is questioned later, that log is the difference between a quick answer and a rebuild.

Convert to App-ID and Tag Every Rule for the Auditor

Expedition supports moving port-based rules toward application-based policy. Its Machine Learning module generates policy suggestions from observed traffic. Its Best Practices Assessment checks configurations against Palo Alto Networks’ recommended practices. Neither replaces an owner’s approval.

Treat Machine Learning Output as Candidates

Check each suggested application against what the application owner says runs on that port. Logs only describe the captured window; they cannot establish the needs of a quarterly process that never ran during collection.

Record why you accept or reject a suggestion. That decision record explains exceptions when an auditor later asks why the deployed policy differs from the tool’s recommendation.

Name Rules in Panorama by Owner and Ticket

Use rule names and tags in Panorama to retain business ownership, with a change ticket and review date. This is professional practice, not a published standard. It gives the next reviewer a person to ask and a record to inspect instead of another unexplained permission.

Cut Over in Phases, Outside the Change Freeze

Cut Over in Phases, Outside the Change Freeze, Total 360 Security

Move one zone or business unit at a time. Define the observation period before cutover and retain a tested rollback until the new policy has handled representative business traffic.

  1. Select a lower-risk zone. Document its window and rollback procedure, including who can authorize reversal.
  2. Validate the converted policy against observed traffic before production enforcement. Do not assume two policies can enforce the same flow simultaneously.
  3. Cut over the zone and inspect permitted traffic as well as unexpected denials.
  4. Keep the legacy configuration available as a tested rollback through the agreed review period.
  5. Obtain the business owner’s sign-off before moving to the next zone.

If your organization freezes changes in November or December, plan backward from that date. Starting cleanup in the final week leaves no room to investigate unexplained flows. Scheduling a routine cutover inside an approved freeze is a governance failure, not merely a scheduling problem. Move it to the next authorized window rather than compressing validation.

After Cutover, Keep the Evidence and Retire the Utility

Expedition 2.0 stores project and device data in shared host volumes. Those files can contain firewall configuration secrets. Restrict access and encrypt stored data; securely remove project data from the migration host after preserving the required evidence.

Save the source configurations and converted output, with the mapping decisions needed to explain the result. The parser’s temporary storage is not your audit archive. Organizations handling sensitive Texas records should review applicable obligations, including Texas SB 2610, rather than assuming a successful firewall migration establishes compliance.

Uninstall the utility when the project closes and record its retirement. Assign ongoing ownership of policy reviews and exceptions. An unsupported migration server has no reason to remain running after its work is complete.

Total 360 Security, based in Fort Worth, runs security programs across 13 risk domains and reports to the board. If your migration has technical implementers but no accountable security leader, review our enterprise security risk management program, then call 817-677-0515 to discuss that ownership gap.

Frequently asked questions

What replaced Palo Alto Expedition?

Palo Alto Networks says it is transferring Expedition’s core functionality into new products. Its end-of-support notice does not establish a single replacement for every workflow. Confirm the current supported conversion path for your source firewall and target PAN-OS environment directly with the vendor.

Is Palo Alto Expedition free?

The documentation supporting this article does not establish current pricing or licensing terms. Confirm those terms with Palo Alto Networks before using it. Regardless of acquisition cost, Expedition has been out of support since January 2025 and requires controlled handling of sensitive configurations.

What vendors can Expedition migrate from?

Palo Alto Networks’ documentation names Check Point and Cisco among supported source vendors. Check compatibility for your specific platform and configuration version before planning the migration. Vendor support in a parser does not guarantee that every rule will translate correctly.

What is a ghost rule in a firewall policy?

A ghost rule has not matched traffic during an observation window long enough to cover its relevant business cycles. That window must account for infrequent work, such as annual processing. Confirm its purpose with the business owner before retiring it; a few weeks of zero hits are insufficient.

Is Expedition safe to expose to the internet?

No. On vulnerable Expedition servers, CVE-2024-5910 and CVE-2024-9464 can be chained to allow unauthenticated command execution. Restrict the utility to authorized users on a trusted network, verify applicable fixes, and rotate credentials processed through it after updating.

Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.

Serving Texas, California, Nevada, New Mexico.

Palo Alto Expedition in 2026: End of Support Explained