Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Risk management for Exponential projects

A risk register for Exponential projects: the usual risks of building and running a site, each with likelihood, impact and a mitigation that points to a real feature, page or command of the product.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/leadership/risk-management.md

On this page

Risk management for Exponential projects

This page is for project managers who keep a risk register. It lists the risks that come up again and again when an organization builds, launches and runs a site with Exponential, and for each one names a mitigation that the product or its documentation already provides: a feature, a page in the administration, a command or a procedure.

The likelihood and impact columns are a starting point for your own judgment, not measurements. The sources do not publish incident statistics; your project's own situation decides the real values. Every mitigation, on the other hand, links to the page that describes it.

Contents

  1. How to use this register
  2. The scales
  3. The risk register
  4. Risks in more detail
  5. Risk review rhythm
  6. A blank register to copy

How to use this register

  1. Copy the register into your project's own document (the blank form is at the end of this page).
  2. Remove what does not apply: a site without a shop drops the commerce risks.
  3. Score each risk for your project: likelihood and impact, with a reason.
  4. Assign an owner from your team for each risk and each mitigation.
  5. Review the register at the rhythm below, and whenever a gate is passed.

Risks that are specific to your organization (budget, staff turnover, procurement, legal) are not on this page. Add them; this page only covers what the product and its documentation can speak to.

The scales

ScoreLikelihoodImpact
1 LowUnlikely during the projectInconvenience; no visitor or editor notices
2 MediumCould well happen onceEditors or visitors are affected for a while; work is redone
3 HighExpected unless something is doneData loss, a security incident, a missed launch, or a site that cannot be maintained

Priority = likelihood x impact. Treat 6 and 9 first.

The risk register

The values in the L (likelihood) and I (impact) columns are suggested defaults for a typical project.

IDRiskLIMitigation in the productWhere it is described
R01Data is lost: a failed upgrade, a mistaken deletion, a broken disk23Database and files backed up together in maintenance mode; a restore tested on another machine; git_manager's backup manager for teams without a shellOperating a site, "Back up and restore", 10.9, git_manager
R02Content removed by mistake22Removed content goes to the trash first; the trash records who removed it and where; the audit trail records every removalThe trash view, The audit trail
R03An upgrade breaks the site23Rehearsal on a copy; the upgrade check before and after; verification commands; the rule "never run an installer over an existing site"Release and upgrade planning, 11.7, The upgrade check
R04A behavior change surprises users after an upgrade (for example accounts that can no longer sign in)22Read the changelog and behavior change notes of each period passed; the upgrade chapter lists the changes people meet most often11.6 step 3
R05A known vulnerability in a release you run23Security fixes are published as the next 6.0.x release; follow releases; composer audit; file consistency check after every updateSECURITY.md, Security hardening
R06A security problem you found is disclosed publicly before it is fixed13Report privately as SECURITY.md says, never in a public trackerWhen something goes wrong, "Security problems"
R07Brute force or credential stuffing on the sign-in23Failed sign-in handling, two-step sign-in, one account per person; audit alert rule for brute forceSecurity hardening, Two-factor login, Security and audit
R08Someone gets more access than intended23Roles built from limited policies; PreventPrivilegeEscalation (on by default) stops users granting what they do not hold; the role list marks full access and role-changing rolesRoles and policies
R09A change nobody can explain ("who did this?")22The audit trail, on by default: content, access, system and commerce channels, hash-chained, verifiableThe audit trail
R10Cross-site scripting through templates or extensions23Content Security Policy, report-only on the administration by default, reports collected in csp.log; switch to enforce step by stepContent Security Policy
R11Debug output or error details shown to visitors22System information health checks flag debug output, development settings and display_errorsSystem information, "Health checks", 13.4
R12Settings changed in the admin are lost at the next deployment, or differ between servers22ManagedByDeployment: the configuration of a siteaccess comes from version control onlyManagedByDeployment
R13A change goes live with stale caches, and the old version is served22exp:velocity deploy runs autoloads, caches, PHP reload and Velocity restart in the right order and stops at the first failureDeploying, section 7, 11.6
R14Cronjobs stop running and nobody notices (no indexing, no notifications, no audit alerts)22System information's cronjob check; the audit dashboard warns when its cronjob part has not run for an hour; the Cronjobs page shows recent runsCronjobs, System information
R15Logs fill the disk12Log rotation; log health against a disk budget (default 256 MB)Log viewer, "Log health", Log rotation
R16Broken links, missing files or unused assets after a content migration22Content checks: broken relations, missing files, unreferenced objects, storage filesContent checks
R17A required PHP version is not available from the host22Check the PHP table early; Supported: PHP 8.0 to 8.5; PHP 7.4 usable without support from 6.0.15PHP versions, Requirements
R18An extension does not load on the PHP of the server22exp:checkclasses reports every class PHP refuses to load11.6 step 4
R19A third-party extension is unsafe or unmaintained22Review its code before installing; extensions are Git repositories with visible historySecurity hardening, Extensions
R20Lock-in: the site cannot move to another host, database or team13GPL v2 or later code, full Git history, a choice of databases and operating systems, self-hostingWho is the Exponential Foundation?, Database support, OS support
R21Too few people with Exponential skills22See Skills availability below: an honest answer, not a featureDevelop with Git, Community places
R22Knowledge stays with one person ("bus factor")23Work in Git with reviewed pull requests; documentation in the repository; the handover documentRunning a team on Git, Project templates
R23A release of your own extension is published with a mistake22Check before tagging; a published tag is never moved; the fix is the next versionExtensions, "Release it"
R24Personal data ends up in logs, reports or bug reports22Logs mask addresses and secrets; the system report leaves out passwords and keys; the bug report advice says what to leave outRequest logs, "Privacy", Log viewer, When something goes wrong
R25Test mail reaches real people during development22The mail file transport writes mail to files; System information notes Transport=file10.4, System information
R26The site is slower after a change21exp:benchmark with a saved baseline exits 1 on a regressionBenchmarking
R27Editors cannot work during maintenance, or visitors see errors21Maintenance mode: a 503 page that is never cached, with a message and an end timeMaintenance mode
R28Accessibility requirements are not met22The admin4 design's tested WCAG rules; right-to-left support; your own checks for your own templatesQuality gates and acceptance, Right to left
R29A writing assistant sends content to an outside service against policy12Exponential Intelligence is inactive until activated; it writes drafts only; a data policy per provider (region us, eu or local)expai
R30The administration is reachable by anyone on the internet22The administration on its own host, restricted by network or VPN; request-shield in frontSecurity hardening, 13.5

