Content updates

Cymph ships two kinds of content with the product: the framework contents behind Mind Maps and framework mappings — MITRE ATT&CK, D3FEND, ATLAS, NIST CSF, ISO 27001, NIS2, GDPR, DORA and the others listed under Frameworks supported — and the material shown in the in-app Learning Center. Both are bundled with each release, so they are normally refreshed when the deployment is upgraded. Content updates is an optional setting that lets the deployment fetch newer versions of that content between releases, from a content service that Cymph hosts in the EU. When a framework publishes a new version, or the Learning Center gains new material, the deployment picks it up without waiting for the next product release.

​

What it does

With content updates enabled, the deployment periodically connects outbound over HTTPS to Cymph’s content service and downloads whatever is newer than what it already holds: The connection is one-way. The deployment downloads content; it does not upload anything. No playbooks, executions, assets, chats, users, integration configuration or credentials are sent to Cymph, and the content service receives nothing beyond what any HTTPS client sends to any server — the request itself and the originating IP address. Updates never change existing work:

• Presets keep their version. Frameworks are versioned and a preset is pinned to the version you chose when you created it, so a newly downloaded version never silently changes the meaning of an existing preset — see Frameworks without framework maintenance. To use a new version, edit the preset and select it.
• Framework mappings on playbooks are untouched. A mapping to a technique stays as you set it. Techniques that a new version revokes or deprecates are reported as validation issues when a preset using that version is built, as described in Stale technique IDs in shipped content, rather than remapped or dropped.

​

What it does not cover

Content updates carry framework and Learning Center material only. They do not upgrade the product: application code, the embedding model behind semantic search, AI prompts and feature behaviour all change with product releases, exactly as before. Nor do they involve licensing or telemetry — a deployment with content updates disabled makes no connection to Cymph at all, and a deployment with them enabled makes only this one.

​

Enabling or disabling content updates

Users with the On-prem Administrator role can change the setting.

1. Go to the On-prem settings page
   • Click on On-prem from the navigation menu, then Settings

2. Enable or disable Content updates

The change takes effect immediately. Disabling it stops further checks; content already downloaded stays in the deployment and remains usable.

​

Networking

The deployment needs outbound HTTPS to Cymph’s content service, which is hosted in the EU. In a self-hosted deployment with restricted egress, permit that destination from the API host or its egress proxy — see Outbound connections Cymph makes. A managed cloud tenant needs no network work on your side. If the content service cannot be reached, the deployment keeps running with the content it has; the next check happens on the normal schedule once connectivity returns.

​

When to leave it off

Leave content updates disabled when policy requires that the deployment make no connection to Cymph — an air-gapped or strictly egress-controlled environment, for example. You lose nothing except timeliness: the same framework and Learning Center content still arrives with each product release.