Installation
Install Cerberus self-hosted, verify the bundle, connect Check Point, and keep the portal out of the runtime path.
Open installation docsDocs
These public docs explain how Nyalma Cerberus works as a self-hosted Check Point governance tool. The portal remains the place for account-gated downloads, issued license material, release artifacts, and support history.
Install the self-hosted Cerberus runtime, then connect Check Point and import the local license.
OpenHow `license.json` and `cerb1:` material is issued in the portal and verified inside Cerberus.
OpenWhy installer bundles, checksums, signatures, SBOMs, and release notes stay account-gated.
OpenHow to stage upgrades and keep self-hosted Cerberus deployments portal-independent.
OpenWhat support covers, what a good ticket includes, and when to use the portal.
OpenProduct tour
Cerberus is not just a download flow. The installed workspace brings rulebase browsing, delegated access, limited log access, approvals, licensing, and audit evidence into one local control surface.




Doc paths
Install Cerberus self-hosted, verify the bundle, connect Check Point, and keep the portal out of the runtime path.
Open installation docsUnderstand how the portal issues `license.json` and `cerb1:` material while Cerberus verifies it locally.
Open licensing docsReview why release bundles, checksums, signatures, SBOMs, and release notes stay tied to portal access.
Open download docsPlan staged upgrades, know when to open a portal case, and keep change control with your own team.
Policy index