ENSURING THE CONFIDENTIALITY OF DEVOPS DATABASES

Authors

DOI:

https://doi.org/10.18372/2410-7840.24.16852

Keywords:

data base, DevOps, data masking, database testing

Abstract

Data base development integration in to the DevOps delivery pipeline is a nessential challenge due to the growing popularity of this application development methodology. The goal of integrating data base changes as part of the DevOps process is to speed up the delivery ofany data base changes. Data base DevOps practice aimstorm prove the data base management efficiency. This practice helps optimize the process of data base deployment and modification, making it possible to auto matemany aspects of the data base life cycle. However, the implementation of Data base DevOps faces certa in challenges. The peculiarities of the database as an object of the information system lead to the fact that their full automation of testing is possible only on data that are as close as possible to the real data in the production database. However, the use of real data creates legitimate data confidentiality risks. The article discusses the methodology of data preparation for testing, meet the requirements of realism and provides the confidentiality of real data. To create this methodology, the analysis of thedatabase development process integrationin DevOps features carried out and problematic identified in terms of operation confidentiality in the DevOps delivery pipeline. These are DB testing operations performed at different stages of DevOps.To maintain the adequacy of the subject area data on the one hand, and ensure its confidentiality on the other hand, a sequence of transformations of information in the database that meets these conditions is proposed.

References

Liquibase.URL:https://www.liquibase.com/resources/reports/database-deployments-2019.

DORA-State of DevOps. URL: http:// cloudplatformonline.com/rs/248-TPC-86/images/ DORA-State of DevOps.pdf.

SQL Server 2015 Release Notes. URL: https:// docs.microsoft.com/en-us/sql/ssdt/download-sq l-server-data-tools-ssdt?redirectedfrom=MSDN &view=sql-server-ver15.

Framework documentation. URL: https://docs. microsoft.com/en-us/aspnet/mvc /overview/ getting-started/getting-started-with-ef -using-mvc /migrations-and-deployment-with-the-entity-fra mework-in-an-asp-net-mvc-application.

TSQLT. Full user guide. URL: https://tsqlt. org/full-user-guide/.

best types of software testing. URL: https:// dzone.com/articles/4-best-types-of-software-tes ting.

Unmasking the Dynamic Data Masking. URL: https://www.red-gate.com/simple-talk/ blogs/unmasking-the-dynamic-data-masking/.

Коломыцев М.В., Носок С.А., Мазуренко А.Е. Маскирование таблиц базы данных с использованием технологии SQL CLR // Захист інформації – 2017. – Т.19, № 1. - С.16-22.

Коломыцев М.В., Носок С.А., Мазуренко А.Е. Обеспечение цело-стности внешних ключей маскированной базы данных // Захист інформації – 2015. – Т.17, № 5. – С.306-311.

Downloads

Published

2022-10-11

Issue

Vol. 24 No. 1 (2022): Захист інформації

Section

Articles

License

Authors who publish with this journal agree to the following terms:

  1. Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.

  2. Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.

  3. Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access).