This chapter describes how to run an Axon Ivy Engine in a safe way. This is important whether you provide an Ivy engine in a secure intranet environment or you make your engine accessible via the internet. Some parts need to be implemented by your IT Operations provider:
Run the Axon Ivy Engine behind a fully patched reverse proxy server (like NGINX, Apache HTTP Server or IIS).
Disable direct access to the Axon Ivy Engine.
Only allow access to the URLs of your application and block all other access.
Run the Axon Ivy Engine with a dedicated system user and database users with limited access rights.
Run the latest Axon Ivy Engine major version with all updates marked as security relevant.
Only serve users via HTTPS (configured on the reverse proxy).
Document and automate the server setup.
Ensure that the provider performs daily backups (database, relevant engine folders) which can also be restored…
Read more about other security tweaks which you can apply to your Axon Ivy Engine: