Fig. 1: Option one: If a company runs its IT infrastructure and database platform with the same cloud provider, there is only one internal cloud connection that is easy to protect. Source: MariaDB
Fig. 1: Option one: If a company runs its IT infrastructure and database platform with the same cloud provider, there is only one internal cloud connection that is easy to protect. Source: MariaDB
Fig. 2: Option two: The corporate applications run on the corporate network. Source: MariaDB
Fig. 3: The company australia telegram screening applications run in a different cloud. Source: MariaDB
But activating such modules integrated into the database system is not enough. A fundamental security consideration concerns the connection of the individual users or applications with the cloud database. The decisive factor here is whether it is located in the same or a different infrastructure or cloud. The simplest case occurs when the company operates its IT infrastructure and the database platform with the same cloud provider. In this case, there is only one internal cloud connection, which is easy to protect.
In the other two cases, the corporate applications run in the classic corporate network (Fig. 2) or in another cloud (Fig. 3).
In both of these cases (Fig. 2 & 3), the connection to the database is via the Internet. Special security measures are required here. The first security option is VPN access. This creates an encrypted, private tunnel between the database network and the company network. If the provider does not offer this, a firewall with IP address filtering must be installed in front of the database access. In this case, only very specific clients are allowed to connect to the DBMS and they are recognized by their IP address. It is possible to only allow IP addresses or address ranges from the company network .