A database is the heart of many applications. It becomes all the more dangerous when this heart opens a back door into the system architecture for hackers. It is therefore no wonder that many companies are reluctant to migrate their database to the cloud. The associated uncertainties seem to be too great, even if advantages such as high availability and scalability are tempting.
According to the latest cloud monitor by the digital association Bitkom, eight out of ten companies are already using cloud computing [1] . The range of applications is broad and many companies use cloud databases. A similar picture emerges across borders: According to a survey by the International Data Corporation (IDC), 63 percent of the companies surveyed are in the process of moving their databases to the cloud or australia telegram screening have already done so [2] . Trust in this form of database management system (DBMS) is therefore high. It extends not only to performance, scalability and easy configuration, but also to database security.
The division of tasks between provider and company
Many security measures are easy to implement because the providers have equipped their systems with numerous security configuration options. However, this should not mislead the companies using them into believing that the provider alone is responsible for database security. This is wrong, because shared responsibility applies in the cloud. The providers are responsible for security and other requirements within a precisely defined framework, but the companies using them must also take on tasks related to database security. Unfortunately, this is sometimes overlooked or not implemented precisely. There have been some security glitches in which millions of data records in the storage services of cloud providers were freely available for access from the Internet. In practice, this shared responsibility can take on different forms.