ELMA365 relies on a set of proven security technologies for data storage and exchange: PostgreSQL, MongoDB, S3, RabbitMQ, and Redis. Interactions with external systems are secure due to JWT authentication and server-side authorization check.

ELMA365 microservices work inside the Kubernetes cluster (Micro8k solution is used off-the-shelf, however, a deployment within a custom clustering solution is possible).  The communication between microservices is organized through secure HTTP and gRPC protocols. 

Ingress rules are used to expose the services from within the cluster to services outside the cluster via HTTP and WebSocket protocols.  Due to such configuration, direct access to cluster services is not allowed.

PostgreSQL is used as a primary database, providing all the necessary security features. For the ELMA365 Cluster, we advise hosting DBMS on dedicated servers and managing its security separately from the primary system. Make sure that you have read the server installation and security instructions carefully.

• PostgreSQL Installation Guide.
• Server Administration.
• Server Setup and Operation.
• Connections and Authentication.
• Client Authentication.
• Database Roles.

The ELMA365 system also uses the MongoDB database. For the ELMA365 Enterprise edition, we advise hosting database software on a dedicated cluster managed separately. Read the installation and security configuration guide carefully.

• MongoDB Installation Guide.

The ELMA365 system uses S3-compatible object storage to store user and temporary files. By default, we offer an S3 MinIO solution that is relatively simple to deploy and administer. MinIO ensures confidentiality and integrity of the processed data through server-side encryption and digital signatures with a limited validity period. For the ELMA365 Enterprise edition, we advise hosting S3-compatible object storage in a dedicated cluster. If you decided to deploy S3 MinIO, read the corresponding security manual carefully:

• S3 MinIO Security Overview.

Please note that the security of the server operating system, virtualization provider, and the physical server is a client’s responsibility and is not part of ELMA365 On‑Premises security framework.

Was this helpful?

Thanks for your feedback!

Please specify why:

Recommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

How we can improve it?

YesNo

Please specify whyRecommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

Found a typo? Highlight the text, press ctrl + enter and notify us