Wiki source code of Information security
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% class="lead" %) | ||
| 2 | Information security of the Loymax System includes a number of tools and methods for secure data handling. | ||
| 3 | |||
| 4 | (% class="box warningmessage" %) | ||
| 5 | ((( | ||
| 6 | Information provided in this section is for guidance only. To ensure protection of your customer data and operations, it is recommended to utilize ALL the security measures listed in this section. Otherwise, Loymax is not responsible for any possible information leakage. | ||
| 7 | ))) | ||
| 8 | |||
| 9 | All mentioned means are aimed to protect personal data of customers and users of the System, ensuring secure data exchange between the server and end users without any loss or data interception. In this respect, each person involved in the process is granted access to the specific data they are allowed to get and are prevented from obtaining any data they should not have. Only precise and reliable information about customers, purchases, and other transactions is stored in the System. | ||
| 10 | |||
| 11 | == Data protection at the start == | ||
| 12 | |||
| 13 | Before launching the Loyalty Program (LP) and issuing cards, it is recommended to perform the following settings that will help to protect you and your customers from leakage of confidential information: | ||
| 14 | |||
| 15 | (% style="width:auto" %) | ||
| 16 | |(% style="border-color:white; width:451px" %)((( | ||
| 17 | ((( | ||
| 18 | (% class="box infomessage" id="HUseacomplexalgorithmtogeneratecard2Fcouponnumbers" %) | ||
| 19 | ((( | ||
| 20 | **Use a complex algorithm to generate card/coupon numbers** | ||
| 21 | ))) | ||
| 22 | ))) | ||
| 23 | )))|(% style="border-color:white; width:1039px" %)Each card number must be unique and consist of 15-16 digits formed by a special algorithm. Read our [[recommendations on generation of card number templates>>doc:Main.Using.MMP.Admin_panel.Cards_issue.Card_issue_recommendations.WebHome]]. Loymax system, in turn, ensures that cards are issued upon registration in such a way that one card can belong to only one customer. | ||
| 24 | |(% style="border-color:white; width:451px" %)((( | ||
| 25 | ((( | ||
| 26 | (% class="box infomessage" id="HSetcriticallimits" %) | ||
| 27 | ((( | ||
| 28 | **Configure the most important limits** | ||
| 29 | ))) | ||
| 30 | ))) | ||
| 31 | )))|(% style="border-color:white; width:1039px" %)((( | ||
| 32 | We have pointed up several limits that we [[recommend configuring in the first place>>doc:Main.Using.MMP.Admin_panel.Limits.WebHome]]. This will help to prevent misuse by employees of points of sale (POS) and customers, fraudulent actions with the data of LP Members, and associated potential financial losses. | ||
| 33 | ))) | ||
| 34 | |(% style="border-color:white; width:451px" %)((( | ||
| 35 | ((( | ||
| 36 | (% class="box infomessage" id="HConfigurecaptchainPersonalAccountonthewebsite" %) | ||
| 37 | ((( | ||
| 38 | **Set up captcha in the Personal Account of the website** | ||
| 39 | ))) | ||
| 40 | ))) | ||
| 41 | )))|(% style="border-color:white; width:1039px" %)((( | ||
| 42 | To protect against hacking, customer authorization in the Personal Account on the website can be protected by an [[invisible captcha>>path:/xwiki/bin/view/Main/Installation_and_configuration/Personal_account_configuration/Invisible_captcha/]] that recognizes user behavior and, in case of suspicious actions, issues additional tasks for verification. | ||
| 43 | ))) | ||
| 44 | |||
| 45 | == Additional methods to protect information: == | ||
| 46 | |||
| 47 | (% style="width:80%" %) | ||
| 48 | |(% style="border-color:white; width:48%" %)(% class="box" %) | ||
| 49 | ((( | ||
| 50 | == [[Server Data Protection>>doc:.Server_data_protection.WebHome]] == | ||
| 51 | |||
| 52 | * Operations logging | ||
| 53 | * Data backup | ||
| 54 | )))|(% style="border-color:white" %)((( | ||
| 55 | (% class="box" %) | ||
| 56 | ((( | ||
| 57 | == [[Processing Protection Against Attacks>>doc:.Processing_protection.WebHome]] == | ||
| 58 | |||
| 59 | * Using captcha | ||
| 60 | * Access limits | ||
| 61 | ))) | ||
| 62 | ))) | ||
| 63 | |(% style="border-color:white" %)((( | ||
| 64 | (% class="box" %) | ||
| 65 | ((( | ||
| 66 | == [[Authorization Protection>>doc:.Authorization_protection.WebHome]] == | ||
| 67 | |||
| 68 | * OAuth authorization | ||
| 69 | * Single access point to the system | ||
| 70 | * Differentiation of access rights | ||
| 71 | ))) | ||
| 72 | )))|(% style="border-color:white" %)((( | ||
| 73 | (% class="box" %) | ||
| 74 | ((( | ||
| 75 | == [[Data Transferring Protection>>doc:.Data_protection.WebHome]] == | ||
| 76 | |||
| 77 | * Encrypted channel of data transmission | ||
| 78 | * Digital signature | ||
| 79 | * Masking card numbers | ||
| 80 | * Impersonal wording of errors | ||
| 81 | ))) | ||
| 82 | ))) | ||
| 83 | |(% style="border-color:white" %)((( | ||
| 84 | (% class="box" %) | ||
| 85 | ((( | ||
| 86 | == [[Security of Conducting Operations >>doc:.Security_operations.WebHome]] == | ||
| 87 | |||
| 88 | * Two-phase operation | ||
| 89 | * Limits of operations with a bonus account | ||
| 90 | * Confirmation of bonus points deduction | ||
| 91 | * Card block | ||
| 92 | ))) | ||
| 93 | )))|(% style="border-color:white" %)(% class="box" %) | ||
| 94 | ((( | ||
| 95 | == [[Enforcement of Legislation>>doc:.Compliance_with_laws.WebHome]] == | ||
| 96 | |||
| 97 | * Age limit when registering | ||
| 98 | * Public Offer and processing of personal data | ||
| 99 | * MRP limits | ||
| 100 | * Phone number validation | ||
| 101 | ))) |