Nyalma Cerberus

Docs

Understand the Cerberus workspaces before you download.

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.

Product tour

What operators see inside a Cerberus deployment.

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.

Cerberus Rulebase workspace with connector selection and rule actions
Rulebase workspaceBrowse Check Point packages and layers, then use permissions, edit locks, ETags, and approval mode to control writes.
Cerberus Logs workspace with time filters, instance selector, and search input
Logs workspaceSearch by time, rule, instance, and fields. User log access filters can limit visibility without giving global log access.
Cerberus Identity and Access workspace with users, teams, roles, grants, and limited logs columns
Identity & AccessManage local users, teams, roles, grants, firewall scopes, and limited log permissions from one admin area.
Cerberus license import form for license.json and cerb1 license strings
Local license importImport `license.json` or a `cerb1:` string into the installed deployment; Cerberus verifies issued material locally.

Doc paths

Start with the operational path you are trying to understand.

Installation

Install Cerberus self-hosted, verify the bundle, connect Check Point, and keep the portal out of the runtime path.

Open installation docs

Licensing

Understand how the portal issues `license.json` and `cerb1:` material while Cerberus verifies it locally.

Open licensing docs

Downloads and checksums

Review why release bundles, checksums, signatures, SBOMs, and release notes stay tied to portal access.

Open download docs

Upgrades and support

Plan staged upgrades, know when to open a portal case, and keep change control with your own team.

Policy index

Trust, privacy, and support boundaries should be as easy to find as the install docs.