After upgrading your system

After upgrading to A33.20 or to a hotfix version of the build, follow the steps in this topic before running your ASMS system.

Check upgrade success

To make sure that the upgrade to A33.20 was successful, perform system sanity checks.

Do the following:

  1. In the algosec_conf main menu, select 17 System health.

  2. Select 1: Check services status to check that basic ASMS processes are running on your machines.

  3. Select 2: Check system health and run a Full check.

Run all firewalls

Run a manual analysis to create an unscheduled report on all on individual devices and groups defined in AFA. See Run a manual AFA analysis.

SSO integration (if applicable)

If you used custom UID parsers (in pre-existing SSO environments), you may need additional adjustments to your local code. See Configure a customized UID parser​.

For Check Point R80 device version R80.30 and lower | configure SFTP

For an R80 device version R80.30 and lower, enable SFTP on the device. To enable SFTP, see Check Point SecureKnowledge article sk82281.

Google Cloud ACE permissions check

After upgrading to A33.20, make sure ACE permissions are up to date so that maps & Traffic Simulation Queries will run flawlessly. See ACE Google Cloud Permissions.

FireFlow | Update the SuggestPropertyValues Hook for Time Objects on Check Point Devices

If you use the SuggestPropertyValues hook for Time Objects on Check Point devices, make sure to update your configuration after upgrading to A33.20:

Change the time object parameter name:

  • From: schedule

  • To: time

This update is required for proper handling of time objects on Check Point devices in A33.20. See Use hooks to control parameters .