Before the upgrade
- read the release notes for the target version
- download the bundle and verify its checksum
- confirm your entitlement and any updated license material if the commercial state changed
Upgrade docs
Treat Cerberus upgrades like controlled self-hosted changes, not like a background SaaS release.
Nyalma can tell you which release is current and provide the bundle, checksum, and notes. Your team still owns rollout timing, approval, validation, and rollback inside the target environment.
During rollout
- use staging or a controlled validation path where feasible
- coordinate firewall, identity, and network-integrated changes through your own change controls
- capture timestamps and version details so support can help faster if something goes wrong
Rollback expectations
- keep snapshots, exports, or backups for the affected environment
- know which version and checksum you are rolling back to
- treat rollback planning as a customer responsibility, even when support is involved
When to ask for help
- open a portal case if you already have customer access and need threaded follow-up
- use the public support path for support add-on or enterprise rollout conversations
- include version, deployment mode, and the exact step where the rollout diverged