Sign in Request access

Palo Alto Strata Cloud Manager Optimization

Clean up Palo Alto policy before it moves to Strata Cloud Manager. NetConverter does not read SCM configurations today; it analyzes the Panorama XML or PAN-OS firewall configurations you plan to move for shadowed rules, stale objects, and change-risk hotspots.

Analyze Panorama or PAN-OS View Optimization Platform

Policy Hygiene

Identify redundant, legacy, and low-value rule segments in the Panorama or PAN-OS policy you plan to move.

Security Gap Analysis

Spot mismatched intent and risky access patterns prior to rollout changes.

Actionable Cleanup Plan

Generate prioritized remediation guidance for engineering and change-approval workflows.

Optimization and Migration to Strata Cloud Manager

Strata Cloud Manager changes the shape of policy review. Instead of Panorama's device-groups and XML candidate configs, SCM delivers policy through a cloud-managed folder and snippet hierarchy where rules inherit down the tree. That inheritance is powerful, but it hides debt: a rule three folders deep can be permanently dead because a parent-folder rule already matches the traffic — something that is hard to see by eye. NetConverter does not read SCM policy today, so run the cleanup on the Panorama XML or PAN-OS configuration before the move: NetConverter evaluates the effective rule base there, surfacing shadowing, redundancy, over-permissive any-any-allows, and unused or duplicate address and service objects as a prioritized, exportable cleanup plan.

Strata Cloud Manager is supported on request, not in the self-service hosted platform. The hosted service does not log in to SCM or push changes to an SCM folder. Review the supported platforms before planning a migration.

Related: see the Panorama → Strata Cloud Manager migration guide, the optimization platform, Panorama vs. Strata Cloud Manager optimization, and Cisco ASA → Palo Alto migration.

Frequently Asked Questions

What does Strata Cloud Manager optimization check?
NetConverter does not read Strata Cloud Manager configurations today. Before an SCM move, analyze the Panorama XML or each PAN-OS firewall configuration you plan to move: NetConverter flags shadowed and redundant security rules, over-permissive any-any-allow entries, unused address and service objects, and duplicate objects defined under different names, so the policy you carry into SCM is already clean. Findings are returned as a prioritized, exportable cleanup plan.
Can NetConverter migrate a Panorama configuration to Strata Cloud Manager?
On request. Conversion to Strata Cloud Manager is supported on request, not in the self-service hosted platform, and the tooling is not published yet. The hosted service does not accept it as a target, log in to SCM, or push into a folder.
How does Strata Cloud Manager differ from Panorama as a migration target?
Panorama organizes policy with device groups and templates; Strata Cloud Manager uses folders and snippets. Plan mapping and target validation for the specific deployment. SCM is supported on request, not in the self-service hosted platform.
Does optimization push changes to SCM automatically?
The hosted service does not log in to SCM or push changes into a folder. SCM is supported on request, not in the self-service hosted platform.
Which source firewalls can be analyzed or migrated toward Strata Cloud Manager?
NetConverter supports selected Cisco ASA, FortiGate, and Palo Alto migration paths. Strata Cloud Manager is supported on request, not in the self-service hosted platform; consult the supported platforms page for available paths.