Wiki source code of Server data protection
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | === Operations logging === | ||
| 2 | |||
| 3 | All operations performed in the Loymax system go along with mandatory logging — recording of information about operations and their initiators in separate files. Log files do not contain personal user data, passwords, keys and access tokens in open form. At the same time, there is always a possibility to get the required information using logs (for example, who performed a certain action and when), however, access to log files is strictly limited. For example, developers or testers can get excerpts from logs only upon request to the technical support service. | ||
| 4 | |||
| 5 | Log files are stored in the Data Storage System with Raid10 backup technology. This solution ensures reliable storage of information resources and guaranteed access to them. At the moment, the log storage includes records for the entire period of the System operation. | ||
| 6 | |||
| 7 | === Database backup === | ||
| 8 | |||
| 9 | To prevent damage or loss of data stored in the database, the process of data backup has been arranged. In this respect, not all the data are copied, but only valuable data — information about purchases, users, accounts. Data copying for the entire period of the System operation (full backup) is launched every week, and changes for the previous day (incremental backup) are copied on a daily basis. The backup copies storage time is 2 weeks from the date of creation. After that, outdated files are automatically deleted. | ||
| 10 | |||
| 11 | Before updating the System, which includes changes to the databases, a backup copy of all databases is created. Only administrators have access to database backup files. | ||
| 12 | |||
| 13 | (% class="box" %) | ||
| 14 | ((( | ||
| 15 | **Recommendations for creating MS SQL database backups:** | ||
| 16 | |||
| 17 | * Data copying for the entire period of the System operation (Full Database Backups (SQL Server)) — every week; | ||
| 18 | * Transaction Log Backups (SQL Server) — daily: in the morning (prior to the start of working hours of retail outlets) and in the evening (after the end of working hours of retail outlets). | ||
| 19 | * If required, it is possible to add Differential Backups (SQL Server) to speed up the backup process and reduce the risk of data loss. The recommended retention time for backup copies is 2 weeks after creation. | ||
| 20 | ))) | ||
| 21 | |||
| 22 | === Protection against unauthorized access and copying === | ||
| 23 | |||
| 24 | The System provides the following protection measures against unauthorized access and data copying: | ||
| 25 | |||
| 26 | * A separate network segment with limited access is allocated for the servers with data. Access to data is limited by user rights. | ||
| 27 | * Ongoing audit, logging, and monitoring of data access are carried out. | ||
| 28 | * Each employee has a personal account to use office PCs. Therefore, access by unauthorized users is excluded. | ||
| 29 | * Only employees from the agreed list have access to Loymax Platform of an individual Company. Each of them is provided with an additional account. | ||
| 30 | |||
| 31 | === Regular data cleanup === | ||
| 32 | |||
| 33 | Historical data are stored in the database for a set period of time, after which they are cleared. The following regular cleaning tasks are set in the System: | ||
| 34 | |||
| 35 | * [[Event calculations>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Event_Calculation_Clearing_Regular_Task.WebHome]]; | ||
| 36 | * [[Target audience calculations>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Regular_Task_Setting_on_Target_Audience_Calculation_Clearing.WebHome]]; | ||
| 37 | * [[Event data>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Event_clearing_Regular_Task.WebHome]] (calculation and deduction of bonus points, information on purchases, etc.). | ||
| 38 | |||
| 39 | Regular tasks on cleaning up event calculations and target audience calculations are set up in the System by default and perform data cleanup on a daily basis. The frequency of triggering a regular task to clean up events is set during configuration. The full list of database tables to be cleaned by this regular task is provided in the corresponding [[article>>doc:Main.Installation_and_configuration.Extra_modules.Regular_tasks_setting.Event_clearing_Regular_Task.WebHome]]. |