Downloads and Verification

1. Choose the release and rollout path

Open portal Downloads and check whether the release is Stable or Preview.
Open the selected version there for its full release notes, migration and breaking-change flags, and any advisory.
Confirm the host and Check Point requirements and choose a fresh installation or an upgrade of an existing signed-installer deployment.
For an upgrade, identify your current version and the required backup and recovery point before scheduling downtime.

Expected result: one selected version, an agreed change window, and the correct installation or upgrade procedure.

2. Open the account's download catalog

Sign in to your customer account, complete email verification, and resolve any required Terms review. An eligible software entitlement is required for protected downloads. Buying Optional Support does not replace that entitlement.

In Downloads, open the selected version's release details. These show the exact file names, recorded digests, signing key identity, and verification commands. If no release is available for your account, ask support rather than obtaining an installer from an unverified mirror.

Check license and entitlement access

3. Collect the matching release files

Installer bundle: the application images, host tooling, configuration templates, and version-specific operating guides.
Signature (.minisig): verifies the bundle against the independently confirmed Minisign public key.
Checksum (.sha256): checks the downloaded bundle's bytes. It does not establish the publisher's identity on its own.
SBOM: the CycloneDX component inventory for your software review.
Release notes: the changes, rollout considerations, and available advisories for that version.

Keep the original file names and place the bundle, signature, and checksum in the same directory. Retain the matching signed release with your recovery records. Your customer license is a separate file issued under Licenses; it is not the installer signature.

4. Verify before extraction or installation

Request and independently confirm the Minisign verification key, its SHA-256 fingerprint, and signing key identity.
Use the selected release's portal verification commands to check that key fingerprint and verify the detached signature.
Check the installer against both the published digest in the release record and its matching checksum file.
Continue only when every check succeeds. Preserve the version, digest, and verification result with your change record.

The portal supplies commands containing that release's exact names and digest. Use those commands instead of substituting a version into an example. Do not extract the bundle or run a script with administrator privileges while a required file or successful verification is missing.

If a download or verification fails

Interrupted or incomplete download: return to the release in the portal and start a fresh download. Verify the newly saved file; do not assume a browser's progress indicator proves completion.
Checksum mismatch: check that all files belong to the same version, download them again, and repeat verification. A repeated mismatch needs support investigation.
Unknown key or failed signature: stop. Independently confirm the key identity and fingerprint; do not replace the trusted key with one extracted from the unverified bundle.
Access denied or missing download: review the account's license, Terms, and billing status. Use account help if you cannot enter the portal.

A portal transfer record shows delivery through the portal, not that your browser saved the file or that it was installed. Keep your own verification result. For help, send the version, artifact name, time, and sanitized error using the support request checklist.

5. Continue with the matching procedure