MES.Site

Security & architecture

Security starts with the architecture – not with the next update.

MES.Site is meant to make websites easy to manage while avoiding unnecessary attack surface. To do so, we rely on a controlled code base, clearly separated permissions and flexible ways of running it. There is no absolute security in software development – but many risks can be reduced by basic architectural decisions.

Security

What MES.Site does differently from systems that can be extended at will.

  • No uncontrolled plugin landscape

    Common content management systems can be extended with plugins from many vendors – each with its own weaknesses, dependencies and updates. MES.Site deliberately does without: we develop, test and ship new features ourselves. Nobody has to worry about the compatibility and security updates of many add-ons.

  • Program code and content are separate

    The application runs as a user without write access to its own program files. Content and uploaded files are kept separately. Only checked file types are accepted – the content must match the extension, HTML and SVG are not allowed – and no uploaded file is ever executed as program code.

  • Administration separate from the website

    The administration is only available at its own address. On the website's domain there is no sign-in page, no /admin and no interface for writing – nowhere for anyone to try passwords.

  • The website may only read

    Public pages access the database with their own login that may only read. Even a flaw in the output could not change any content.

  • Strict rules in the browser

    A strict content security policy allows only our own scripts, styles and fonts and no third-party servers. Texts are checked against a fixed list of allowed elements on output – injected code has no effect.

  • Controlled updates

    Software changes only arrive through a defined process. Nobody can install add-ons with executable code on the side; components and versions stay manageable. Database updates only run on command, with a backup beforehand.

  • Roles, approval and log

    Everyone has their own access with exactly the rights they need. If required, nothing goes live without approval, and every change can be traced to a person and a time.

  • No public source code

    The source code of MES.Site is not public. That makes automated searches for weaknesses harder – but it replaces neither secure programming nor regular checks, so we do not rely on it alone.

  • Several websites and tenants

    One customer can manage several websites. Depending on the requirements, customers share a common infrastructure or get their own, separate installation.

Technical architecture

What MES.Site is built on and how it is run.

How MES.Site is built
Visitors open the website at the customer's domain
Editors manage the content at the separate admin address
Reverse proxy and load balancer TLS certificates automatically for every registered domain, requests only to ready instances (health check)
Instance 1 Linux container with ASP.NET Core, program files read-only
Public output may only read, output cache, strict CSP
Administration only at the admin address
Instance 2 Linux container with ASP.NET Core, program files read-only
Public output may only read, output cache, strict CSP
Administration only at the admin address
Microsoft SQL Server
  • Read-only login for the output
  • separate login for the administration
  • Updates only on command, with a backup
File storage Media separate from the program code, never executed
Sign-in service MES.Identity with OpenID Connect – no passwords in the CMS

The browser loads everything from our own server: no CDNs, no tracking services, no third-party fonts.

  • Modern .NET technology

    MES.Site is based on ASP.NET Core and runs as a container on Linux. The application is not tied to a particular hosting environment.

  • Several instances behind a load balancer

    For higher availability, several independent instances run – on the same server or on different ones. A load balancer in front distributes the requests.

  • Built-in health checks

    Health checks tell the load balancer whether an instance is ready. It only counts as ready once its database is at the matching version; until then it receives no requests.

  • Maintenance without planned downtime

    Instances are updated one after the other: while one is being maintained, the other answers requests. With compatible database changes, updates without planned downtime are possible.

  • Database can run separately

    Data is kept in Microsoft SQL Server, if required on a server of its own, separate from the applications. Compact installations on shared hardware work too; a highly available database can be planned as needed.

Ways of running it

  • Shared hosting Several websites and customers use an infrastructure run centrally by us – the MES.Site packages.
  • Own installation A customer gets an application environment of their own, with us or on their own hardware (self-hosting).
  • Redundant Several instances behind a load balancer, updates without planned downtime.
  • Distributed The instances run on different servers, if required with an existing firewall as the load balancer.

Security is an ongoing process

  • Even a deliberately small attack surface does not rule out flaws entirely.
  • That is why secure development, controlled changes, regular updates and careful operation are part of the concept.
  • We always fix software bugs free of charge.

All technical details – hosts, database logins, content security policy, data protection and operation – are in the document for IT. Document for IT (German only) →

Text suggestions with AI

During setup, an AI can suggest texts – only at the press of a button and only if wanted. The customer chooses the provider: Mistral with processing in the EU, OpenAI or Google Gemini, with their own key or the one from MES. Confidential or personal details do not belong in such a request.

As many features as necessary. As little attack surface as possible.