May the 4th (+4)
Roadmap Session and Use Cases for
Cloud Security, SASE, and Email Security
SASE Masters:
Deploying Harmony SASE for a 6,000-Strong Workforce
in a Single Weekend
Paradigm Shifts: Adventures Unleashed!
Capture Your Adventure for a Chance to WIN!
Mastering Compliance
Unveiling the power of Compliance Blade
CPX 2024 Content
is Here!
Harmony SaaS
The most advanced prevention
for SaaS-based threats
CheckMates Go:
CPX 2024 Recap
I assume the corresponding fix is this one: https://github.com/CheckPointSW/SmartMove/commit/58d249452c5ba1dcb109582dc1b9ca5aaa6e4465
Unfortunately this breaks SmartMove for a PaloAlto (8.1) config export where panorama isn't the first device in alphabetical order.
Example contents of a no longer working export file:
devfw01_111111111111.xml
devfw02_222222222222.xml
panorama_333333333333.xml
prodfw02_444444444444.xml
prodfw02_555555555555.xml
Before the code change, every file would be checked for existence of a node "panorama" until there is a match.
After the code change, the first file is assumed do be the panorama config without checking anything.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY
