Warning tiers in this document

Our set of warning messages represent 4 different types of digital hazards. If applicable, we also add the possible impact (HIGH, MEDIUM, LOW) within the warning message.

  • Our warning types are as follows:
  • Potential security risk (red)
  • Potential performance issue (orange)
  • Potential functional limitation (yellow)
  • Notice (blue)

We always place our warning messages before the hazardous situation.

Compact warnings

Within instruction lists, we make use of compact versions of warning messages.

  1. Step by step
  2. This is an action step, followed by a compact warning message.
  3. High warning level. Used wherever there could be a major data safety hazard.

  4. This is a follow-up action step

Compact warning messages are equivalent to our standard warning messages.

Standard warnings


This universal type of warning will be replaced by one of the following specific warning tiers, within our effort to streamline and improve our documentation.

(HIGH / MEDIUM / LOW) – Used in case of a data security hazard.

  • Example:
  • HIGH – Placed before internal data are exposed to the internet, e.g. because of disabled security measures.

(HIGH / MEDIUM / LOW) – Used in case of a functional restriction or limitation hazard.

  • Example:
  • MEDIUM – Placed whenever it is likely that a feature might be misconfigured, but does not sacrifice the overall security level. For instance, when a new feature can be configured in a way, that it does not work correctly but cannot lead to data exposure either.

(HIGH / MEDIUM / LOW) – Used for performance-related issues.

  • Example:
  • MEDIUM – Placed whenever it is likely, that a high server workload can lead to weak performance.
  • HIGH – Placed whenever continuous aggressive logging will create storage problems after a short time.

(HIGH / MEDIUM / LOW) – Used as a general warning type. Used in cases where none of the other warning types are applicable.

  • Example:
  • MEDIUM – Often used for advanced configuration recommendations.
  • LOW – Placed whenever a non-safety, non-performance-related feature can be activated. Often used for feature related recommendations.