Risks in more detail

Data loss (R01, R02)

The product's own guidance is blunt: "Test a restore on another server at least once; a backup you have never restored is a hope" (Operating a site). Make "restore tested" a line in every launch and upgrade checklist, with a date and a name.

A backup covers both places where Exponential keeps state: the database, and the files (var/, settings/override/, settings/siteaccess/, your extensions and designs). The files in settings/override/ hold database passwords, so the backup itself must be protected (Security hardening).

Upgrades (R03, R04, R17, R18)

Most upgrade risk is known in advance, because the project writes it down: each changelog opens with an "Upgrading" section, and the behavior change notes say what to check. The mitigation is a planning one: read before you estimate. See Release and upgrade planning.

Security (R05 to R11, R30)

The help page Security hardening walks through the threats one by one and ends with a checklist; the installation book's 13.16 Go-live checklist goes setting by setting. Put both into your launch gate. For watching after launch, the same page lists which log or tab records what ("Watching: logs, the request classifier and the audit trail").

Lock-in (R20)

These properties are documented and checkable:

What the product cannot remove for you: lock-in to your own custom code. Keep it in your own Git repositories, with documentation, and the handover is possible.

Skills availability

An honest answer for your register: the sources do not state how many developers or agencies work with Exponential. What they do document:

  • The project's code base goes back to 1999, and the documentation, the training books and the encyclopedia of the earlier years remain available under free licenses (Who is 7x?).
  • The community has a forum, a Telegram chat and issue trackers (Community places).
  • 7x offers services for new sites, migrations and support of existing sites (Who is 7x?).
  • The help pages are written so that a user can grow into a developer (Develop with Git).

Mitigations you control: budget time for onboarding, pair a new developer with an experienced one on the first tasks, and keep the project's own knowledge in Git and in documentation.

Knowledge concentration (R22)

Make reviews part of the work (every change is a pull request that a second person reads), keep settings in version control, and keep a handover document from the first week, not the last (Project templates).

Risk review rhythm

WhenWhat to reviewWho
Project startScore every risk; assign ownersProject manager with the team
Each gateRisks of the next phase; close what is pastProject manager
Before go-liveR01, R03, R05 to R11, R13, R14, R30 in particularProject manager, administrator
Weekly after go-liveThe weekly checklist of Operating a siteAdministrator
Each upgradeR03, R04, R17, R18Administrator, developer

A blank register to copy

Risk register: <project name>          Version: <date>          Owner: <role>

Scales: Likelihood 1 low / 2 medium / 3 high; Impact 1 low / 2 medium / 3 high; Priority = L x I

| ID  | Risk                     | L | I | P | Mitigation (feature, page, procedure) | Owner  | Due     | Status |
|-----|--------------------------|---|---|---|---------------------------------------|--------|---------|--------|
| R01 | <risk>                   |   |   |   | <mitigation, link>                    | <role> | <date>  | open   |
| R02 |                          |   |   |   |                                       |        |         |        |

Closed risks:
| ID | Closed on | Why |

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x